From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Fabien Dessenne <fabien.dessenne@foss.st.com>
Subject: Re: [PATCH] dt-bindings: pinctrl: stm32: add missing entries for gpio subnodes
Date: Fri, 23 Sep 2022 11:21:30 +0200 [thread overview]
Message-ID: <5145d4db-65bf-971d-84cd-73c222311cd3@linaro.org> (raw)
In-Reply-To: <c21b9c95-ae35-fd7e-9e8e-6926703725b4@foss.st.com>
On 23/09/2022 10:29, Alexandre TORGUE wrote:
> Hi Krzysztof
>
> On 9/19/22 13:32, Krzysztof Kozlowski wrote:
>> On 13/09/2022 09:46, Alexandre Torgue wrote:
>>> Add "interrupt-controller" and gpio-line-names to gpio subnodes in order to
>>> fix dtb validation.
>>
>> Rebase your patch on recent Linux kernel and use get_maintainers.pl.
>
> I did it on 6.0-rc5 but yes I used your kernel.org address instead of
> linaro ones. Sorry.
>
>>
>>>
>>> Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
>>>
>>> diff --git a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
>>> index d35dcc4f0242..92582cccbb1b 100644
>>> --- a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
>>> +++ b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
>>> @@ -65,6 +65,10 @@ patternProperties:
>>> '#gpio-cells':
>>> const: 2
>>>
>>> + interrupt-controller: true
>>> + '#interrupt-cells':
>>> + const: 2
>>> +
>>> reg:
>>> maxItems: 1
>>> clocks:
>>> @@ -80,6 +84,8 @@ patternProperties:
>>> minimum: 1
>>> maximum: 16
>>>
>>> + gpio-line-names: true
>>
>> maxItems?
>
> Generic question, Is it mandatory to add maxItems information for all
> entries ?
It's not mandatory for all. For some it is recommended, for some it does
not make sense. Here it's quite easy to add and it will validate the
entry. Any reason not to add it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-23 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 7:46 [PATCH] dt-bindings: pinctrl: stm32: add missing entries for gpio subnodes Alexandre Torgue
2022-09-13 15:55 ` Rob Herring
2022-09-19 11:32 ` Krzysztof Kozlowski
2022-09-23 8:29 ` Alexandre TORGUE
2022-09-23 9:21 ` Krzysztof Kozlowski [this message]
2022-09-26 10:32 ` Alexandre TORGUE
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=5145d4db-65bf-971d-84cd-73c222311cd3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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;
as well as URLs for NNTP newsgroup(s).