From: David Lechner <dlechner@baylibre.com>
To: "Francesco Lavra" <flavra@baylibre.com>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v8 6/6] iio: imu: st_lsm6dsx: Add support for rotation sensor
Date: Sat, 21 Mar 2026 12:46:47 -0500 [thread overview]
Message-ID: <e1b3e1e5-6073-4ddc-a0f4-2834ce6c29f7@baylibre.com> (raw)
In-Reply-To: <20260317150427.3878450-1-flavra@baylibre.com>
On 3/17/26 10:04 AM, Francesco Lavra wrote:
> Some IMU chips in the LSM6DSX family have sensor fusion features that
> combine data from the accelerometer and gyroscope. One of these features
> generates rotation vector data and makes it available in the hardware
> FIFO as a quaternion (more specifically, the X, Y and Z components of the
> quaternion vector, expressed as 16-bit half-precision floating-point
> numbers).
>
> Add support for a new sensor instance that allows receiving sensor fusion
> data, by defining a new struct st_lsm6dsx_fusion_settings (which contains
> chip-specific details for the sensor fusion functionality), and adding this
> struct as a new field in struct st_lsm6dsx_settings. In st_lsm6dsx_core.c,
> populate this new struct for the LSM6DSV and LSM6DSV16X chips, and add the
> logic to initialize an additional IIO device if this struct is populated
> for the hardware type being probed.
> Note: a new IIO device is being defined (as opposed to adding channels to
> an existing device) because the rate at which sensor fusion data is
> generated may not match the data rate from any of the existing devices.
>
> Tested on LSMDSV16X.
>
We should mention that this depends on [1] to get the correct sizing
of the buffer in userspace.
[1]: https://lore.kernel.org/linux-iio/20260307-iio-fix-timestamp-alignment-v2-4-d1d48fbadbbf@baylibre.com/
next prev parent reply other threads:[~2026-03-21 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 15:03 [PATCH v8 0/6] " Francesco Lavra
2026-03-17 15:03 ` [PATCH v8 1/6] iio: imu: st_lsm6dsx: Fix check for invalid samples from FIFO Francesco Lavra
2026-03-17 15:04 ` [PATCH v8 2/6] iio: Replace 'sign' field with union in struct iio_scan_type Francesco Lavra
2026-03-21 17:22 ` David Lechner
2026-03-23 16:04 ` Francesco Lavra
2026-03-23 16:08 ` David Lechner
2026-03-23 16:49 ` Andy Shevchenko
2026-03-23 17:37 ` Francesco Lavra
2026-03-24 11:04 ` Andy Shevchenko
2026-03-24 11:42 ` Francesco Lavra
2026-03-24 11:52 ` Andy Shevchenko
2026-03-17 15:04 ` [PATCH v8 3/6] iio: tools: Add support for floating-point types in buffer scan elements Francesco Lavra
2026-03-21 17:26 ` David Lechner
2026-03-17 15:04 ` [PATCH v8 4/6] iio: ABI: Add support for floating-point numbers " Francesco Lavra
2026-03-17 15:04 ` [PATCH v8 5/6] iio: ABI: Add quaternion axis modifier Francesco Lavra
2026-03-21 17:29 ` David Lechner
2026-03-17 15:04 ` [PATCH v8 6/6] iio: imu: st_lsm6dsx: Add support for rotation sensor Francesco Lavra
2026-03-21 17:46 ` David Lechner [this message]
2026-03-21 18:51 ` 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=e1b3e1e5-6073-4ddc-a0f4-2834ce6c29f7@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=flavra@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nuno.sa@analog.com \
/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®