[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aH4m84n5UbCsktCM@smile.fi.intel.com>
Date: Mon, 21 Jul 2025 14:39:31 +0300
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Manikanta Guntupalli <manikanta.guntupalli@....com>
Cc: git@....com, michal.simek@....com, lorenzo@...nel.org, jic23@...nel.org,
dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
radhey.shyam.pandey@....com, srinivas.goud@....com,
manion05gk@...il.com
Subject: Re: [PATCH] iio: imu: lsm6dsx: Add shutdown callback support for I3C
interface
On Mon, Jul 21, 2025 at 02:38:42PM +0300, Andy Shevchenko wrote:
> On Mon, Jul 21, 2025 at 04:37:41PM +0530, Manikanta Guntupalli wrote:
> > Add a shutdown handler for the ST LSM6DSx I3C driver to perform a hardware
> > reset during system shutdown. This ensures the sensor is placed in a
> > well-defined reset state, preventing issues during subsequent reboots,
> > such as kexec, where the device may fail to respond correctly during
> > enumeration.
>
> Do you imply that tons of device drivers missing this? I don't think we have
> even 5% of the drivers implementing the feature.
>
> > To support this, the previously static st_lsm6dsx_reset_device() function
> > is now exported via EXPORT_SYMBOL_NS() under the IIO_LSM6DSX namespace,
> > allowing it to be invoked from the I3C-specific driver.
>
> Why system suspend callback can't do this?
Ah, and why only I3C is important? Doesn't I2C or SPI also broken in this sense?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists