Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/4] arm64: dts: ti: j721e*: Define aliases in board files
Date: Tue, 30 Aug 2022 15:15:00 -0500	[thread overview]
Message-ID: <20220830201500.sowmkdyrlizpt6o2@confider> (raw)
In-Reply-To: <b96e012d-8537-4695-9ca4-520c7715fcb2@www.fastmail.com>

On 20:18-20220830, Arnd Bergmann wrote:
> On Tue, Aug 30, 2022, at 5:21 PM, Nishanth Menon wrote:
> > Define aliases in board files, instead of in the SoC dtsi file.
> >
> > Reported-by: Daniel Thompson <daniel.thompson@linaro.org>
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> 
> The patch is a good step in the right direction, but
> 
> > 
> > +	aliases {
> > +		serial0 = &wkup_uart0;
> > +		serial1 = &mcu_uart0;
> > +		serial2 = &main_uart0;
> > +		serial3 = &main_uart1;
> > +		serial4 = &main_uart2;
> > +		serial5 = &main_uart3;
> > +		serial6 = &main_uart4;
> > +		serial7 = &main_uart5;
> > +		serial8 = &main_uart6;
> > +		serial9 = &main_uart7;
> > +		serial10 = &main_uart8;
> > +		serial11 = &main_uart9;
> > +		ethernet0 = &cpsw_port1;
> > +		mmc0 = &main_sdhci0;
> > +		mmc1 = &main_sdhci1;
> > +		mmc2 = &main_sdhci2;
> 
> Are all these devices actually used on both of the boards?
> 
> There is no point in defining an alias if the board
> does not route these to a device or a connector.

Thanks and true, I had indeed missed cross checking against the usage.
Will recheck, cleanup and respin this series.

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-30 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 15:21 [PATCH 0/4] arm64: dts: ti: *: Define aliases in board file Nishanth Menon
2022-08-30 15:21 ` [PATCH 1/4] arm64: dts: ti: am65*: Define aliases in board files Nishanth Menon
2022-08-30 15:21 ` [PATCH 2/4] arm64: dts: ti: j721e*: " Nishanth Menon
2022-08-30 18:18   ` Arnd Bergmann
2022-08-30 20:15     ` Nishanth Menon [this message]
2022-08-30 15:21 ` [PATCH 3/4] arm64: dts: ti: j7200*: " Nishanth Menon
2022-08-30 15:21 ` [PATCH 4/4] arm64: dts: ti: am64*: " Nishanth Menon

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=20220830201500.sowmkdyrlizpt6o2@confider \
    --to=nm@ti.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@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