From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Trevor Gamblin" <tgamblin@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"David Lechner" <dlechner@baylibre.com>,
"Uwe Kleine-Konig" <u.kleine-koenig@baylibre.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs
Date: Mon, 12 Aug 2024 15:55:58 +0200 [thread overview]
Message-ID: <c1e63a22-2dd7-48ab-9b98-ffd9f8b08a1b@kernel.org> (raw)
In-Reply-To: <f8a7754e-0f6b-4802-985b-d8817892ecbb@baylibre.com>
On 12/08/2024 15:41, Trevor Gamblin wrote:
>
> On 2024-08-10 8:10 a.m., Krzysztof Kozlowski wrote:
>> On 09/08/2024 20:41, Trevor Gamblin wrote:
>>> Add a binding specification for the Analog Devices Inc. AD7625,
>>> AD7626, AD7960, and AD7961 ADCs.
>>>
>> Thank you for your patch. There is something to discuss/improve.
>>
>>> +allOf:
>>> + - if:
>>> + required:
>>> + - ref-supply
>>> + then:
>>> + # refin-supply is not needed if ref-supply is given
>> Not needed or not allowed? Schema says the latter.
> Yes, this is poor wording on my part. I will fix it to say "not allowed".
so just drop it. No need to repeat schema - it is obvious from the
comment. OTOH, if you want to keep any of such comments, then make it
useful - explain WHY it is not allowed. Because the WHY is not visible
from the code.
>>
>>> + properties:
>>> + refin-supply: false
>>> + - if:
>>> + required:
>>> + - refin-supply
>>> + then:
>>> + # ref-supply is not needed if refin-supply is given
>>> + properties:
>>> + ref-supply: false
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - adi,ad7625
>>> + - adi,ad7626
>>> + then:
>>> + properties:
>>> + en2-gpios: false
>>> + en3-gpios: false
>>> + adi,en2-always-on: false
>>> + adi,en3-always-on: false
>>> +
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - adi,ad7960
>>> + - adi,ad7961
>>> + then:
>>> + # ad796x parts must have one of the two supplies
>>> + oneOf:
>>> + - required: [ref-supply]
>>> + - required: [refin-supply]
>> That's duplicating first and second if. And all three - comment, first
>> if:then: and this one here is kind of contradictory so I don't know what
>> you want to achieve.
>
> It sounds like there's a better way for me to specify this, but I'm not
> exactly sure how.
>
> The AD762x parts can operate without external references, so the intent
> was that neither REF nor REFIN was required in the bindings, but if one
> is given then the other can't be.
>
> For the AD796x parts, one of REF or REFIN must be provided, but not
> both. If REFIN is provided, then REF doesn't need an input because a
> reference voltage is generated on REF. If REF is provided, then REFIN is
> tied to ground.
>
> Maybe there's a simpler way for me to specify the whole block?
Ah, now I see. Looks correct. I am not sure if it could be coded simpler.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-12 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 18:41 [PATCH v2 0/3] iio: adc: add new ad7625 driver Trevor Gamblin
2024-08-09 18:41 ` [PATCH v2 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs Trevor Gamblin
2024-08-10 12:10 ` Krzysztof Kozlowski
2024-08-12 13:41 ` Trevor Gamblin
2024-08-12 13:55 ` Krzysztof Kozlowski [this message]
2024-08-09 18:41 ` [PATCH v2 2/3] iio: adc: ad7625: add driver Trevor Gamblin
2024-08-17 11:47 ` Jonathan Cameron
2024-08-19 12:38 ` Trevor Gamblin
2024-08-09 18:41 ` [PATCH v2 3/3] docs: iio: new docs for ad7625 driver Trevor Gamblin
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=c1e63a22-2dd7-48ab-9b98-ffd9f8b08a1b@kernel.org \
--to=krzk@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=u.kleine-koenig@baylibre.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