From: "Rob Herring (Arm)" <robh@kernel.org>
To: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-scsi@vger.kernel.org,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>,
"David S. Miller" <davem@davemloft.net>,
Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v5 1/4] dt-bindings: crypto: ice: add operating-points-v2 property for QCOM ICE
Date: Wed, 11 Feb 2026 16:08:51 -0600 [thread overview]
Message-ID: <177084773073.3975957.7006950267237342921.robh@kernel.org> (raw)
In-Reply-To: <20260211-enable-ufs-ice-clock-scaling-v5-1-221c520a1f2e@oss.qualcomm.com>
On Wed, 11 Feb 2026 15:17:44 +0530, Abhinaba Rakshit wrote:
> Add support for specifying OPPs for the Qualcomm Inline Crypto Engine
> by allowing the use of the standard "operating-points-v2" property in
> the ICE device node.
>
> ICE clock management was handled by the storage drivers in legacy
> bindings, so the ICE driver itself had no mechanism for clock scaling.
> With the introduction of the new standalone ICE device node, clock
> control must now be performed directly by the ICE driver. Enabling
> operating-points-v2 allows the driver to describe and manage the
> frequency and voltage requirements for proper DVFS operation.
>
> Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com>
> ---
> .../bindings/crypto/qcom,inline-crypto-engine.yaml | 26 ++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-02-11 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 9:47 [PATCH v5 0/4] Enable ICE clock scaling Abhinaba Rakshit
2026-02-11 9:47 ` [PATCH v5 1/4] dt-bindings: crypto: ice: add operating-points-v2 property for QCOM ICE Abhinaba Rakshit
2026-02-11 22:08 ` Rob Herring (Arm) [this message]
2026-02-11 9:47 ` [PATCH v5 2/4] soc: qcom: ice: Add OPP-based clock scaling support for ICE Abhinaba Rakshit
2026-02-12 11:30 ` Konrad Dybcio
2026-02-13 7:02 ` Abhinaba Rakshit
2026-02-16 12:18 ` Konrad Dybcio
2026-02-18 19:02 ` Abhinaba Rakshit
2026-02-19 14:20 ` Konrad Dybcio
2026-02-20 7:33 ` Abhinaba Rakshit
2026-02-20 9:42 ` Konrad Dybcio
2026-02-20 11:15 ` Abhinaba Rakshit
2026-02-24 13:31 ` Konrad Dybcio
2026-02-13 7:32 ` Abhinaba Rakshit
2026-02-11 9:47 ` [PATCH v5 3/4] ufs: host: Add ICE clock scaling during UFS clock changes Abhinaba Rakshit
2026-02-11 9:47 ` [PATCH v5 4/4] soc: qcom: ice: Set ICE clk to TURBO on probe Abhinaba Rakshit
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=177084773073.3975957.7006950267237342921.robh@kernel.org \
--to=robh@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=abhinaba.rakshit@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neeraj.soni@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