From: Lars-Peter Clausen <lars@metafoo.de>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>,
Fawzi Khaber <Fawzi.Khaber@tdk.com>,
"jic23@kernel.org" <jic23@kernel.org>
Cc: linux-iio <linux-iio@vger.kernel.org>
Subject: Re: iio: imu new driver
Date: Fri, 15 Apr 2022 19:39:28 +0200 [thread overview]
Message-ID: <9dcc005b-20b4-6884-1096-6d81fedaddaf@metafoo.de> (raw)
In-Reply-To: <FR3P281MB175790BCD24EC802E3B22EC8CEEF9@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>
On 4/14/22 15:03, Jean-Baptiste Maneyrol wrote:
> Hello,
>
> accel and gyro are synchronized and are outputting data inside the same hardware FIFO, as inv_icm42600 is doing. The issue is that the sensors have different frequencies, using a header for signaling data availability, thus demultiplexing from userspace is not possible in a standard way.
>
> Solution found for inv_icm42600 was to use 2 devices with each one a buffer. FIFO is read, data demultiplexed, and sent in each device. Now that we can have 2 buffers for 1 device, is it simpler to use this solution rather than 2 devices?
>
> Thanks for your advice,
> JB
Hi,
So the data rates are synchronized, but different, i.e. integer ratios?
I think this might be a good use case to give the multi-buffer support a
bit of real world testing.
- Lars
>
>
> From: Lars-Peter Clausen <lars@metafoo.de>
> Sent: Thursday, April 14, 2022 13:19
> 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
>
> [CAUTION] This is EXTERNAL email. Do not click any links or open attachments unless you recognize the sender and know the content is safe.
>
> ======================================================================
> 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-15 17:39 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
2022-04-14 13:03 ` Jean-Baptiste Maneyrol
2022-04-15 17:39 ` Lars-Peter Clausen [this message]
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=9dcc005b-20b4-6884-1096-6d81fedaddaf@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