From: Antoniu Miclaus <antoniu.miclaus@analog.com>
To: "Michael Hennerich" <michael.hennerich@analog.com>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Petre Rodan" <petre.rodan@subdimension.ro>,
"Jorge Marques" <jorge.marques@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/4] iio: accel: adxl372: add ADXL371 support
Date: Sat, 21 Mar 2026 12:04:55 +0200 [thread overview]
Message-ID: <20260321100729.2440-1-antoniu.miclaus@analog.com> (raw)
Add support for the Analog Devices ADXL371 3-axis, +-200g MEMS
accelerometer to the existing ADXL372 IIO driver. The ADXL371 shares
the same register map as the ADXL372 but differs in ODR/bandwidth
values, timer scale factors, and has a known silicon anomaly (er001)
that prevents reliable FIFO operation.
Changes in v4:
- [Patch 1/4] Reformat info_mask_shared_by_type to use consistent
multi-line style matching info_mask_shared_by_type_available.
- [Patch 1/4] Drop trailing comma from ADXL372_ODR_NUM enum
terminator.
- [Patch 1/4] Drop redundant NULL checks for chip_info in SPI/I2C
probe functions since match data is always provided.
- [Patch 3/4] Use 'if (ret)' instead of 'if (ret < 0)' for
devm_iio_trigger_register() and devm_iio_triggered_buffer_setup_ext()
return checks in adxl372_buffer_setup().
- [Patch 4/4] Drop trailing comma from ADXL371_ODR_NUM enum
terminator.
Antoniu Miclaus (4):
iio: accel: adxl372: introduce chip_info structure
dt-bindings: iio: accel: adi,adxl372: add ADXL371 compatible
iio: accel: adxl372: factor out buffer and trigger setup
iio: accel: adxl372: add support for ADXL371
.../bindings/iio/accel/adi,adxl372.yaml | 9 +-
MAINTAINERS | 5 +-
drivers/iio/accel/Kconfig | 12 +-
drivers/iio/accel/adxl372.c | 300 +++++++++++-------
drivers/iio/accel/adxl372.h | 20 +-
drivers/iio/accel/adxl372_i2c.c | 17 +-
drivers/iio/accel/adxl372_spi.c | 17 +-
7 files changed, 244 insertions(+), 136 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-21 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 10:04 Antoniu Miclaus [this message]
2026-03-21 10:04 ` [PATCH v4 1/4] iio: accel: adxl372: introduce chip_info structure Antoniu Miclaus
2026-03-21 11:13 ` Jonathan Cameron
2026-03-21 10:04 ` [PATCH v4 2/4] dt-bindings: iio: accel: adi,adxl372: add ADXL371 compatible Antoniu Miclaus
2026-03-21 10:04 ` [PATCH v4 3/4] iio: accel: adxl372: factor out buffer and trigger setup Antoniu Miclaus
2026-03-21 11:18 ` Jonathan Cameron
2026-03-21 10:04 ` [PATCH v4 4/4] iio: accel: adxl372: add support for ADXL371 Antoniu Miclaus
2026-03-21 11:25 ` [PATCH v4 0/4] iio: accel: adxl372: add ADXL371 support Jonathan Cameron
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=20260321100729.2440-1-antoniu.miclaus@analog.com \
--to=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=petre.rodan@subdimension.ro \
--cc=robh@kernel.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