From: Taha Ed-Dafili <0rayn.dev@gmail.com>
To: dlechner@baylibre.com
Cc: 0rayn.dev@gmail.com, Michael.Hennerich@analog.com,
andy@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
jic23@kernel.org, krzk+dt@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@analog.com, nuno.sa@analog.com, robh@kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v6 6/6] iio: dac: ad5504: support scale via output-range-microvolt property
Date: Sat, 22 Aug 2026 15:45:05 -0400 [thread overview]
Message-ID: <20260822194505.20389-1-0rayn.dev@gmail.com> (raw)
In-Reply-To: <fb0b857e-eac8-4755-9330-5cfe55523271@baylibre.com>
> 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.
>
> Either return an error here that it is not supported. Or implement
> it by making IIO_CHAN_INFO_SCALE writable.
Thank you for catching that. For now I'll return an error in that
case, we can always expand it later if needed.
Best Regards,
Taha Ed-Dafili
prev parent reply other threads:[~2026-08-22 19:45 UTC|newest]
Thread overview: 14+ 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 9:10 ` sashiko-bot
2026-08-22 18:24 ` David Lechner
2026-08-22 19:45 ` Taha Ed-Dafili [this message]
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=20260822194505.20389-1-0rayn.dev@gmail.com \
--to=0rayn.dev@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.