public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Heiko Thiery <heiko.thiery@gmail.com>,
	Tim Harvey <tharvey@gateworks.com>
Cc: u-boot <u-boot@lists.denx.de>,
	"Ying-Chun Liu" <paul.liu@linaro.org>,
	"Peng Fan" <peng.fan@nxp.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Marek Vasut" <marek.vasut@gmail.com>,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	"Sean Anderson" <seanga2@gmail.com>,
	"Thomas Schäfer" <thomas.schaefer@kontron.com>,
	"Stefano Babic" <sbabic@denx.de>,
	"Simon Glass" <sjg@chromium.org>
Subject: Re: [PATCH v2 2/2] ARM: imx: imx8mn-evk: use one common u-boot.dtsi for the evk boards
Date: Wed, 22 Jun 2022 21:16:58 +0300	[thread overview]
Message-ID: <330e62ca-2d80-03a6-2a0b-fa0e364b295d@gmail.com> (raw)
In-Reply-To: <CAEyMn7ZSGURzGK262ZFw25dAZJf1=huRLrV=MVT2Sra_fROZHA@mail.gmail.com>

On 10/06/2022 00:38, Heiko Thiery wrote:
> Hi Tim, Hi Simon,
> 
> [SNIP]
> 
>>
>> Heiko,
>>
>> You can add multi-dtb support to this so that it's usable by the other
>> imx8mn boards with the following:
>> 
>> [...]
>> 
>> I don't mind sending this as a follow-up to your patch here.
> 
> Since this patch moves the parts from the 2 imx8mn-evk boards to one
> "common" file it would be better to do more changes on that in a
> separate patch.
> 
>> It looks like there are only the following boards in mainline that
>> would benefit from using this shared include:
>> imx8mn-beacon-kit-u-boot.dtsi
>> imx8mn-var-som-symphony-u-boot.dtsi
>> imx8mn-venice-u-boot.dtsi

There's also 'imx8mn-bsh-smm-s2-u-boot-common.dtsi'. Slightly different
because only half of the blobs are there with IMX8M_DDR3L.

>> Have you compared the binman portions of imx8m{m,n,p}-u-boot.dtsi?
> 
> No not yet.

I looked a bit and they look very much alike. I suspect it's possible to
eventually unify everything into a shared 'imx8m-u-boot.dtsi', but I
didn't actually try.

>> There are a lot of differences due to different property ordering and
>> label/node naming conventions. I would like to see these normalized
>> but i'm not clear which is the best example to normalize to.
>> Specifically I don't know:
>> 1. what is the convention for property ordering in dt... is it simply
>> alphabetical order?

AFAIK property order doesn't matter for binman. Node order is very
significant though. For names, I think we should:

- Prefer hyphens to underscores
- Prefer lowercase to uppercase
- Prefer meaningful names to things like 'blob-ext@1'
- Avoid first char being a number (because labels can't have that)

>> 2. have we settled on a convention for the blob naming, if so what is
>> the best example?

I had suggested 'ddr-1d-imem-fw' etc. on a series from Peng, see latest
version of it [1].

[1] arm: dts: imx8m: update binman ddr firmware node name
https://lore.kernel.org/u-boot/20220603071715.15212-4-peng.fan@oss.nxp.com/

> I am not aware that there is a conventional here. But maybe simon can
> give some hints here.
> 

  reply	other threads:[~2022-06-22 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 20:49 [PATCH v2 1/2] ARM: imx: imx8mn-evk: generate a single bootable flash.bin Heiko Thiery
2022-06-09 20:49 ` [PATCH v2 2/2] ARM: imx: imx8mn-evk: use one common u-boot.dtsi for the evk boards Heiko Thiery
2022-06-09 21:17   ` Tim Harvey
2022-06-09 21:38     ` Heiko Thiery
2022-06-22 18:16       ` Alper Nebi Yasak [this message]
2022-06-22 18:16   ` Alper Nebi Yasak
2022-06-26  9:53     ` Heiko Thiery
2022-06-22 18:16 ` [PATCH v2 1/2] ARM: imx: imx8mn-evk: generate a single bootable flash.bin Alper Nebi Yasak
2022-06-26  9:49   ` Heiko Thiery

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=330e62ca-2d80-03a6-2a0b-fa0e364b295d@gmail.com \
    --to=alpernebiyasak@gmail.com \
    --cc=festevam@gmail.com \
    --cc=heiko.thiery@gmail.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marek.vasut@gmail.com \
    --cc=paul.liu@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=tharvey@gateworks.com \
    --cc=thomas.schaefer@kontron.com \
    --cc=u-boot@lists.denx.de \
    /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