From: Tom Rini <trini@konsulko.com>
To: Andrew Davis <afd@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Bryan Brattlof <bb@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Vignesh R <vigneshr@ti.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 6/6] doc: board: ti: Add beagleplay documentation
Date: Wed, 26 Jul 2023 12:21:47 -0400 [thread overview]
Message-ID: <20230726162147.GT3630934@bill-the-cat> (raw)
In-Reply-To: <db210ab9-6d77-4a6a-3ed1-db4c1d5a8270@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]
On Wed, Jul 26, 2023 at 09:59:16AM -0500, Andrew Davis wrote:
> On 7/25/23 5:45 PM, Tom Rini wrote:
> > On Tue, Jul 25, 2023 at 05:00:15PM -0500, Nishanth Menon wrote:
> > > On 17:35-20230725, Tom Rini wrote:
> > > > On Tue, Jul 25, 2023 at 01:52:53PM -0500, Nishanth Menon wrote:
> > > >
> > > [...]
> > >
> > > > > +
> > > > > +Build procedure:
> > > > > +----------------
> > > > > +1. Trusted Firmware-A:
> > > > > +
> > > > > +.. code-block:: bash
> > > > > +
> > > > > + $ make CROSS_COMPILE=aarch64-none-linux-gnu- ARCH=aarch64 PLAT=k3 \
> > > > > + TARGET_BOARD=lite SPD=opteed
> > > > > +
> > > > > +2. OP-TEE:
> > > > > +
> > > > > +.. code-block:: bash
> > > > > +
> > > > > + $ make PLATFORM=k3 CFG_ARM64_core=y CROSS_COMPILE=arm-none-linux-gnueabihf- \
> > > > > + CROSS_COMPILE64=aarch64-none-linux-gnu-
> > > >
> > > > So, we have some generic wording on how to build TF-A and OP-TEE up in
> > > > doc/board/ti/k3.rst. It should be made clearer if needed that unless
> > > > otherwise indicated, top of tree is expected to be used for TF-A/OP-TEE
> > > > and ti-linux-firmware for the ti-linux-firmware repo. Then just state
> > > > that TF-A should be which of {lite|generic|j784s4} as it is a $family
> > > > device. And we then drop much of the duplication here.
> > >
> > > Also, Robert pointed out I missed K3_PM_SYSTEM_SUSPEND=1 :(
> >
> > Ugh, how many platforms is that variable valid for?
> >
> None soon :)
>
> I'm getting rid of that flag in TF-A. There is a bug blocking me right now,
> but after that it will be automatic. Not sure if it is worth documenting a
> flag that is going away..
OK. But, automatic how? What I'm getting at, from both a documentation
standpoint and also how I run my labs standpoint, is that it seems like
instead of having a set of TF-A and OP-TEE binaries for each TI K3
platform I have, I really need just 3 different TF-A builds (well, in
reality I don't have the J784s4 stuff so just 2) and a single OP-TEE
build.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-07-26 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 18:52 [PATCH 0/6] board: ti: Add support for BeaglePlay Nishanth Menon
2023-07-25 18:52 ` [PATCH 1/6] doc: board: ti: k3: Sort the boards in alphabetical order Nishanth Menon
2023-07-25 21:23 ` Tom Rini
2023-07-25 18:52 ` [PATCH 2/6] arm: dts: k3-am625-sk-binman: Add labels for unsigned binary Nishanth Menon
2023-07-25 21:23 ` Tom Rini
2023-07-25 18:52 ` [PATCH 3/6] board: ti: am62x: Add basic initialization for usb voltage, 32k crystal, debounce Nishanth Menon
2023-07-25 21:25 ` Tom Rini
2023-07-25 21:37 ` Nishanth Menon
2023-07-25 21:42 ` Tom Rini
2023-07-25 22:03 ` Nishanth Menon
2023-07-25 22:16 ` Francesco Dolcini
2023-07-25 22:35 ` Francesco Dolcini
2023-07-26 11:10 ` Nishanth Menon
2023-07-26 13:29 ` Francesco Dolcini
2024-01-07 10:54 ` Jan Kiszka
2023-07-25 18:52 ` [PATCH 4/6] arm: dts: Add k3-am625-beagleplay Nishanth Menon
2023-07-25 21:25 ` Tom Rini
2023-07-25 18:52 ` [PATCH 5/6] configs: Add am62x_beagleplay_* defconfigs Nishanth Menon
2023-07-25 18:52 ` [PATCH 6/6] doc: board: ti: Add beagleplay documentation Nishanth Menon
2023-07-25 21:35 ` Tom Rini
2023-07-25 22:00 ` Nishanth Menon
2023-07-25 22:45 ` Tom Rini
2023-07-26 14:59 ` Andrew Davis
2023-07-26 16:21 ` Tom Rini [this message]
2023-07-26 16:41 ` Andrew Davis
2023-07-26 16:49 ` Tom Rini
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=20230726162147.GT3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robertcnelson@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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