From: Lars-Peter Clausen <lars@metafoo.de>
To: Fawzi Khaber <Fawzi.Khaber@tdk.com>,
"jic23@kernel.org" <jic23@kernel.org>
Cc: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: iio: imu new driver
Date: Thu, 14 Apr 2022 13:19:34 +0200 [thread overview]
Message-ID: <89c89115-334b-27ae-413c-73b3006d3ffa@metafoo.de> (raw)
In-Reply-To: <FRYP281MB020540A2361C4DCDB9F315A694EF9@FRYP281MB0205.DEUP281.PROD.OUTLOOK.COM>
On 4/14/22 12:35, Fawzi Khaber wrote:
> Hello Jonathan,
> We are currently implementing a new driver for an invensense chip similar to
> iio/imu/inv_icm42600. The chip has 2 sensors a gyroscope and an
> accelerometer, and we are wandering if it was better the have two
> IIO devices, one for each sensor, or just one IIO device with two buffers.
Are these two completely independent sensors that only sit in the same
package or do they share a common clock and the data acquisition can be
synchronized?
If it is the latter the best might be to have a single device with a
single buffer.
Typical algorithms that process IMU data, like odometry, want to process
the accelerator and gyroscope data jointly. If the data gets
artificially separated into two buffers it first has to be re-aligned,
which might be tricky to do.
- Lars
next prev parent reply other threads:[~2022-04-14 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 10:35 iio: imu new driver Fawzi Khaber
2022-04-14 11:19 ` Lars-Peter Clausen [this message]
2022-04-14 13:03 ` Jean-Baptiste Maneyrol
2022-04-15 17:39 ` Lars-Peter Clausen
2022-04-15 18:01 ` 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=89c89115-334b-27ae-413c-73b3006d3ffa@metafoo.de \
--to=lars@metafoo.de \
--cc=Fawzi.Khaber@tdk.com \
--cc=Jean-Baptiste.Maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.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