From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7124: add ext attributes to temperature channel
Date: Sat, 27 Sep 2025 19:20:10 +0100 [thread overview]
Message-ID: <20250927192010.6d6427a3@jic23-huawei> (raw)
In-Reply-To: <20250923-iio-adc-ad7124-add-ext-attributes-to-temperature-channel-v1-1-173baac28169@baylibre.com>
On Tue, 23 Sep 2025 15:33:18 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Use the same .ext_info for the temperature channel as for the voltage
> channels. In the ADC, these all go though a mux to select the source
> and otherwise operate the same.
>
> These attributes probably won't be used much, but since it is trivial
> to add this, we might as well include them.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Seems unlikely this with clash with the fixes in flight so
applied to the testing branch of iio.git
Thanks,
Jonathan
> ---
> drivers/iio/adc/ad7124.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c
> index 374e39736584f55c1290db3e257dff2c60f884d2..7ed31399a875b76be08491f56acff55032c95ced 100644
> --- a/drivers/iio/adc/ad7124.c
> +++ b/drivers/iio/adc/ad7124.c
> @@ -1348,6 +1348,7 @@ static int ad7124_parse_channel_config(struct iio_dev *indio_dev,
> },
> .address = num_channels,
> .scan_index = num_channels,
> + .ext_info = ad7124_calibsys_ext_info,
> };
> }
>
>
> ---
> base-commit: 411e8b72c181e4f49352c12ced0fd8426eb683aa
> change-id: 20250923-iio-adc-ad7124-add-ext-attributes-to-temperature-channel-dd963150dea9
>
> Best regards,
prev parent reply other threads:[~2025-09-27 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 20:33 David Lechner
2025-09-27 18:20 ` Jonathan Cameron [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=20250927192010.6d6427a3@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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®