From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tarang Raval <tarang.raval@siliconsignals.io>,
Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
Cc: "linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: pinctrl: convert pinctrl-mcp23s08.txt to yaml format
Date: Sat, 26 Oct 2024 20:06:37 +0200 [thread overview]
Message-ID: <91a8d0ab-a6a6-4dfa-8613-8d4dbafeda40@kernel.org> (raw)
In-Reply-To: <PN3P287MB1829C2FCE4C56325CD1DC8988B482@PN3P287MB1829.INDP287.PROD.OUTLOOK.COM>
On 26/10/2024 17:02, Tarang Raval wrote:
> Hi Krzysztof , Himanshu
>
>>>> +
>>>> + i2c {
>>>
>>> Keep one complete example for i2c and one for spi. This was not in
>>> previous patch and change log does not explain why you need three
>>> examples.
>>
>> Okay, I will drop one example of I2C
>
> In ex1: use when you only need basic GPIO and interrupt capabilities
> without additional pin control and in ex2: use when you need pull-up
> resistors on specific GPIO pins or a reset line.
>
> Original bindings state that this node can be implemented in two
> different ways, so we should maintain both examples for reference.
Example is not the binding. If you claim conversion is incomplete, it
must be done through the binding, not example.
>
> But it's up to you, I trust your expertise on this, Krzysztof
>
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>> +
>>>> + mcp23017: gpio@21 {
>>>
>>> Drop unused label
>>
>> May I know how its unused, AFAIK, Since it's an I/O expanded, it’s referenced elsewhere, so keeping it is necessary for >functionality.
>
> I agree with Himanshu.
> It's definitely used for reset GPIOs, LED pins, or something similar.
So point to the specific line in this file. Really, it's no different
than every other binding. If it is different, provide some arguments why
this is different.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-26 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 12:46 [PATCH v2] dt-bindings: pinctrl: convert pinctrl-mcp23s08.txt to yaml format Himanshu Bhavani
2024-10-26 12:18 ` Krzysztof Kozlowski
2024-10-26 13:11 ` Himanshu Bhavani
2024-10-26 15:02 ` Tarang Raval
2024-10-26 18:06 ` Krzysztof Kozlowski [this message]
2024-10-26 19:25 ` Tarang Raval
2024-10-26 18:05 ` Krzysztof Kozlowski
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=91a8d0ab-a6a6-4dfa-8613-8d4dbafeda40@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tarang.raval@siliconsignals.io \
/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).