From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
Udit Tiwari <udit.tiwari@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 v8] crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Date: Wed, 29 Jul 2026 10:05:31 +0200 [thread overview]
Message-ID: <f19fa79b-82c6-4cb7-87fe-43c9b92907de@oss.qualcomm.com> (raw)
In-Reply-To: <d5de5a55-eb35-4ad5-8d53-12e188e156cb@oss.qualcomm.com>
On 7/28/26 8:11 AM, Kuldeep Singh wrote:
>> 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.
>>
>> Address this by enabling runtime PM and dynamic interconnect
>> bandwidth scaling to allow the system to suspend the device when idle
>> and scale interconnect usage based on actual demand. Improve overall
>> system efficiency by reducing power usage and optimizing interconnect
>> resource allocation.
>>
>> Signed-off-by: Udit Tiwari <udit.tiwari@oss.qualcomm.com>
>
> Herbert, can you please review and pick the patch if no further comments.
> This is required to fix interconnect votes summary for qce driver.
This needs to be rebased on linux-next/master
Konrad
next prev parent reply other threads:[~2026-07-29 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 10:52 [PATCH v8] crypto: qce - Add runtime PM and interconnect bandwidth scaling support Udit Tiwari
2026-07-21 11:26 ` Pankaj Patil
2026-07-28 6:11 ` Kuldeep Singh
2026-07-29 8:05 ` Konrad Dybcio [this message]
2026-07-29 8:56 ` Kuldeep Singh
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=f19fa79b-82c6-4cb7-87fe-43c9b92907de@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuldeep.singh@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 \
--cc=udit.tiwari@oss.qualcomm.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