From: Jonathan Cameron <jic23@kernel.org>
To: Kim Seer Paller <kimseer.paller@analog.com>
Cc: "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>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <noname.nuno@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/3] iio: dac: ad3530r: Add driver for AD3530R and AD3531R
Date: Sat, 12 Apr 2025 18:44:33 +0100 [thread overview]
Message-ID: <20250412184433.58f0a9d5@jic23-huawei> (raw)
In-Reply-To: <20250412-togreg-v4-3-cb9e5309b99d@analog.com>
On Sat, 12 Apr 2025 13:57:32 +0800
Kim Seer Paller <kimseer.paller@analog.com> wrote:
> The AD3530/AD3530R (8-channel) and AD3531/AD3531R (4-channel) are
> low-power, 16-bit, buffered voltage output 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.
>
> Support for monitoring internal die temperature, output voltages, and
> current of a selected channel via the MUXOUT pin using an external ADC
> is currently not implemented.
>
> Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
Hi,
One really small comment from me. Otherwise this just needs
to sit on list for a little while to give other reviewers time.
If nothing else comes up I may just tweak the thing below (or leave
it alone!)
Thanks,
Jonathan
> diff --git a/drivers/iio/dac/ad3530r.c b/drivers/iio/dac/ad3530r.c
> new file mode 100644
> index 0000000000000000000000000000000000000000..ffa04f678b86d8da6f5e47c35c265b6648121843
> --- /dev/null
> +++ b/drivers/iio/dac/ad3530r.c
> @@ -0,0 +1,506 @@
...
> +static int ad3530r_probe(struct spi_device *spi)
> +{
...
> + vref = devm_regulator_get_enable_read_voltage(dev, "ref");
> + if (vref < 0 && vref != -ENODEV)
> + return vref;
> +
> + has_external_vref = vref != -ENODEV;
> +
> + if (!st->chip_info->internal_ref_support && !has_external_vref)
> + return vref;
If doing a v5 I'd go with
return -ENODEV;
rather than having people scratch their heads to figure out what is in vref.
> +
next prev parent reply other threads:[~2025-04-12 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 5:57 [PATCH v4 0/3] Add driver for AD3530R and AD3531R DACs Kim Seer Paller
2025-04-12 5:57 ` [PATCH v4 1/3] iio: ABI: add new DAC powerdown mode Kim Seer Paller
2025-04-12 5:57 ` [PATCH v4 2/3] dt-bindings: iio: dac: Add adi,ad3530r.yaml Kim Seer Paller
2025-04-12 5:57 ` [PATCH v4 3/3] iio: dac: ad3530r: Add driver for AD3530R and AD3531R Kim Seer Paller
2025-04-12 17:44 ` Jonathan Cameron [this message]
2025-04-16 19:23 ` David Lechner
2025-04-18 14:37 ` Jonathan Cameron
2025-04-16 19:24 ` [PATCH v4 0/3] Add driver for AD3530R and AD3531R DACs David Lechner
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=20250412184433.58f0a9d5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--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