From: David Lechner <dlechner@baylibre.com>
To: Taha Ed-Dafili <0rayn.dev@gmail.com>,
linux-iio@vger.kernel.org, jic23@kernel.org
Cc: rdunlap@infradead.org, skhan@linuxfoundation.org,
linux-kernel-mentees-archive@lists.linuxfoundation.org,
nuno.sa@analog.com, andy@kernel.org, corbet@lwn.net,
lars@metafoo.de, Michael.Hennerich@analog.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] iio: accel: adxl345: Implement event scaling for ABI compliance
Date: Sat, 21 Feb 2026 10:47:34 -0600 [thread overview]
Message-ID: <e2c74e7f-d851-457f-88f8-d80a8d17c51f@baylibre.com> (raw)
In-Reply-To: <20260221141251.34855-4-0rayn.dev@gmail.com>
On 2/21/26 8:12 AM, Taha Ed-Dafili wrote:
> The ADXL345 uses a fixed threshold resolution of 62.5 mg/LSB for
> event-related registers. Previously, the driver reported raw
> values without a scale factor.
>
> Implement IIO_EV_INFO_SCALE for all event types to provide the
> conversion factor (0.612915 m/s^2) as required by the IIO ABI.
>
> Consequently, remove the obsolete comment in adxl345_read_event_value()
> which stated that the scale factor is not applied.
>
> Add explicit write rejection for IIO_EV_INFO_SCALE in
> adxl345_write_event_value() returning -EINVAL.
>
> Suggested-by: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Taha Ed-Dafili <0rayn.dev@gmail.com>
> ---
> drivers/iio/accel/adxl345_core.c | 37 ++++++++++++++++++++++----------
> 1 file changed, 26 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/iio/accel/adxl345_core.c b/drivers/iio/accel/adxl345_core.c
> index 78e3f799ecc1..eac4ab052fa2 100644
> --- a/drivers/iio/accel/adxl345_core.c
> +++ b/drivers/iio/accel/adxl345_core.c
> @@ -213,7 +213,8 @@ static const struct iio_event_spec adxl345_events[] = {
> .dir = IIO_EV_DIR_RISING,
> .mask_shared_by_type =
> BIT(IIO_EV_INFO_ENABLE) |
> - BIT(IIO_EV_INFO_VALUE),
> + BIT(IIO_EV_INFO_VALUE) |
> + BIT(IIO_EV_INFO_SCALE),
> },
> {
> /* activity, ac bit set */
> @@ -221,22 +222,27 @@ static const struct iio_event_spec adxl345_events[] = {
> .dir = IIO_EV_DIR_RISING,
> .mask_shared_by_type =
> BIT(IIO_EV_INFO_ENABLE) |
> - BIT(IIO_EV_INFO_VALUE),
> + BIT(IIO_EV_INFO_VALUE) |
> + BIT(IIO_EV_INFO_SCALE),
> },
> {
> /* single tap */
> .type = IIO_EV_TYPE_GESTURE,
> .dir = IIO_EV_DIR_SINGLETAP,
> .mask_separate = BIT(IIO_EV_INFO_ENABLE),
> - .mask_shared_by_type = BIT(IIO_EV_INFO_VALUE) |
> + .mask_shared_by_type =
> + BIT(IIO_EV_INFO_VALUE) |
> + BIT(IIO_EV_INFO_SCALE) |
> BIT(IIO_EV_INFO_TIMEOUT),
> },
> {
> /* double tap */
> .type = IIO_EV_TYPE_GESTURE,
> .dir = IIO_EV_DIR_DOUBLETAP,
> - .mask_shared_by_type = BIT(IIO_EV_INFO_ENABLE) |
> - BIT(IIO_EV_INFO_RESET_TIMEOUT) |
> + .mask_shared_by_type =
> + BIT(IIO_EV_INFO_ENABLE) |
> + BIT(IIO_EV_INFO_SCALE) |
I still question this one. Why do we have a IIO_EV_INFO_SCALE with no
IIO_EV_INFO_VALUE?
The docs say:
| in_accel_gesture_doubletap_scale | Double tap gesture threshold scale. |
But there is no attribute labeled "Double tap gesture threshold" that it
could be referring to.
> + BIT(IIO_EV_INFO_RESET_TIMEOUT) |
> BIT(IIO_EV_INFO_TAP2_MIN_DELAY),
> },
> };ret = adxl345_write_mag_value(st, dir, info,
next prev parent reply other threads:[~2026-02-21 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 14:12 [PATCH v4 0/4] iio: accel: adxl345: Implement event scaling and " Taha Ed-Dafili
2026-02-21 14:12 ` [PATCH v4 1/4] docs: iio: adxl345: fix typos and grammar Taha Ed-Dafili
2026-02-21 14:12 ` [PATCH v4 2/4] iio: core: Add IIO_EV_INFO_SCALE to event info Taha Ed-Dafili
2026-02-21 14:12 ` [PATCH v4 3/4] iio: accel: adxl345: Implement event scaling for ABI compliance Taha Ed-Dafili
2026-02-21 16:47 ` David Lechner [this message]
2026-02-21 17:21 ` Taha Ed-Dafili
2026-02-22 16:11 ` Jonathan Cameron
2026-02-21 14:12 ` [PATCH v4 4/4] docs: iio: adxl345: update math and examples for scaling Taha Ed-Dafili
2026-02-21 16:50 ` David Lechner
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=e2c74e7f-d851-457f-88f8-d80a8d17c51f@baylibre.com \
--to=dlechner@baylibre.com \
--cc=0rayn.dev@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees-archive@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®