From: Jonathan Cameron <jic23@kernel.org>
To: Stepan Ionichev <sozdayvek@gmail.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
hcazarim@yahoo.com, linux-iio@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org
Subject: Re: [PATCH v3] iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind
Date: Sat, 4 Jul 2026 00:04:15 +0100 [thread overview]
Message-ID: <20260704000415.2446940f@jic23-huawei> (raw)
In-Reply-To: <20260529095649.2452-1-sozdayvek@gmail.com>
On Fri, 29 May 2026 14:56:48 +0500
Stepan Ionichev <sozdayvek@gmail.com> wrote:
> iadc_probe() calls enable_irq_wake() after a successful
> devm_request_irq(), but the driver has no remove callback or
> matching disable_irq_wake(), so the wake reference count on the
> IRQ is leaked on module unload or driver unbind.
>
> Check the IRQ request error first, then register a devm action
> that calls disable_irq_wake() so the wake reference is released
> in the same scope as the enable. While here, drop the inverted
> "if (!ret) ... else return ret" in favour of the standard
> "if (ret) return ret;" pattern.
>
> Fixes: ce0694841ea6 ("iio: iadc: Qualcomm SPMI PMIC current ADC driver")
> Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
+CC Bjorn and Konrad as we don't seem to have a more specific
maintainer for this driver.
Seems low risk, but nice to run it past them.
Thanks,
Jonathan
> ---
> v3:
> - Add Fixes tag (Jonathan)
>
> v2: https://lore.kernel.org/all/20260523134613.4930-1-sozdayvek@gmail.com/
> v1: https://lore.kernel.org/all/20260520190924.12774-1-sozdayvek@gmail.com/
>
> drivers/iio/adc/qcom-spmi-iadc.c | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/adc/qcom-spmi-iadc.c b/drivers/iio/adc/qcom-spmi-iadc.c
> index b64a8a407168..88f6be2108e7 100644
> --- a/drivers/iio/adc/qcom-spmi-iadc.c
> +++ b/drivers/iio/adc/qcom-spmi-iadc.c
> @@ -481,6 +481,11 @@ static const struct iio_chan_spec iadc_channels[] = {
> },
> };
>
> +static void iadc_disable_irq_wake(void *data)
> +{
> + disable_irq_wake((long)data);
> +}
> +
> static int iadc_probe(struct platform_device *pdev)
> {
> struct device_node *node = pdev->dev.of_node;
> @@ -538,9 +543,16 @@ static int iadc_probe(struct platform_device *pdev)
> if (!iadc->poll_eoc) {
> ret = devm_request_irq(dev, irq_eoc, iadc_isr, 0,
> "spmi-iadc", iadc);
> - if (!ret)
> - enable_irq_wake(irq_eoc);
> - else
> + if (ret)
> + return ret;
> +
> + ret = enable_irq_wake(irq_eoc);
> + if (ret)
> + return ret;
> +
> + ret = devm_add_action_or_reset(dev, iadc_disable_irq_wake,
> + (void *)(long)irq_eoc);
> + if (ret)
> return ret;
> } else {
> ret = devm_device_init_wakeup(iadc->dev);
next prev parent reply other threads:[~2026-07-03 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 9:56 [PATCH v3] iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind Stepan Ionichev
2026-07-03 23:04 ` Jonathan Cameron [this message]
2026-07-06 11:25 ` Konrad Dybcio
2026-07-06 15:45 ` Jonathan Cameron
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=20260704000415.2446940f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andersson@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=hcazarim@yahoo.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.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