From: Jonathan Cameron <jic23@kernel.org>
To: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Amit Kucheria" <amitk@kernel.org>,
"Thara Gopinath" <thara.gopinath@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Lukasz Luba" <lukasz.luba@arm.com>,
linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
"Kamal Wadhwa" <kamal.wadhwa@oss.qualcomm.com>,
"David Collins" <david.collins@oss.qualcomm.com>,
"Anjelique Melendez" <anjelique.melendez@oss.qualcomm.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Stephan Gerhold" <stephan.gerhold@linaro.org>
Subject: Re: [PATCH v2 1/2] iio: adc: qcom-spmi-adc5-gen3: Share SDAM0 IRQ with ADC_TM auxiliary driver
Date: Wed, 27 May 2026 12:29:45 +0100 [thread overview]
Message-ID: <20260527122945.2bd99d3d@jic23-huawei> (raw)
In-Reply-To: <20260526-gen3_adc_tm-v2-1-702fbac919ac@oss.qualcomm.com>
On Tue, 26 May 2026 16:26:09 +0530
Jishnu Prakash <jishnu.prakash@oss.qualcomm.com> wrote:
> The SDAM0 IRQ can be triggered for both EOC (end of conversion) events for
> immediate ADC reads done in this driver and for threshold violation events,
> based on ADC_TM thresholds configured from the auxiliary ADC_TM driver on
> TM channels on the first SDAM.
>
> At present, this interrupt is handled only in the ISR in the main ADC driver.
> When the ISR is triggered for an ADC_TM event, this driver notifies the ADC_TM
> driver by calling a notifier callback exposed from it for this purpose.
>
> To simplify the interrupt handling in both drivers, share the interrupt between
> the drivers. With this, ADC_TM interrupts on SDAM0 will be handled directly in
> the ADC_TM driver, so remove the notifier callback and all TM interrupt
> handling in the main ADC ISR.
>
> Signed-off-by: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
One trivial thing inline if you are respinning. Not worth the bother
for just this.
Reviewed-by: Jonathan Cameron <jic23@kernel.org>
> static int adc5_gen3_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -817,10 +781,18 @@ static int adc5_gen3_probe(struct platform_device *pdev)
> return -ENOMEM;
> }
>
> - ret = devm_request_irq(dev, adc->dev_data.base[ADC5_GEN3_VADC_SDAM].irq,
> - adc5_gen3_isr, 0,
> - adc->dev_data.base[ADC5_GEN3_VADC_SDAM].irq_name,
> - adc);
> + /*
> + * This interrupt is shared with the ADC_TM auxiliary driver, which
> + * is threaded and uses IRQF_ONESHOT. Since shared interrupts need
> + * to agree on IRQF_ONESHOT configuration and there is a kernel
> + * warning for using IRQF_ONESHOT with non-threaded interrupts,
> + * make this also a threaded IRQ.
> + */
> +
If spinning again, drop this blank line. That will make it even more obvious
the comment is talking about the line that immediately follows.
> + ret = devm_request_threaded_irq(dev, adc->dev_data.base[ADC5_GEN3_VADC_SDAM].irq,
> + NULL, adc5_gen3_isr, IRQF_ONESHOT | IRQF_SHARED,
> + adc->dev_data.base[ADC5_GEN3_VADC_SDAM].irq_name,
> + adc);
> if (ret)
> return dev_err_probe(dev, ret,
> "Failed to request SDAM%d irq\n",
next prev parent reply other threads:[~2026-05-27 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 10:56 [PATCH v2 0/2] thermal: qcom: add support for PMIC5 Gen3 ADC thermal monitoring Jishnu Prakash
2026-05-26 10:56 ` [PATCH v2 1/2] iio: adc: qcom-spmi-adc5-gen3: Share SDAM0 IRQ with ADC_TM auxiliary driver Jishnu Prakash
2026-05-26 13:12 ` Daniel Lezcano
2026-05-27 11:26 ` Jonathan Cameron
2026-05-27 11:29 ` Jonathan Cameron [this message]
2026-06-02 23:35 ` Andy Shevchenko
2026-06-04 10:46 ` Jonathan Cameron
2026-06-04 14:44 ` Andy Shevchenko
2026-06-11 10:43 ` Jishnu Prakash
2026-06-11 18:53 ` Andy Shevchenko
2026-06-14 19:02 ` Jonathan Cameron
2026-05-26 10:56 ` [PATCH v2 2/2] thermal: qcom: add support for PMIC5 Gen3 ADC thermal monitoring Jishnu Prakash
2026-05-27 11:42 ` Jonathan Cameron
2026-06-11 10:42 ` Jishnu Prakash
2026-06-14 19:06 ` Jonathan Cameron
2026-06-02 23:44 ` Andy Shevchenko
2026-06-11 10:42 ` Jishnu Prakash
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=20260527122945.2bd99d3d@jic23-huawei \
--to=jic23@kernel.org \
--cc=amitk@kernel.org \
--cc=andy@kernel.org \
--cc=anjelique.melendez@oss.qualcomm.com \
--cc=daniel.lezcano@kernel.org \
--cc=david.collins@oss.qualcomm.com \
--cc=dlechner@baylibre.com \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=neil.armstrong@linaro.org \
--cc=nuno.sa@analog.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stephan.gerhold@linaro.org \
--cc=thara.gopinath@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