From: Udit Tiwari <quic_utiwari@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
<herbert@gondor.apana.org.au>, <thara.gopinath@gmail.com>,
<davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_neersoni@quicinc.com>
Subject: Re: [PATCH v5] crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Date: Tue, 6 Jan 2026 10:41:20 +0530 [thread overview]
Message-ID: <ec9e420a-932d-4265-8cac-dee003933898@quicinc.com> (raw)
In-Reply-To: <a2c6cbdb-a114-423f-a315-6e5e9ab84e5a@oss.qualcomm.com>
On 12/5/2025 4:59 PM, Konrad Dybcio wrote:
> On 11/20/25 7:24 AM, quic_utiwari@quicinc.com wrote:
>> From: Udit Tiwari <quic_utiwari@quicinc.com>
>>
>> The Qualcomm Crypto Engine (QCE) driver currently lacks support for
>> runtime power management (PM) and interconnect bandwidth control.
>> As a result, the hardware remains fully powered and clocks stay
>> enabled even when the device is idle. Additionally, static
>> interconnect bandwidth votes are held indefinitely, preventing the
>> system from reclaiming unused bandwidth.
>
> [...]
>
>> @@ -90,13 +93,17 @@ static int qce_handle_queue(struct qce_device *qce,
>> struct crypto_async_request *async_req, *backlog;
>> int ret = 0, err;
>>
>> + ret = pm_runtime_resume_and_get(qce->dev);
>> + if (ret < 0)
>> + return ret;
>> +
>
> This is quite new, but maybe we could use
>
> ACQUIRE(pm_runtime_active_try, pm)(qce->dev);
> ret = ACQUIRE_ERR(pm_runtime_active_auto_try, &pm)
> if (ret)
> return ret;
>
> and drop the goto-s
>
> Konrad
Thanks for the review and suggestion konrad.
The optimization you proposed is more of an incremental refinement
rather than a functional fix, and I’d prefer to keep this patch focused
so it’s easier to review and backport. Would it be acceptable to merge
this as-is and handle that optimization in a small follow-up patch?
If you consider it a hard requirement for this series, I can rework it,
but my preference is to land the functional PM support first and then
iterate.
Best regards,
Udit
next prev parent reply other threads:[~2026-01-06 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 6:24 quic_utiwari
2025-12-05 11:29 ` Konrad Dybcio
2026-01-06 5:11 ` Udit Tiwari [this message]
2026-01-27 4:27 ` Udit Tiwari
2026-02-02 12:25 ` Konrad Dybcio
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=ec9e420a-932d-4265-8cac-dee003933898@quicinc.com \
--to=quic_utiwari@quicinc.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_neersoni@quicinc.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®