From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/3] TF-A: AM62lx: Fixes for barebox support
Date: Tue, 17 Jun 2025 11:01:39 +0200 [thread overview]
Message-ID: <20250617090142.3000882-1-s.hauer@pengutronix.de> (raw)
The AM62lx ARM trusted firmware support is not yet merged upstream,
the downstream support is currently available at [1]
Unfortunately this contains some bugs in the SCMI clock implementation
which confuses both the barebox and the Linux SCMI clock driver. TI is
aware of this, see [2] and [3] for details.
I am posting these patches here for others be able to build a usable AM62lx
TF-A for barebox and to refer to these patches from the barebox documentation.
Patches are based on the 11.00.11 tag.
[1] https://github.com/TexasInstruments/arm-trusted-firmware.git.
[2] https://lore.kernel.org/all/aCcSG5ah12N0yOwi@pengutronix.de/
[3] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/34834/1
Sascha Hauer (3):
plat: ti: k3: fix SCMI parent clock ids
plat: ti: k3: return 0 parents for clocks which only have a single
parent
HACK: drop COPY_NAME_IDENTIFIER string length check
drivers/scmi-msg/common.h | 1 -
plat/ti/k3/common/drivers/scmi/scmi_clock.c | 9 ++++++---
2 files changed, 6 insertions(+), 4 deletions(-)
--
2.39.5
next reply other threads:[~2025-06-17 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 9:01 Sascha Hauer [this message]
2025-06-17 9:01 ` [PATCH 1/3] plat: ti: k3: fix SCMI parent clock ids Sascha Hauer
2025-06-17 9:01 ` [PATCH 2/3] plat: ti: k3: return 0 parents for clocks which only have a single parent Sascha Hauer
2025-06-17 9:01 ` [PATCH 3/3] HACK: drop COPY_NAME_IDENTIFIER string length check Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250617090142.3000882-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox