From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Amit Kumar Mahapatra" <amit.kumar-mahapatra@amd.com>,
"Michal Simek" <michal.simek@amd.com>,
"Sai Krishna Potthuri" <sai.krishna.potthuri@amd.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, amitrkcian2002@gmail.com
Subject: Re: [PATCH 3/6] iio: adc: versal-sysmon: disable interrupts on shutdown
Date: Sat, 7 Nov 2026 23:30:31 +0000 [thread overview]
Message-ID: <20261107233031.7ea9a718@jic23-hlaptop> (raw)
In-Reply-To: <aumzIdkwp_jVcTTs@ashevche-desk.local>
On Tue, 3 Nov 2026 12:10:41 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Mon, Nov 02, 2026 at 05:51:09PM +0530, Amit Kumar Mahapatra wrote:
> > Interrupt teardown is registered with devm_add_action_or_reset(), so
> > sysmon_disable_interrupts() runs when the driver is unbound but not when
> > the system shuts down: device_shutdown() invokes only the driver's
> > .shutdown callback, which this driver does not implement.
> >
> > The device is therefore left with its alarm interrupts enabled in
> > hardware once Linux has stopped servicing them.
> >
> > Add a .shutdown callback performing the same teardown, so the device is
> > quiesced before control is handed on. The helper lives in the core
> > module, so it is exported for the platform front-end. It skips a
> > device described without an interrupt, which never set up interrupt
> > handling.
> >
> > Disabling the interrupts at shutdown is safe to have and not a must have
> > requirement for shutdown.
>
> ...
>
> > + struct iio_dev *indio_dev = dev_get_drvdata(dev);
> > + struct sysmon *sysmon = iio_priv(indio_dev);
>
> Side Q to Jonathan: How do you see having a helper that unites these two?
> Something like void *iio_priv_from_drvdata(struct device *dev)
>
There is no strong reason to assume that dev_get_drvdata() returns
an iio_dev (even though that's a common choice) so a helper would
have to express that somehow in the naming.
next prev parent reply other threads:[~2026-11-07 23:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 12:21 [PATCH 0/6] iio: adc: versal-sysmon: Add OT alarm, shutdown and thermal zone support Amit Kumar Mahapatra
2026-11-02 12:21 ` [PATCH 1/6] iio: adc: versal-sysmon: fix race in interrupt teardown Amit Kumar Mahapatra
2026-11-03 7:05 ` Prasanna Kumar T S M
2026-11-07 23:27 ` Jonathan Cameron
2026-11-02 12:21 ` [PATCH 2/6] iio: adc: versal-sysmon: validate temperature hysteresis Amit Kumar Mahapatra
2026-11-03 10:08 ` Andy Shevchenko
2026-11-06 11:35 ` Mahapatra, Amit Kumar
2026-11-02 12:21 ` [PATCH 3/6] iio: adc: versal-sysmon: disable interrupts on shutdown Amit Kumar Mahapatra
2026-11-03 7:07 ` Prasanna Kumar T S M
2026-11-03 10:10 ` Andy Shevchenko
2026-11-07 23:30 ` Jonathan Cameron [this message]
2026-11-07 23:32 ` Jonathan Cameron
2026-11-02 12:21 ` [PATCH 4/6] iio: adc: versal-sysmon: add over-temperature alarm events Amit Kumar Mahapatra
2026-11-07 23:43 ` Jonathan Cameron
2026-11-02 12:21 ` [PATCH 5/6] arm64: versal-net: Add SysMon and thermal zone Amit Kumar Mahapatra
2026-11-02 14:53 ` Michal Simek
2026-11-06 11:46 ` Mahapatra, Amit Kumar
2026-11-02 12:21 ` [PATCH 6/6] MAINTAINERS: update Versal SysMon maintainers Amit Kumar Mahapatra
2026-11-02 12:53 ` Michal Simek
2026-11-06 11:46 ` Sai Krishna Potthuri
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=20261107233031.7ea9a718@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=amit.kumar-mahapatra@amd.com \
--cc=amitrkcian2002@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=sai.krishna.potthuri@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®