From: Paul Cercueil <paul@crapouillou.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Rahul Bedarkar" <rahulbedarkar89@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] MIPS: dts: correct gpio-keys names and properties
Date: Sat, 25 Jun 2022 21:15:14 +0100 [thread overview]
Message-ID: <EXU1ER.FH53VZXY9EYP3@crapouillou.net> (raw)
In-Reply-To: <89b6a40b-eb6b-eba5-78c3-6b5f35bed717@linaro.org>
Hi Krzysztof,
Le sam., juin 25 2022 at 21:58:08 +0200, Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> a écrit :
> On 24/06/2022 20:40, Paul Cercueil wrote:
>> Hi Krzysztof,
>>
>> Le ven., juin 24 2022 at 19:07:39 +0200, Krzysztof Kozlowski
>> <krzysztof.kozlowski@linaro.org> a écrit :
>>> gpio-keys children do not use unit addresses.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>
>>> ---
>>>
>>> See:
>>>
>>> https://lore.kernel.org/all/20220616005224.18391-1-krzysztof.kozlowski@linaro.org/
>>> ---
>>> arch/mips/boot/dts/img/pistachio_marduk.dts | 4 +--
>>> arch/mips/boot/dts/ingenic/gcw0.dts | 31
>>> +++++++++----------
>>> arch/mips/boot/dts/ingenic/rs90.dts | 18 +++++------
>>> arch/mips/boot/dts/pic32/pic32mzda_sk.dts | 9 ++----
>>> .../boot/dts/qca/ar9132_tl_wr1043nd_v1.dts | 6 ++--
>>> arch/mips/boot/dts/qca/ar9331_dpt_module.dts | 4 +--
>>> .../mips/boot/dts/qca/ar9331_dragino_ms14.dts | 6 ++--
>>> arch/mips/boot/dts/qca/ar9331_omega.dts | 4 +--
>>> .../qca/ar9331_openembed_som9331_board.dts | 4 +--
>>> arch/mips/boot/dts/qca/ar9331_tl_mr3020.dts | 8 ++---
>>> 10 files changed, 37 insertions(+), 57 deletions(-)
>>>
>>> diff --git a/arch/mips/boot/dts/img/pistachio_marduk.dts
>>> b/arch/mips/boot/dts/img/pistachio_marduk.dts
>>> index a8708783f04b..a8da2f992b1a 100644
>>> --- a/arch/mips/boot/dts/img/pistachio_marduk.dts
>>> +++ b/arch/mips/boot/dts/img/pistachio_marduk.dts
>>> @@ -59,12 +59,12 @@ led-1 {
>>>
>>> keys {
>>> compatible = "gpio-keys";
>>> - button@1 {
>>> + button-1 {
>>> label = "Button 1";
>>> linux,code = <0x101>; /* BTN_1 */
>>> gpios = <&gpio3 6 GPIO_ACTIVE_LOW>;
>>> };
>>> - button@2 {
>>> + button-2 {
>>> label = "Button 2";
>>> linux,code = <0x102>; /* BTN_2 */
>>> gpios = <&gpio2 14 GPIO_ACTIVE_LOW>;
>>> diff --git a/arch/mips/boot/dts/ingenic/gcw0.dts
>>> b/arch/mips/boot/dts/ingenic/gcw0.dts
>>> index 4abb0318416c..5d33f26fd28c 100644
>>> --- a/arch/mips/boot/dts/ingenic/gcw0.dts
>>> +++ b/arch/mips/boot/dts/ingenic/gcw0.dts
>>> @@ -130,89 +130,86 @@ backlight: backlight {
>>>
>>> gpio-keys {
>>> compatible = "gpio-keys";
>>> - #address-cells = <1>;
>>> - #size-cells = <0>;
>>
>> Are you sure you can remove these?
>
> Yes, from DT spec point of view, DT bindings and Linux implementation.
> However this particular change was not tested, except building.
>
>>
>> Looking at paragraph 2.3.5 of the DT spec, I would think they have
>> to
>> stay (although with #address-cells = <0>).
>
> The paragraph 2.3.5 says nothing about regular properties (which can
> be
> also child nodes). It says about children of a bus, right? It's not
> related here, it's not a bus.
I quote:
"A DTSpec-compliant boot program shall supply #address-cells and
#size-cells on all nodes that have children."
The gpio-keys node has children nodes, therefore it should have
#address-cells and #size-cells, there's no room for interpretation here.
> Second, why exactly this one gpio-keys node is different than all
> other
> gpio-keys everywhere and than bindings? Why this one has to be
> incompatible/wrong according to bindings (which do not allow
> address-cells and nodes with unit addresses)?
Nothing is different. I'm just stating that your proposed fix is
invalid if we want to enforce compliance with the DT spec.
Cheers,
-Paul
>
next prev parent reply other threads:[~2022-06-25 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 17:07 [PATCH 1/2] MIPS: dts: correct gpio-keys names and properties Krzysztof Kozlowski
2022-06-24 17:07 ` [PATCH 2/2] MIPS: dts: align gpio-key node names with dtschema Krzysztof Kozlowski
2022-06-29 12:12 ` Arınç ÜNAL
2022-07-14 9:56 ` Thomas Bogendoerfer
2022-06-24 18:40 ` [PATCH 1/2] MIPS: dts: correct gpio-keys names and properties Paul Cercueil
2022-06-25 19:58 ` Krzysztof Kozlowski
2022-06-25 20:15 ` Paul Cercueil [this message]
2022-06-25 20:25 ` Krzysztof Kozlowski
2022-06-29 12:08 ` Arınç ÜNAL
2022-07-14 9:55 ` Thomas Bogendoerfer
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=EXU1ER.FH53VZXY9EYP3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rahulbedarkar89@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.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