From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Santos <Jonathan.Santos@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Michael.Hennerich@analog.com>,
<ramona.gradinariu@analog.com>, <antoniu.miclaus@analog.com>,
<dlechner@baylibre.com>, <nuno.sa@analog.com>, <andy@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Subject: Re: [PATCH 2/2] iio: accel: adxl380: add support for ADXL318 and ADXL319
Date: Sun, 9 Nov 2025 16:50:55 +0000 [thread overview]
Message-ID: <20251109165055.404d0417@jic23-huawei> (raw)
In-Reply-To: <7d990c72acca31b2fe6c7685fd13ef5284c7646f.1762281527.git.Jonathan.Santos@analog.com>
On Wed, 5 Nov 2025 09:40:34 -0300
Jonathan Santos <Jonathan.Santos@analog.com> wrote:
> The ADXL318 and ADXL319 are low noise density, low power, 3-axis
> accelerometers based on ADXL380 and ADXL382, respectively. The main
> difference between the new parts and the existing ones are the absence
> of interrupts and events like tap detection, activity/inactivity, and
> free-fall detection.
>
> Other differences in the new parts are fewer power modes, basically
> allowing only idle and measurement modes, and the removal of the 12-bit
> SAR ADC path for the 3-axis signals (known as lower signal chain),
> being excluisive for the temperature sensor in the ADXL318/319.
>
> Signed-off-by: Jonathan Santos <Jonathan.Santos@analog.com>
Only comments are about numeric order, similar to the comments on
the dt-binding.
Thanks,
Jonathan
> ---
> drivers/iio/accel/adxl380.c | 134 ++++++++++++++++++++++----------
> drivers/iio/accel/adxl380.h | 4 +
> drivers/iio/accel/adxl380_i2c.c | 4 +
> drivers/iio/accel/adxl380_spi.c | 4 +
> 4 files changed, 107 insertions(+), 39 deletions(-)
>
> diff --git a/drivers/iio/accel/adxl380.c b/drivers/iio/accel/adxl380.c
> index 0cf3c6815829..7733a0902afa 100644
> --- a/drivers/iio/accel/adxl380.c
> +++ b/drivers/iio/accel/adxl380.c
> @@ -27,6 +27,8 @@
>
> #define ADXL380_ID_VAL 380
> #define ADXL382_ID_VAL 382
> +#define ADXL318_ID_VAL 380
> +#define ADXL319_ID_VAL 382
Similar to the binding. Sort these by number.
>
> #define ADXL380_DEVID_AD_REG 0x00
> #define ADLX380_PART_ID_REG 0x02
> @@ -178,41 +180,6 @@ enum adxl380_tap_time_type {
> +
> +const struct adxl380_chip_info adxl382_chip_info = {
> + .name = "adxl382",
> + .chip_id = ADXL382_ID_VAL,
> + .scale_tbl = {
> + [ADXL382_OP_MODE_15G_RANGE] = { 0, 4903325 },
> + [ADXL382_OP_MODE_30G_RANGE] = { 0, 9806650 },
> + [ADXL382_OP_MODE_60G_RANGE] = { 0, 19613300 },
> + },
> + .samp_freq_tbl = { 16000, 32000, 64000 },
> + /*
> + * The datasheet defines an intercept of 570 LSB at 25 degC
> + * and a sensitivity of 10.2 LSB/C.
> + */
> + .temp_offset = 25 * 102 / 10 - 570,
> + .has_low_power = true,
> + .info = &adxl380_info,
> +};
> +EXPORT_SYMBOL_NS_GPL(adxl382_chip_info, "IIO_ADXL380");
> +
> +const struct adxl380_chip_info adxl318_chip_info = {
> + .name = "adxl318",
> + .chip_id = ADXL318_ID_VAL,
> + .scale_tbl = {
> + [ADXL380_OP_MODE_4G_RANGE] = { 0, 1307226 },
> + [ADXL380_OP_MODE_8G_RANGE] = { 0, 2615434 },
> + [ADXL380_OP_MODE_16G_RANGE] = { 0, 5229886 },
> + },
> + .samp_freq_tbl = { 8000, 16000, 32000 },
> + /*
> + * The datasheet defines an intercept of 550 LSB at 25 degC
> + * and a sensitivity of 10.2 LSB/C.
> + */
> + .temp_offset = 25 * 102 / 10 - 550,
> + .info = &adxl318_info,
> +};
> +EXPORT_SYMBOL_NS_GPL(adxl318_chip_info, "IIO_ADXL380");
> +
> +const struct adxl380_chip_info adxl319_chip_info = {
Numeric order preferred for these structures as well.
There might have been some argument for grouping by ID but that
doesn't seem to be the case either here.
> + .name = "adxl319",
> + .chip_id = ADXL319_ID_VAL,
> + .scale_tbl = {
> + [ADXL382_OP_MODE_15G_RANGE] = { 0, 4903325 },
> + [ADXL382_OP_MODE_30G_RANGE] = { 0, 9806650 },
> + [ADXL382_OP_MODE_60G_RANGE] = { 0, 19613300 },
> + },
> + .samp_freq_tbl = { 16000, 32000, 64000 },
> + /*
> + * The datasheet defines an intercept of 550 LSB at 25 degC
> + * and a sensitivity of 10.2 LSB/C.
> + */
> + .temp_offset = 25 * 102 / 10 - 550,
> + .info = &adxl318_info,
> +};
> +EXPORT_SYMBOL_NS_GPL(adxl319_chip_info, "IIO_ADXL380");
> diff --git a/drivers/iio/accel/adxl380.h b/drivers/iio/accel/adxl380.h
> index a683625d897a..5d88c111d616 100644
> --- a/drivers/iio/accel/adxl380.h
> +++ b/drivers/iio/accel/adxl380.h
>
> extern const struct adxl380_chip_info adxl380_chip_info;
> extern const struct adxl380_chip_info adxl382_chip_info;
> +extern const struct adxl380_chip_info adxl318_chip_info;
> +extern const struct adxl380_chip_info adxl319_chip_info;
Sort numerically.
next prev parent reply other threads:[~2025-11-09 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 12:40 [PATCH 1/2] dt-bindings: iio: accel: adxl380: add new supported parts Jonathan Santos
2025-11-05 12:40 ` [PATCH 2/2] iio: accel: adxl380: add support for ADXL318 and ADXL319 Jonathan Santos
2025-11-05 15:11 ` Andy Shevchenko
2025-11-09 16:50 ` Jonathan Cameron [this message]
2025-11-06 9:04 ` [PATCH 1/2] dt-bindings: iio: accel: adxl380: add new supported parts Krzysztof Kozlowski
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=20251109165055.404d0417@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.gradinariu@analog.com \
--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