From: Andi Shyti <andi.shyti@kernel.org>
To: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
Cc: Frank.Li@kernel.org, viken.dadhaniya@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com, zhengxingda@iscas.ac.cn,
kees@kernel.org, quic_jseerapu@quicinc.com,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
bjorn.andersson@oss.qualcomm.com,
konrad.dybcio@oss.qualcomm.com,
Aniket Randive <aniketrandive@oss.qualcomm.com>
Subject: Re: [PATCH v7 2/2] dmaengine: qcom-gpi: Keep GPI interrupt active during system resume
Date: Wed, 29 Jul 2026 22:21:49 +0200 [thread overview]
Message-ID: <ampgw7SerP4d_hQ0@zenone.zhora.eu> (raw)
In-Reply-To: <20260709134623.1724212-3-mukesh.savaliya@oss.qualcomm.com>
Hi Mukesh,
On Thu, Jul 09, 2026 at 07:16:23PM +0530, Mukesh Kumar Savaliya wrote:
> GPI DMA clients may initiate transfers during the early stages of
> system resume before the normal IRQ resume phase has completed.
> However, the GPI interrupt is currently suspended during system
> sleep, preventing transfer completion notifications from being
> delivered until later in the resume sequence.
>
> Request the GPI interrupt with IRQF_NO_SUSPEND and IRQF_EARLY_RESUME
> to keep it available across suspend/resume transitions and allow
> interrupt handling to resume during the noirq phase.
>
> This ensures DMA completion events can be delivered to clients that
> become operational before the normal resume phase completes
>
> Signed-off-by: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
> Acked-by: Aniket Randive <aniketrandive@oss.qualcomm.com>
shouldn't this patch come before patch 1?
Andi
prev parent reply other threads:[~2026-07-29 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 13:46 [PATCH v7 0/2] i2c: i2c-qcom-geni: serve transfers during early resume Mukesh Kumar Savaliya
2026-07-09 13:46 ` [PATCH v7 1/2] i2c: qcom-geni: Handle runtime PM disabled state " Mukesh Kumar Savaliya
[not found] ` <9cf5b5ab-c418-4b0d-8b2f-b888a64db0f0@oss.qualcomm.com>
[not found] ` <933d864d-f0c2-4727-a01d-f564eb854d23@oss.qualcomm.com>
[not found] ` <4133bbcb-22e7-41e0-b9f4-affd63df0e38@oss.qualcomm.com>
[not found] ` <86828cb8-0e96-48ce-aff4-0f7e59438ad7@oss.qualcomm.com>
2026-07-24 4:42 ` Praveen Talari
2026-07-24 6:35 ` Mukesh Savaliya
2026-07-24 8:29 ` Praveen Talari
2026-07-29 20:20 ` Andi Shyti
2026-07-09 13:46 ` [PATCH v7 2/2] dmaengine: qcom-gpi: Keep GPI interrupt active during system resume Mukesh Kumar Savaliya
2026-07-29 20:21 ` Andi Shyti [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=ampgw7SerP4d_hQ0@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=aniketrandive@oss.qualcomm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=quic_jseerapu@quicinc.com \
--cc=viken.dadhaniya@oss.qualcomm.com \
--cc=zhengxingda@iscas.ac.cn \
/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