Re: [PATCH] iio: imu: inv_icm42600: update gyro start and stop delay

From: Jean-Baptiste Maneyrol

Date: Tue Oct 20 2026 - 08:43:43 EST


>________________________________________
>From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxx>
>Sent: Tuesday, October 20, 2026 10:53
>To: Jean-Baptiste Maneyrol
>Cc: Jonathan Cameron; David Lechner; Nuno Sá; Andy Shevchenko; linux-iio@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
>Subject: Re: [PATCH] iio: imu: inv_icm42600: update gyro start and stop delay
>
>On Tue, Oct 20, 2026 at 10: 42: 30AM +0200, Jean-Baptiste Maneyrol via B4 Relay wrote: > Following datasheet gyroscope specifications, the maximum start time What datasheet? What specifications? Please, be more precise to refer the Datasheet
>ZjQcmQRYFpfptBannerStart
>This Message Is From an External Sender
>This message came from outside your organization.
>
>ZjQcmQRYFpfptBannerEnd
>
>On Tue, Oct 20, 2026 at 10:42:30AM +0200, Jean-Baptiste Maneyrol via B4 Relay wrote:
>
>> Following datasheet gyroscope specifications, the maximum start time
>
>What datasheet? What specifications? Please, be more precise to refer the
>Datasheet name, version, chapter, section, et cetera.

Hello Andy,

I will add the reference.

>
>> for gyroscope is 45ms. Stop time is required for letting gyroscope
>> mechanical structure settle down before enabling it back. 50ms is a
>> sufficient value for that.
>>
>> Update values to these numbers.
>
>Do we need a Fixes tag?

I don't think so, since it is not a bug fix but an enhancement. It was
working correctly before, even if it was waiting too much for nothing.

>
>--
>With Best Regards,
>Andy Shevchenko
>

Thanks,
JB