U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: Neha Malcom Francis <n-francis@ti.com>,
	Bryan Brattlof <bb@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
	Andrew Davis <afd@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: Tue, 25 Jul 2023 17:00:15 -0500	[thread overview]
Message-ID: <20230725220015.i5dctounavfnsobg@wrinkle> (raw)
In-Reply-To: <20230725213552.GJ3630934@bill-the-cat>

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 :(

I am wondering how to let people read a single page and know all the
steps to build the components needed instead of referring to other docs.

Are you thinking something like:
https://gist.github.com/nmenon/8c883ebf37a5d6021400cce9d76bfc35

I am not a sphinx expert, is this something you'd not like?

I have had feedback from multiple folks saying one single doc showing
all the build commands for the platform is what they are trying to get..
so this might be a good trade-off, perhaps?


[..]
> > +Image formats:
> > +--------------
> > +
> > +The Image format follows the standard AM62X image format [1]_.
> > +
> > +A53 SPL DDR Memory Layout
> > +-------------------------
> 
> This is unchanged for all AM62 platforms, yes? That should be in a
> generic am62 doc.

I really did think of it, but then, if we did have config fragments, I
could have reused things, but at the moment, it is a different
defconfig.. hence, though it is same at the moment, I cant guarantee it.


-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2023-07-25 22:00 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 [this message]
2023-07-25 22:45       ` Tom Rini
2023-07-26 14:59         ` Andrew Davis
2023-07-26 16:21           ` Tom Rini
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=20230725220015.i5dctounavfnsobg@wrinkle \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=n-francis@ti.com \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=trini@konsulko.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