From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Heiko Stübner" <heiko@sntech.de>,
"Quentin Schulz" <foss+kernel@0leil.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: add spi controller aliases on rk3399
Date: Tue, 9 Jan 2024 20:13:23 +0100 [thread overview]
Message-ID: <e5737533-a7fa-4949-a8ca-d2c5c0a6210f@linaro.org> (raw)
In-Reply-To: <2305627.1xdlsreqCQ@diego>
On 09/01/2024 16:22, Heiko Stübner wrote:
> Hi Krzysztof,
>
> Am Dienstag, 9. Januar 2024, 16:15:30 CET schrieb Krzysztof Kozlowski:
>> On 09/01/2024 14:35, Quentin Schulz wrote:
>>> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>>>
>>> There are 6 SPI controllers on RK3399 and they are all numbered in the
>>> TRM, so let's add the appropriate aliases to the main DTSI so that any
>>> RK3399-based board doesn't need to define the aliases themselves to
>>> benefit from stable SPI indices in userspace.
>>
>> But that contradicts the point that board should define aliases for
>> exposable interfaces. Sorry, that's a NAK.
>
> didn't we have this same discussion some weeks ago? ;-) .
We could have and my feedback might be repeated every time someone does
something against common policy or common sense without explaining it.
>
> I.e. spi2 on Rockchip socs is called spi2 in _all_ SoC documentation,
This does not matter.
> lines in _all_ schematics are also always called spi2_foo , so as before
If you mean board schematics, then this matters.
> I really don't see any value in repeating the very same aliases in
> _every_ board.
>
> Same for i2c, uart .
>
The same as in all previous discussions: the board labels them and these
should match the board labeling.
https://lore.kernel.org/linux-rockchip/CAK8P3a25iYksubCnQb1-e5yj=crEsK37RB9Hn4ZGZMwcVVrG7g@mail.gmail.com/
https://lore.kernel.org/all/27455049.omNFrla0xU@wuerfel/
These are replies from your upstream maintainer, if you disagree with me.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-09 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 13:35 [PATCH 0/2] arm64: dts: rockchip: add SPI controller aliases to RK3399 Quentin Schulz
2024-01-09 13:35 ` [PATCH 1/2] arm64: dts: rockchip: add spi controller aliases on rk3399 Quentin Schulz
2024-01-09 15:15 ` Krzysztof Kozlowski
2024-01-09 15:22 ` Heiko Stübner
2024-01-09 16:14 ` Dragan Simic
2024-01-09 19:13 ` Krzysztof Kozlowski [this message]
2024-01-09 13:35 ` [PATCH 2/2] arm64: dts: rockchip: remove duplicate SPI aliases for helios64 Quentin Schulz
2024-01-09 15:16 ` Krzysztof Kozlowski
2024-01-09 15:23 ` Heiko Stübner
2024-01-09 19:14 ` Krzysztof Kozlowski
2024-01-10 11:18 ` Heiko Stübner
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=e5737533-a7fa-4949-a8ca-d2c5c0a6210f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=foss+kernel@0leil.net \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®