From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Priyansh Jain <priyansh.jain@oss.qualcomm.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] thermal: qcom: tsens: refine wake IRQ handling for suspend
Date: Tue, 2 Jun 2026 23:12:32 +0200 [thread overview]
Message-ID: <993ef9ed-65d8-4bcd-b0f9-fa6f167395d2@oss.qualcomm.com> (raw)
In-Reply-To: <20260601-tsens_interrupt_wake_control-v2-0-ce9570946abd@oss.qualcomm.com>
On 6/1/26 08:37, Priyansh Jain wrote:
> This series refines how TSENS threshold IRQs are used as wake sources
> across suspend/resume.
>
> Patch 1 moves IRQ wake control from registration time into PM callbacks,
> so wakeup configuration follows the actual suspend state instead of being
> left enabled during normal runtime.
>
> Patch 2 adds a platform-data opt-out for wake IRQ setup and uses it for
> automotive TSENS compatibles (SA8775P/SA8255P), where parking suspend
> should not be exited repeatedly due to TSENS threshold wake events.
>
> Series highlights:
> - store and manage TSENS IRQ wake state in suspend/resume paths
> - keep existing runtime monitoring behavior unchanged
> - disable TSENS wake IRQ setup for selected automotive targets
>
> Signed-off-by: Priyansh Jain <priyansh.jain@oss.qualcomm.com>
> ---
Applied, thanks
prev parent reply other threads:[~2026-06-02 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:37 Priyansh Jain
2026-06-01 6:37 ` [PATCH v2 1/2] thermal: qcom: tsens: switch wake IRQ handling to PM callbacks Priyansh Jain
2026-06-01 6:37 ` [PATCH v2 2/2] thermal: qcom: tsens: Disable wakeup interrupt setup on automotive targets Priyansh Jain
2026-06-03 12:25 ` Konrad Dybcio
2026-06-03 12:27 ` Daniel Lezcano
2026-06-16 11:46 ` Konrad Dybcio
2026-06-02 21:12 ` Daniel Lezcano [this message]
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=993ef9ed-65d8-4bcd-b0f9-fa6f167395d2@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=priyansh.jain@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--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
all inboxes | Powered by JetHome®