From: "Nicolás Antinori" <nico.antinori.7@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Nicolás Antinori" <nico.antinori.7@gmail.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Brigham Campbell" <me@brighamcampbell.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Jori Koolstra" <jkoolstra@xs4all.nl>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Rob Herring" <robh@kernel.org>,
"Shuah Khan" <skhan@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: [PATCH v4 0/2] add support for Aosong AM2320
Date: Thu, 20 Aug 2026 11:31:08 -0300 [thread overview]
Message-ID: <cover.1786973355.git.nico.antinori.7@gmail.com> (raw)
The AM2320 is fully compatible with the AM2315 sensor in terms of I2C
communication protocol and measurement conversions.
This patch series adds am2320 to the i2c_device_id table, creates
of_device_id table and adds both am2315 and am2320 to
trivial-devices.yml dt bindings.
v4:
- Addressed minor styling issues in driver's C code pointed by Andy Shevchenko
(carried "Reviewed-by: Andy Shevchenko <...> from v3)
- Adapted commit message pointed by Marcelo Schmitt (carried
"Reviewed-by: Marcelo Schmitt <...>" from v3)
- Carried Acked-by: "Krzysztof Kozlowski <...>: from v3 dt-bindings patch
since bindings patch did not change.
Note: I carried tags from v3 because reviewers declared the tag after
pointing things that were resolved in v4 (and the dt-bindings one
because the patch did not change from v3 to v4). If this is a mistake
please let me know.
v3: [3]
- Added "aosong,am2315" and "aosong,am2320" to trivial-devices.yml.
- Added of_device_id table.
- Replaced using a constant for driver's name with chip_info struct.
- Separated code changes and dt-bindings changes in two commits.
v2: [2]
- Generalized KConfig description text.
v1: [1]
[1] https://lore.kernel.org/all/20260805183733.1000550-1-nico.antinori.7@gmail.com/T/#u
[2] https://lore.kernel.org/all/20260810183337.451812-1-nico.antinori.7@gmail.com/T/#u
[3] https://lore.kernel.org/all/cover.1786725567.git.nico.antinori.7@gmail.com/
Nicolás Antinori (2):
dt-bindings: trivial-devices: add Aosong AM2315 and AM2320 chips
iio: humidity: am2315: add support for am2320
.../devicetree/bindings/trivial-devices.yaml | 2 ++
drivers/iio/humidity/Kconfig | 8 +++--
drivers/iio/humidity/am2315.c | 34 ++++++++++++++++---
3 files changed, 36 insertions(+), 8 deletions(-)
--
2.47.3
next reply other threads:[~2026-08-20 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 14:31 Nicolás Antinori [this message]
2026-08-20 14:31 ` [PATCH v4 1/2] dt-bindings: trivial-devices: add Aosong AM2315 and AM2320 chips Nicolás Antinori
2026-08-20 14:31 ` [PATCH v4 2/2] iio: humidity: am2315: add support for am2320 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=cover.1786973355.git.nico.antinori.7@gmail.com \
--to=nico.antinori.7@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=krzk+dt@kernel.org \
--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=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