From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Tinaco, Mariel" <Mariel.Tinaco@analog.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <noname.nuno@gmail.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: dac: add docs for ad8460
Date: Mon, 9 Sep 2024 08:41:53 +0200 [thread overview]
Message-ID: <9889af99-9da4-48ea-aa7e-64529222f2cb@kernel.org> (raw)
In-Reply-To: <SJ0PR03MB6224860552845EF2B3339DF591992@SJ0PR03MB6224.namprd03.prod.outlook.com>
On 09/09/2024 08:22, Tinaco, Mariel wrote:
>
>
>> -----Original Message-----
>> From: Jonathan Cameron <jic23@kernel.org>
>> Sent: Sunday, September 8, 2024 1:02 AM
>> To: Krzysztof Kozlowski <krzk@kernel.org>
>> Cc: Tinaco, Mariel <Mariel.Tinaco@analog.com>; linux-iio@vger.kernel.org;
>> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Lars-Peter Clausen
>> <lars@metafoo.de>; Rob Herring <robh@kernel.org>; Krzysztof Kozlowski
>> <krzk+dt@kernel.org>; Hennerich, Michael <Michael.Hennerich@analog.com>;
>> Conor Dooley <conor+dt@kernel.org>; Marcelo Schmitt
>> <marcelo.schmitt1@gmail.com>; Dimitri Fedrau <dima.fedrau@gmail.com>;
>> David Lechner <dlechner@baylibre.com>; Nuno Sá
>> <noname.nuno@gmail.com>
>> Subject: Re: [PATCH v3 1/2] dt-bindings: iio: dac: add docs for ad8460
>>
>> [External]
>>
>> On Wed, 4 Sep 2024 08:20:53 +0200
>> Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>>> On Wed, Sep 04, 2024 at 10:30:39AM +0800, Mariel Tinaco wrote:
>>>> This adds the bindings documentation for the 14-bit
>>>
>>> Please do not use "This commit/patch/change", but imperative mood. See
>>> longer explanation here:
>>> https://urldefense.com/v3/__https://elixir.bootlin.com/linux/v5.17.1/s
>>> ource/Documentation/process/submitting-
>> patches.rst*L95__;Iw!!A3Ni8CS0y
>>> 2Y!7lj0hq-U2ClkGNYfHqjR3-k-
>> ea6TFUFsgEYQokkU95K6TXPHIPU33VxQcl_iH_etJ4k
>>> pbPEV39dP1oAd$
>>>
>>>> High Voltage, High Current, Waveform Generator Digital-to-Analog
>>>> converter.
>>>>
>>>> Signed-off-by: Mariel Tinaco <Mariel.Tinaco@analog.com>
>>>> ---
>>>> .../bindings/iio/dac/adi,ad8460.yaml | 154 ++++++++++++++++++
>>>> MAINTAINERS | 7 +
>>>> 2 files changed, 161 insertions(+)
>>>> create mode 100644
>>>> Documentation/devicetree/bindings/iio/dac/adi,ad8460.yaml
>>>
>>>> + adi,range-microvolt:
>>>> + description: Voltage output range specified as <minimum, maximum>
>>>> + oneOf:
>>>
>>> This oneOf does not make sense. There is only one condition. Drop.
>>>
>>>> + - items:
>>>> + - enum: [0, -10000000, -20000000, -30000000, -40000000, -
>> 55000000]
>>>> + - enum: [10000000, 20000000, 30000000, 40000000,
>>>> + 55000000]
>>>
>>> What's the default? It's not a required property.
>>>
>>>> +
>>>> + adi,range-microamp:
>>>> + description: Current output range specified as <minimum, maximum>
>>>> + oneOf:
>>>> + - items:
>>>> + - enum: [-50000, -100000, -300000, -500000, -1000000]
>>>
>>> I don't understand why 0 is not listed here.
>>
>> I'm not sure why it is a list at all. Seems like the hardware allows a continuous
>> value so this should just specify max and min.
>>
>
> That's right, the values can be flexible but only at a certain range.
> The first element of the array should only be in the negative range, while
> The second element of the array should only be in the positive range.
>
> Is there a way to do this with the max and min attribute?
>
> Items:
> Item 1
> min: -10000
> max: 0
> item 2
> min: 0
> max: 10000
items:
- minimum: -10000
maximum: 0
- minimum: 0
maximum: 10000
should work, try.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-09 6:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 2:30 [PATCH v3 0/2] Add support to AD8460 Waveform Generator DAC Mariel Tinaco
2024-09-04 2:30 ` [PATCH v3 1/2] dt-bindings: iio: dac: add docs for ad8460 Mariel Tinaco
2024-09-04 6:20 ` Krzysztof Kozlowski
2024-09-07 17:01 ` Jonathan Cameron
2024-09-09 6:22 ` Tinaco, Mariel
2024-09-09 6:41 ` Krzysztof Kozlowski [this message]
2024-09-04 2:30 ` [PATCH v3 2/2] iio: dac: support the ad8460 Waveform DAC Mariel Tinaco
2024-09-04 15:50 ` kernel test robot
2024-09-04 17:23 ` kernel test robot
2024-09-06 0:50 ` David Lechner
2024-09-09 9:47 ` Tinaco, Mariel
2024-09-09 14:51 ` David Lechner
2024-09-09 19:09 ` Jonathan Cameron
2024-09-10 1:44 ` Tinaco, Mariel
2024-09-14 11:45 ` Jonathan Cameron
2024-09-07 17:14 ` Jonathan Cameron
2024-09-09 8:22 ` Tinaco, Mariel
2024-09-09 14:41 ` David Lechner
2024-09-04 6:16 ` [PATCH v3 0/2] Add support to AD8460 Waveform Generator DAC Krzysztof Kozlowski
2024-09-05 1:10 ` Tinaco, Mariel
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=9889af99-9da4-48ea-aa7e-64529222f2cb@kernel.org \
--to=krzk@kernel.org \
--cc=Mariel.Tinaco@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=noname.nuno@gmail.com \
--cc=robh@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