From: "Arnd Bergmann" <arnd@arndb.de>
To: "Heiko Stübner" <heiko@sntech.de>, arm <arm@kernel.org>
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: Sat, 10 May 2025 12:27:52 +0200 [thread overview]
Message-ID: <df6003e3-7fc3-4e50-a702-f0aa8d663dff@app.fastmail.com> (raw)
In-Reply-To: <2857184.BEx9A2HvPv@diego>
On Fri, May 9, 2025, at 23:37, Heiko Stübner wrote:
> Am Freitag, 9. Mai 2025, 23:03:54 Mitteleuropäische Sommerzeit schrieb
>>
>> 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.
It's usually most important for the uart, since that tends to go
to an external connector on the board that may use a different
numbering, or may not even use the one you named serial0, so these are
renumbered most of the time.
For i2c, I can see a reason for keeping the numbering the same
as the on-chip pins, but only have an alias for those that are
actually enabled. We should probably have dtc check that there
are no aliases to disabled devices, but that requires cleaning
up a load of board files first.
> But ok, if you feel strongly about that, I'll move the i2c and uart aliases.
Yes, please do.
Arnd
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2025-05-10 10:52 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
2025-05-10 10:27 ` Arnd Bergmann [this message]
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=df6003e3-7fc3-4e50-a702-f0aa8d663dff@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=heiko@sntech.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