From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Guntupalli, Manikanta" <manikanta.guntupalli@amd.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "git (AMD-Xilinx)" <git@amd.com>,
"Simek, Michal" <michal.simek@amd.com>,
"lorenzo@kernel.org" <lorenzo@kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"dlechner@baylibre.com" <dlechner@baylibre.com>,
"nuno.sa@analog.com" <nuno.sa@analog.com>,
"andy@kernel.org" <andy@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
"Goud, Srinivas" <srinivas.goud@amd.com>,
"manion05gk@gmail.com" <manion05gk@gmail.com>
Subject: Re: [PATCH] iio: imu: lsm6dsx: Add shutdown callback support for I3C interface
Date: Fri, 19 Sep 2025 12:10:08 +0100 [thread overview]
Message-ID: <9331e7064c6e6b4224e5ad50e1673e9c0c966ae0.camel@gmail.com> (raw)
In-Reply-To: <DM4PR12MB6109997B928B39D878B12FB68C5CA@DM4PR12MB6109.namprd12.prod.outlook.com>
On Tue, 2025-07-22 at 07:19 +0000, Guntupalli, Manikanta wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi @Andy Shevchenko,
>
> > -----Original Message-----
> > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > Sent: Monday, July 21, 2025 5:10 PM
> > To: Guntupalli, Manikanta <manikanta.guntupalli@amd.com>
> > Cc: git (AMD-Xilinx) <git@amd.com>; Simek, Michal <michal.simek@amd.com>;
> > lorenzo@kernel.org; jic23@kernel.org; dlechner@baylibre.com;
> > nuno.sa@analog.com; andy@kernel.org; linux-iio@vger.kernel.org; linux-
> > kernel@vger.kernel.org; Pandey, Radhey Shyam
> > <radhey.shyam.pandey@amd.com>; Goud, Srinivas <srinivas.goud@amd.com>;
> > manion05gk@gmail.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?
>
> There is no device enumeration process involved for I2C and SPI, so they are
> not impacted.
>
> However, for I3C, device enumeration does occur. During this process, the
> device PID and BCR/DCR values are compared against the entries defined in the
> driver:
>
> static const struct i3c_device_id st_lsm6dsx_i3c_ids[] = {
> I3C_DEVICE(0x0104, 0x006C, (void *)ST_LSM6DSO_ID),
> I3C_DEVICE(0x0104, 0x006B, (void *)ST_LSM6DSR_ID),
> { }
> };
>
> Only if there is a match, the probe function will be called.
>
> Additionally, the sensor reset logic is implemented inside the probe.
> Therefore, to ensure the sensor responds correctly during device enumeration
> after a reboot (such as after kexec), it is necessary to reset the sensor
> during the shutdown phase.
>
Hmm I see. I was going to ask why can't we just do this during probe().
- Nuno Sá
> Thanks,
> Manikanta.
next prev parent reply other threads:[~2025-09-19 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 11:07 Manikanta Guntupalli
2025-07-21 11:38 ` Andy Shevchenko
2025-07-21 11:39 ` Andy Shevchenko
2025-07-22 7:19 ` Guntupalli, Manikanta
2025-09-19 11:10 ` Nuno Sá [this message]
2025-07-21 21:01 ` David Lechner
2025-07-22 7:32 ` Guntupalli, Manikanta
2025-07-22 7:56 ` Jorge Marques
2025-07-29 12:02 ` Guntupalli, Manikanta
2025-07-29 12:49 ` Jorge Marques
2025-07-30 6:27 ` Guntupalli, Manikanta
2025-09-05 5:29 ` Guntupalli, Manikanta
2025-09-18 7:22 ` Mario TESI
2025-09-19 9:22 ` Guntupalli, Manikanta
2025-09-19 11:18 ` Nuno Sá
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=9331e7064c6e6b4224e5ad50e1673e9c0c966ae0.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=git@amd.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=manikanta.guntupalli@amd.com \
--cc=manion05gk@gmail.com \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=srinivas.goud@amd.com \
/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
all inboxes | Powered by JetHome®