From: David Lechner <dlechner@baylibre.com>
To: "Nuno Sá" <noname.nuno@gmail.com>,
"Kim Seer Paller" <kimseer.paller@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: iio: dac: Add adi,ad3530r.yaml
Date: Fri, 4 Apr 2025 11:28:43 -0500 [thread overview]
Message-ID: <dcb9c90f-480d-456e-ab01-d68171356050@baylibre.com> (raw)
In-Reply-To: <b2082b59fcbffe9f546bb681eb33276a3c5896c5.camel@gmail.com>
On 4/3/25 6:15 AM, Nuno Sá wrote:
>
> Hi Kim,
>
> On Thu, 2025-04-03 at 13:33 +0800, Kim Seer Paller wrote:
>> Document the AD3530/AD3530R (8-channel) and AD3531/AD3531R (4-channel)
>> low-power, 16-bit, buffered voltage output DACs with software-
>> programmable gain controls. They provide full-scale output spans of 2.5V
>> or 5V for reference voltages of 2.5V. These devices operate on a single
>> 2.7V to 5.5V supply and are guaranteed to be monotonic by design.
>> The "R" variants include a 2.5V, 5ppm/°C internal reference, which is
>> disabled by default.
>>
>> Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
>> ---
>> .../devicetree/bindings/iio/dac/adi,ad3530r.yaml | 99
>> ++++++++++++++++++++++
>> MAINTAINERS | 7 ++
>> 2 files changed, 106 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad3530r.yaml
>> b/Documentation/devicetree/bindings/iio/dac/adi,ad3530r.yaml
>> new file mode 100644
>> index
>> 0000000000000000000000000000000000000000..cf4a3eb98f1fa30afdeb0740bba7f052d8ec
>> 2cd4
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/dac/adi,ad3530r.yaml
>> @@ -0,0 +1,99 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/iio/dac/adi,ad3530r.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Analog Devices AD3530R and Similar DACs
>> +
>> +maintainers:
>> + - Kim Seer Paller <kimseer.paller@analog.com>
>> +
>> +description: |
>> + The AD3530/AD3530R (8-channel) and AD3531/AD3531R (4-channel) are low-
>> power,
>> + 16-bit, buffered voltage output digital-to-analog converters (DACs) with
>> + software-programmable gain controls, providing full-scale output spans of
>> 2.5V
>> + or 5V for reference voltages of 2.5V. These devices operate from a single
>> 2.7V
>> + to 5.5V supply and are guaranteed monotonic by design. The "R" variants
>> + include a 2.5V, 5ppm/°C internal reference, which is disabled by default.
>> + Datasheet can be found here:
>> +
>> https://www.analog.com/media/en/technical-documentation/data-sheets/ad3530_ad530r.pdf
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - adi,ad3530
>> + - adi,ad3530r
>> + - adi,ad3531
>> + - adi,ad3531r
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + spi-max-frequency:
>> + maximum: 50000000
>> +
>> + vdd-supply:
>> + description: Power Supply Input.
>> +
>> + iovdd-supply:
>> + description: Digital Power Supply Input.
>> +
>> + io-channels:
>> + description:
>> + ADC channel used to monitor internal die temperature, output voltages,
>> and
>> + current of a selected channel via the MUXOUT pin.
>> + maxItems: 1
>>
>
> I'm a bit puzzled... Isn't this device the provider of such a channel?
> Therefore, I believe we should have #io-channel-cells, right?
Nope. :-)
The MUXOUT is an analog output pin, so this property is to read back from
an external ADC what the analog value of MUXOUT is. The DAC doesn't have an
internal ADC for measuring these values.
Comes from Jonathan's suggestion on a similar chip:
https://lore.kernel.org/linux-iio/20240413160610.4cec010b@jic23-huawei/
>
> - Nuno Sá
>
>
next prev parent reply other threads:[~2025-04-04 16:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 5:33 [PATCH v3 0/3] Add driver for AD3530R and AD3531R DACs Kim Seer Paller
2025-04-03 5:33 ` [PATCH v3 1/3] iio: ABI: add new DAC powerdown mode Kim Seer Paller
2025-04-03 5:33 ` [PATCH v3 2/3] dt-bindings: iio: dac: Add adi,ad3530r.yaml Kim Seer Paller
2025-04-03 6:27 ` Rob Herring (Arm)
2025-04-03 6:44 ` Krzysztof Kozlowski
2025-04-03 6:59 ` Paller, Kim Seer
2025-04-03 7:02 ` Krzysztof Kozlowski
2025-04-03 7:11 ` Paller, Kim Seer
2025-04-03 7:22 ` Krzysztof Kozlowski
2025-04-03 7:22 ` Krzysztof Kozlowski
2025-04-03 11:15 ` Nuno Sá
2025-04-04 16:28 ` David Lechner [this message]
2025-04-03 5:33 ` [PATCH v3 3/3] iio: dac: ad3530r: Add driver for AD3530R and AD3531R Kim Seer Paller
2025-04-03 11:31 ` Nuno Sá
2025-04-04 17:48 ` David Lechner
2025-04-07 8:01 ` Paller, Kim Seer
2025-04-08 14:06 ` David Lechner
2025-04-10 8:39 ` Paller, Kim Seer
2025-04-10 14:11 ` David Lechner
2025-04-05 16:11 ` Jonathan Cameron
2025-04-07 8:07 ` Paller, Kim Seer
2025-04-03 6:43 ` [PATCH v3 0/3] Add driver for AD3530R and AD3531R DACs Krzysztof Kozlowski
2025-04-03 6:58 ` Paller, Kim Seer
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=dcb9c90f-480d-456e-ab01-d68171356050@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kimseer.paller@analog.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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