From: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: lemans: Add OPP-table for ICE UFS device node
Date: Fri, 29 May 2026 11:32:19 +0530 [thread overview]
Message-ID: <ahkr613YCCWR+EdP@hu-arakshit-hyd.qualcomm.com> (raw)
In-Reply-To: <20260527101620.A83141F000E9@smtp.kernel.org>
On Wed, May 27, 2026 at 10:16:20AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] Mismatch between OPP node name `opp-75000000` and its `opp-hz` value, incorrectly specifying 750 MHz instead of 75 MHz.
> --
>
> commit 7df0ac8d5186b38efd03084ecec240e439760d84
> Author: Abhinaba Rakshit <abhinaba.rakshit@oss.qualcomm.com>
>
> arm64: dts: qcom: lemans: Add OPP-table for ICE UFS device node
>
> This commit adds an optional OPP-table for the Inline Crypto Engine (ICE) UFS
> device nodes on the Qualcomm LeMans platform. It defines the operating points
> by specifying required clock frequencies and their corresponding power domain
> performance states.
>
> > diff --git a/arch/arm64/boot/dts/qcom/lemans.dtsi b/arch/arm64/boot/dts/qcom/lemans.dtsi
> > --- a/arch/arm64/boot/dts/qcom/lemans.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/lemans.dtsi
>
> [ ... ]
>
> > @@ -3109,6 +3109,32 @@ ice: crypto@1d88000 {
> > clock-names = "core",
> > "iface";
> > power-domains = <&gcc UFS_PHY_GDSC>;
> > +
> > + operating-points-v2 = <&ice_opp_table>;
> > +
> > + ice_opp_table: opp-table {
> > + compatible = "operating-points-v2";
> > +
> > + opp-75000000 {
> > + opp-hz = /bits/ 64 <750000000>;
>
> [Severity: High]
> Does this opp-hz value have an extra zero?
>
> The node name is opp-75000000, but the frequency specified is 750000000
> (750 MHz) instead of 75 MHz. Requesting a 750 MHz clock frequency at the
> rpmhpd_opp_svs_l1 low power state could potentially cause clock scaling
> failures or hardware instability for the ICE block.
>
> > + required-opps = <&rpmhpd_opp_svs_l1>;
> > + };
Thanks for pointing this out.
Apologies, it's a miss on my side.
I will fix this in the next patch set.
Abhinaba Rakshit
prev parent reply other threads:[~2026-05-29 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 10:10 [PATCH] arm64: dts: qcom: lemans: Add OPP-table for ICE UFS device node Abhinaba Rakshit
2026-05-27 10:16 ` sashiko-bot
2026-05-29 6:02 ` Abhinaba Rakshit [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=ahkr613YCCWR+EdP@hu-arakshit-hyd.qualcomm.com \
--to=abhinaba.rakshit@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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