From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Kryštof Černý" <cleverline1mc@gmail.com>,
"Conor Dooley" <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Stefan Wahren <stefan.wahren@chargebyte.com>,
Ben Gardner <bgardner@wabtec.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: w1: ds2482: Add vcc-supply property
Date: Wed, 20 Nov 2024 09:48:53 +0100 [thread overview]
Message-ID: <9896a38f-4b68-46a9-83b8-bf76abea47ba@kernel.org> (raw)
In-Reply-To: <83c8487c-2c50-4315-8244-ff80632165e9@gmail.com>
On 20/11/2024 09:34, Kryštof Černý wrote:
> Hello,
>
>> On Fri, Nov 15, 2024 at 03:58:06PM +0100, Kryštof Černý via B4 Relay wrote:
>>> From: Kryštof Černý <cleverline1mc@gmail.com>
>>>
>>> Adds the newly added vcc-supply property to bindings.
>>
>> This commit message is a circular argument. You're adding it to the
>> binding, which of course means it is newly added.
>
> You are right, I will replace with "Adds the vcc-supply property to
> bindings." in the next version.
No, please say why, e.g. because it was missing and device has it
according to datasheet.
>
>>>
>>> Signed-off-by: Kryštof Černý <cleverline1mc@gmail.com>
>>> ---
>>> Documentation/devicetree/bindings/w1/maxim,ds2482.yaml | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/w1/maxim,ds2482.yaml b/Documentation/devicetree/bindings/w1/maxim,ds2482.yaml
>>> index 422becc6e1fa8d58665c5586ebdc611cd0b2c760..a6b9e0658ec858cb24b21cf64443a061bb43e4ef 100644
>>> --- a/Documentation/devicetree/bindings/w1/maxim,ds2482.yaml
>>> +++ b/Documentation/devicetree/bindings/w1/maxim,ds2482.yaml
>>> @@ -25,6 +25,9 @@ properties:
>>> reg:
>>> maxItems: 1
>>>
>>> + vcc-supply:
>>> + description: phandle of the regulator that provides the supply voltage.
>>
>> "vcc-supply: true" should suffice.
>>
>
> Right, I suppose you mean to remove the description and just have
> "vcc-supply: true".
> If so, could you explain why no description? Is it some standard property
> or because the name is self-explanatory? If you mean to keep both,
> please reply.
It's almost self-explanatory and your description does not give any more
information. git grep for existing code - you will find also examples
which give actual information, e.g. detailed PIN name and accepted voltages.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-20 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 14:58 [PATCH 0/3] Add support for attaching a regulator to w1: ds2482 Kryštof Černý via B4 Relay
2024-11-15 14:58 ` [PATCH 1/3] w1: ds2482: Add regulator support Kryštof Černý via B4 Relay
2024-11-15 14:58 ` [PATCH 2/3] w1: ds2482: Fix datasheet URL Kryštof Černý via B4 Relay
2024-11-15 14:58 ` [PATCH 3/3] dt-bindings: w1: ds2482: Add vcc-supply property Kryštof Černý via B4 Relay
2024-11-15 18:16 ` Conor Dooley
2024-11-20 8:34 ` Kryštof Černý
2024-11-20 8:48 ` Krzysztof Kozlowski [this message]
2024-11-20 22:53 ` Kryštof Černý
2024-11-21 7:43 ` Krzysztof Kozlowski
2024-11-21 15:56 ` Kryštof Černý
2024-11-21 16:21 ` 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=9896a38f-4b68-46a9-83b8-bf76abea47ba@kernel.org \
--to=krzk@kernel.org \
--cc=bgardner@wabtec.com \
--cc=cleverline1mc@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stefan.wahren@chargebyte.com \
/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