From: David Lechner <dlechner@baylibre.com>
To: Taha Ed-Dafili <0rayn.dev@gmail.com>, jic23@kernel.org, lars@metafoo.de
Cc: Michael.Hennerich@analog.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, nuno.sa@analog.com,
andy@kernel.org, skhan@linuxfoundation.org, linux@analog.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 6/6] iio: dac: ad5504: support scale via output-range-microvolt property
Date: Sat, 22 Aug 2026 13:24:29 -0500 [thread overview]
Message-ID: <fb0b857e-eac8-4755-9330-5cfe55523271@baylibre.com> (raw)
In-Reply-To: <20260822085850.17527-7-0rayn.dev@gmail.com>
On 8/22/26 3:56 AM, Taha Ed-Dafili wrote:
> The AD5504 output range is set by the R_SEL pin, not the VCC supply.
> Add support for 'output-range-microvolt' to set vref_mv directly from
> firmware. Use device_property_present() to distinguish absent from
> malformed property rather than relying on the ambiguous -EINVAL from
> device_property_read_u32_array(). Fall back to the vcc regulator
> voltage for old DTs that predate this property.
>
> Signed-off-by: Taha Ed-Dafili <0rayn.dev@gmail.com>
> ---
> drivers/iio/dac/ad5504.c | 31 +++++++++++++++++++++++++------
> 1 file changed, 25 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/dac/ad5504.c b/drivers/iio/dac/ad5504.c
> index 74679feea385..d0a3dd4b000d 100644
> --- a/drivers/iio/dac/ad5504.c
> +++ b/drivers/iio/dac/ad5504.c
> @@ -300,6 +300,7 @@ static int ad5504_probe(struct spi_device *spi)
> struct device *dev = &spi->dev;
> struct iio_dev *indio_dev;
> struct ad5504_state *st;
> + u32 range[2];
> int ret;
>
> indio_dev = devm_iio_device_alloc(dev, sizeof(*st));
> @@ -315,12 +316,30 @@ static int ad5504_probe(struct spi_device *spi)
> if (is_acpi_device_node(dev_fwnode(dev))) {
> st->vref_mv = AD5504_VREF_ACPI_DEFAULT_mV;
> } else {
> - ret = devm_regulator_get_enable_read_voltage(dev, "vcc");
> - if (ret < 0)
> - return dev_err_probe(dev, ret,
> - "Failed to get vcc regulator\n");
> -
> - st->vref_mv = ret / 1000;
> + if (device_property_present(dev, "output-range-microvolt")) {
> + ret = device_property_read_u32_array(dev, "output-range-microvolt",
> + range, ARRAY_SIZE(range));
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "Error parsing output-range-microvolt\n");
> +
> + if (range[0] != 0 || (range[1] != 30 * MICRO && range[1] != 60 * MICRO))
> + return dev_err_probe(dev, -EINVAL,
> + "Invalid output-range-microvolt\n");
> +
> + st->vref_mv = range[1] / (MICRO / MILLI);
> +
> + ret = devm_regulator_get_enable(dev, "vcc");
> + if (ret < 0)
> + return dev_err_probe(dev, ret, "Failed to enable vcc regulator\n");
We should probably handle range-sel-gpios here. Otherwise, if a new DT tries
to use it, it will end up falling back to this old wrong behavior.
} else if (device_property_present("range-sel-gpios")) {
Either return an error here that it is not supported. Or implement it by
making IIO_CHAN_INFO_SCALE writable.
> + } else {
> + /* Backward compat: old DTs without output-range-microvolt */
> + ret = devm_regulator_get_enable_read_voltage(dev, "vcc");
> + if (ret < 0)
> + return dev_err_probe(dev, ret, "Failed to get vcc regulator\n");
> +
> + st->vref_mv = ret / (MICRO / MILLI);
> + }
> }
>
> st->spi = spi;
next prev parent reply other threads:[~2026-08-22 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 8:56 [PATCH v6 0/6] iio: dac: ad5504: bindings, cleanups, locking, and scale fixes Taha Ed-Dafili
2026-08-22 8:56 ` [PATCH v6 1/6] dt-bindings: iio: dac: ad5504: add output-range and missing gpios Taha Ed-Dafili
2026-08-22 18:20 ` David Lechner
2026-08-22 19:36 ` Taha Ed-Dafili
2026-08-22 22:37 ` David Lechner
2026-08-23 1:36 ` Jonathan Cameron
2026-08-22 8:56 ` [PATCH v6 2/6] iio: dac: ad5504: Align headers with IWYU principle Taha Ed-Dafili
2026-08-22 8:56 ` [PATCH v6 3/6] iio: dac: ad5504: separate ACPI and DT paths Taha Ed-Dafili
2026-08-22 8:56 ` [PATCH v6 4/6] iio: dac: ad5504: remove legacy platform data support Taha Ed-Dafili
2026-08-22 8:56 ` [PATCH v6 5/6] iio: dac: ad5504: introduce local lock to protect state and spi transfers Taha Ed-Dafili
2026-08-22 8:56 ` [PATCH v6 6/6] iio: dac: ad5504: support scale via output-range-microvolt property Taha Ed-Dafili
2026-08-22 18:24 ` David Lechner [this message]
2026-08-22 19:45 ` Taha Ed-Dafili
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=fb0b857e-eac8-4755-9330-5cfe55523271@baylibre.com \
--to=dlechner@baylibre.com \
--cc=0rayn.dev@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®