From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7476: Support ROHM BU79100G
Date: Sat, 31 May 2025 16:42:58 +0100 [thread overview]
Message-ID: <20250531164258.47f0d1a2@jic23-huawei> (raw)
In-Reply-To: <aDk2qNE9LTVnfAFM@mva-rohm>
On Fri, 30 May 2025 07:40:08 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> ROHM BU79100G is a 12-bit, single channel ADC. From the software point
> of view it is identical to the TI's ADS7866. Support reading ADC
> measurements using the ad7476.c
>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
Applied.
> ---
>
> Please, see the relevant discussion (as to why an ID for a fallback is
> added) in:
> https://lore.kernel.org/all/f8ec547a-5924-4563-aa1d-dde8227844fa@gmail.com/
>
> This patch was based on v6.15-rc1. I can rebase if needed.
>
> drivers/iio/adc/ad7476.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/iio/adc/ad7476.c b/drivers/iio/adc/ad7476.c
> index 37b0515cf4fc..d48ee8f1d547 100644
> --- a/drivers/iio/adc/ad7476.c
> +++ b/drivers/iio/adc/ad7476.c
> @@ -435,6 +435,13 @@ static const struct spi_device_id ad7476_id[] = {
> { "ads7866", ID_ADS7866 },
> { "ads7867", ID_ADS7867 },
> { "ads7868", ID_ADS7868 },
> + /*
> + * The ROHM BU79100G is identical to the TI's ADS7866 from the software
> + * point of view. The binding document mandates the ADS7866 to be
> + * marked as a fallback for the BU79100G, but we still need the SPI ID
> + * here to make the module loading work.
> + */
> + { "bu79100g", ID_ADS7866 },
> { "ltc2314-14", ID_LTC2314_14 },
> { }
> };
prev parent reply other threads:[~2025-05-31 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 4:40 [PATCH] iio: adc: ad7476: Support ROHM BU79100G Matti Vaittinen
2025-05-31 15:42 ` 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=20250531164258.47f0d1a2@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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