From: "Heiko Stübner" <heiko@sntech.de>
To: arm <arm@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, Yao Zi <ziyao@disroot.org>
Subject: Re: [GIT PULL] Rockchip dts64 changes for 6.16 #1
Date: Fri, 09 May 2025 23:37:28 +0200 [thread overview]
Message-ID: <2857184.BEx9A2HvPv@diego> (raw)
In-Reply-To: <c142bdf4-3910-48bb-ba5e-8accbdb32a00@app.fastmail.com>
Hi Arnd,
Am Freitag, 9. Mai 2025, 23:03:54 Mitteleuropäische Sommerzeit schrieb Arnd Bergmann:
> On Thu, May 8, 2025, at 00:04, Heiko Stuebner wrote:
> > Hi soc maintainers,
> >
> > please find below and in a subsequent pull-requests
> > Rockchip changes for for 6.16 .
> >
> > Even some arm32 boards got some love (in the next PR)
>
> One small issue stuck out here:
>
>
> > Yao Zi (2):
> > arm64: dts: rockchip: Add I2C controllers for RK3528
>
> This creates a lot of new aliases in the dtsi file:
>
> index 826f9be0be19..2c9780069af9 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> @@ -24,6 +24,14 @@ aliases {
> gpio2 = &gpio2;
> gpio3 = &gpio3;
> gpio4 = &gpio4;
> + i2c0 = &i2c0;
> + i2c1 = &i2c1;
> + i2c2 = &i2c2;
> + i2c3 = &i2c3;
> + i2c4 = &i2c4;
> + i2c5 = &i2c5;
> + i2c6 = &i2c6;
> + i2c7 = &i2c7;
> serial0 = &uart0;
> serial1 = &uart1;
>
> but the corresponding nodes are left at disabled. I see
> that the same mistake is present in the uart nodes.
>
> Please send a fixup to remove these from the .dtsi file
> here and the similar chips, unless you are sure that every
> board will have them enabled (like e.g. the gpio nodes).
>
> The aliases are not meant to refer to soc-internal names,
> but the identifiers on board.
For the uarts and i2c (and spi), all the identifiers are always numerical
both in the SoC documentation as well as on the boards and board
schematics.
If you look in a random Rockchip schematic file, the lines for the i2c0
controller will be called i2c0_scl_foo, i2c0_sda_foo, etc.
Similar uart0_tx, uart0_rx, etc.
So while I fully understand that mmc0 -> emmc, mmc1 -> sd-card are very
much board specific, somehow repeating the very same i2c aliases for every
board feels strange. The 7th i2c controller on the soc, will never be
called anything else than i2c7 afterall.
But ok, if you feel strongly about that, I'll move the i2c and uart aliases.
Heiko
next prev parent reply other threads:[~2025-05-09 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 22:04 [GIT PULL] Rockchip dts64 changes for 6.16 #1 Heiko Stuebner
2025-05-09 21:03 ` Arnd Bergmann
2025-05-09 21:37 ` Heiko Stübner [this message]
2025-05-10 10:27 ` Arnd Bergmann
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=2857184.BEx9A2HvPv@diego \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=soc@kernel.org \
--cc=ziyao@disroot.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;
as well as URLs for NNTP newsgroup(s).