mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] Documentation: AM62lx: Add note about required TF-A
Date: Tue, 17 Jun 2025 11:10:17 +0200	[thread overview]
Message-ID: <20250617091017.3003866-1-s.hauer@pengutronix.de> (raw)

The am62lx barebox port currently needs a modified downstream TF-A to
work properly. Add a note to the documention providing the necessary
hints and pointers.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 Documentation/boards/ti-k3-am62lx.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Documentation/boards/ti-k3-am62lx.rst b/Documentation/boards/ti-k3-am62lx.rst
index 3cd7a6debf..79f2e17cf3 100644
--- a/Documentation/boards/ti-k3-am62lx.rst
+++ b/Documentation/boards/ti-k3-am62lx.rst
@@ -11,6 +11,14 @@ some firmware files and a BL1 which is responsible for setting up the initial cl
 power domains and DRAM. When this is done the BL1 branches back to the ROM which loads
 the second stage which contains the TF-A BL31, barebox proper and optionally OP-TEE.
 
+.. note::
+The AM62lx support currently depends on a modified downstream version of the TF-A. See
+https://lore.kernel.org/20250617090142.3000882-1-s.hauer@pengutronix.de for a patch
+series to be applied on the Downstream TF-A. Be aware that barebox might need further
+changes to be compatible with future upstream TF-A support. Specifically the SCMI clock
+IDs used in the assigned-clock-parents properties might not match the future upstream
+solution.
+
 Building TF-A
 -------------
 
-- 
2.39.5




                 reply	other threads:[~2025-06-17  9:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250617091017.3003866-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