[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <vlpqd3jeszhgpcob7qyzp5vljdowwu26my7xuwuvfftf54zg35@czxhsjejgdkm>
Date: Tue, 15 Jul 2025 20:55:35 -0300
From: Gustavo Silva <gustavograzs@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: Alex Lanzano <lanzano.alex@...il.com>, 
	Jonathan Cameron <jic23@...nel.org>, David Lechner <dlechner@...libre.com>, 
	Nuno Sá <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>, linux-iio@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Lothar Rubusch <l.rubusch@...il.com>
Subject: Re: [PATCH v4 3/3] iio: imu: bmi270: add support for motion events
On Tue, Jul 15, 2025 at 10:49:25AM +0300, Andy Shevchenko wrote:
> On Tue, Jul 15, 2025 at 10:37:22AM +0300, Andy Shevchenko wrote:
> > On Fri, Jul 11, 2025 at 08:36:03PM -0300, Gustavo Silva wrote:
> 
> ...
> 
> > > +/* 9.81 * 1000000 m/s^2 */
> > > +#define BMI270_G_MEGA_M_S_2				9810000
> > 
> > I thought this is MICRO...
> 
> Btw, what if we use the device on poles and on equator (or even on orbital
> station)? I'm wondering if this constant should be defined in units.h or
> even in uAPI that user space may add a correction if needed.
> 
I certainly hadn't thought about these scenarios.
FWIW, the accelerometer scale values also assume g = 9.81 m/s^2.
For example, 0.000598 = 2 * 9.81 / 32768
> 
> -- 
> With Best Regards,
> Andy Shevchenko
> 
> 
Powered by blists - more mailing lists
 
