From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: quic_utiwari@quicinc.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,
quic_kuldsing@quicinc.com
Subject: Re: [PATCH v6] crypto: qce - Add runtime PM and interconnect bandwidth scaling support
Date: Tue, 17 Feb 2026 11:42:22 +0100 [thread overview]
Message-ID: <e5fe09e4-758e-43ed-a134-55bcf3a198b7@oss.qualcomm.com> (raw)
In-Reply-To: <20260210061437.2293654-1-quic_utiwari@quicinc.com>
On 2/10/26 7:14 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.
>
> 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.
>
[...]
> + ret = pm_runtime_resume_and_get(dev);
> if (ret)
> return ret;
I expected this to use the new helper too, removing the need for gotos
altogether (unless this path needs some other handling which doesn't
immediately jump out to me)
[...]
> +static int __maybe_unused qce_runtime_resume(struct device *dev)
> +{
> + struct qce_device *qce = dev_get_drvdata(dev);
> + int ret = 0;
> +
> + ret = icc_enable(qce->mem_path);
> + if (ret)
> + return ret;
> +
> + ret = icc_set_bw(qce->mem_path, QCE_DEFAULT_MEM_BANDWIDTH, QCE_DEFAULT_MEM_BANDWIDTH);
> + if (ret)
> + goto err_icc;
Just one of these is good - icc_enable() simply calls icc_set_bw() with
the last known rate. Since we're not setting the rate any earlier,
just keeping the set_bw() alone seems like the way to go
Konrad
next prev parent reply other threads:[~2026-02-17 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 6:14 [PATCH v6] crypto: qce - Add runtime PM and interconnect bandwidth scaling support quic_utiwari
2026-02-17 10:42 ` Konrad Dybcio [this message]
2026-02-18 6:02 ` Udit Tiwari
2026-02-18 11:12 ` 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=e5fe09e4-758e-43ed-a134-55bcf3a198b7@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kuldsing@quicinc.com \
--cc=quic_neersoni@quicinc.com \
--cc=quic_utiwari@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