From: David Lechner <dlechner@baylibre.com>
To: "Nicolás Antinori" <nico.antinori.7@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Brigham Campbell" <me@brighamcampbell.com>,
"Jori Koolstra" <jkoolstra@xs4all.nl>,
"Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2] iio: humidity: am2315: add am2320 to i2c_device_id table
Date: Mon, 10 Aug 2026 14:28:26 -0500 [thread overview]
Message-ID: <ebca396e-1ff4-4723-b46c-de407b051767@baylibre.com> (raw)
In-Reply-To: <20260810183337.451812-1-nico.antinori.7@gmail.com>
On 8/10/26 1:32 PM, Nicolás Antinori wrote:
> The AM2320 is fully compatible with the AM2315 sensor in terms of I2C
> communication protocol and measurement conversions.
>
> Add the "am2320" entry to the i2c_device_id table.
Interesting. No devicetree bindings for this one? What kind of
system is it on?
>
> Signed-off-by: Nicolás Antinori <nico.antinori.7@gmail.com>
> ---
> v2:
> - Adapted KConfig text using the suggestions from v1 by Nuno Sá and Andy
> Shevchenko
>
> v1: https://lore.kernel.org/all/20260805183733.1000550-1-nico.antinori.7@gmail.com/T/#u
>
> drivers/iio/humidity/Kconfig | 8 +++++---
> drivers/iio/humidity/am2315.c | 3 ++-
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/humidity/Kconfig b/drivers/iio/humidity/Kconfig
> index 54f11f000b6f..10598a0b15bc 100644
> --- a/drivers/iio/humidity/Kconfig
> +++ b/drivers/iio/humidity/Kconfig
> @@ -5,13 +5,15 @@
> menu "Humidity sensors"
>
> config AM2315
> - tristate "Aosong AM2315 relative humidity and temperature sensor"
> + tristate "Aosong AM2315 and similar relative humidity and temperature sensor"
> depends on I2C
> select IIO_BUFFER
> select IIO_TRIGGERED_BUFFER
> help
> - If you say yes here you get support for the Aosong AM2315
> - relative humidity and ambient temperature sensor.
> + If you say yes here you get support for the Aosong relative
> + humidity and ambient temperature sensors:
> + - AM2315
> + - AM2320
>
> This driver can also be built as a module. If so, the module will
> be called am2315.
> diff --git a/drivers/iio/humidity/am2315.c b/drivers/iio/humidity/am2315.c
> index f29baa251f9f..5bce5eec45cc 100644
> --- a/drivers/iio/humidity/am2315.c
> +++ b/drivers/iio/humidity/am2315.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0-only
> /*
> - * Aosong AM2315 relative humidity and temperature
> + * Aosong AM2315 and similar relative humidity and temperature
> *
> * Copyright (c) 2016, Intel Corporation.
> *
> @@ -251,6 +251,7 @@ static int am2315_probe(struct i2c_client *client)
>
> static const struct i2c_device_id am2315_i2c_id[] = {
> { .name = "am2315" },
> + { .name = "am2320" },
> { }
> };
> MODULE_DEVICE_TABLE(i2c, am2315_i2c_id);
> --
> 2.47.3
>
Currently, the driver sets `indio_dev->name = AM2315_DRIVER_NAME;`
Usually, when there is more than one chip supported in a driver, we
want this to be the the name of the actual chip.
(And we usually try to avoid DRIVER_NAME macros so removing that
would be a welcome change.)
next prev parent reply other threads:[~2026-08-10 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 18:32 [PATCH v2] iio: humidity: am2315: add am2320 to i2c_device_id table Nicolás Antinori
2026-08-10 18:53 ` Andy Shevchenko
2026-08-10 19:28 ` David Lechner [this message]
2026-08-11 2:36 ` Marcelo Schmitt
2026-08-11 7:38 ` Andy Shevchenko
2026-08-11 15:12 ` Nicolás Antinori
2026-08-11 15:49 ` David Lechner
2026-08-11 17:58 ` Nicolás Antinori
2026-08-11 18:06 ` David Lechner
2026-08-12 4:43 ` Jonathan Cameron
2026-08-12 15:56 ` Nicolás Antinori
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=ebca396e-1ff4-4723-b46c-de407b051767@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=me@brighamcampbell.com \
--cc=nico.antinori.7@gmail.com \
--cc=nuno.sa@analog.com \
--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.