From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <~postmarketos/upstreaming@lists.sr.ht>,
<phone-devel@vger.kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC
Date: Mon, 17 Mar 2025 13:12:33 +0100 [thread overview]
Message-ID: <D8IJ5TEHREW1.2FK88ACT1JPYQ@fairphone.com> (raw)
In-Reply-To: <cddcd851-5e8c-4202-baad-e56a09d5775a@oss.qualcomm.com>
Hi Konrad,
On Fri Mar 14, 2025 at 11:08 PM CET, Konrad Dybcio wrote:
> On 3/14/25 10:17 AM, Luca Weiss wrote:
>> UFS host controller, when scaling gears, should choose appropriate
>> performance state of RPMh power domain controller along with clock
>> frequency. So let's add the OPP table support to specify both clock
>> frequency and RPMh performance states replacing the old "freq-table-hz"
>> property.
>>
>> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>> ---
>
> [...]
>
>> +
>> + ufs_opp_table: opp-table {
>> + compatible = "operating-points-v2";
>> +
>> + opp-50000000 {
>> + opp-hz = /bits/ 64 <50000000>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <0>,
>> + /bits/ 64 <37500000>,
>
> This rate on this clk requires opp_svs (not low_svs)
Not sure where you're seeing this?
This is from my msm-4.19 tree:
gcc_ufs_phy_axi_clk_src:
.rate_max = (unsigned long[VDD_NUM]) { [VDD_LOWER] = 50000000,
gcc_ufs_phy_unipro_core_clk_src:
.rate_max = (unsigned long[VDD_NUM]) { [VDD_LOWER] = 37500000,
gcc_ufs_phy_ice_core_clk_src:
.rate_max = (unsigned long[VDD_NUM]) { [VDD_LOWER] = 75000000,
[VDD_LOWER] = RPMH_REGULATOR_LEVEL_LOW_SVS,
My intepretation for this is we need low_svs?
Regards
Luca
>
> with that:
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Konrad
next prev parent reply other threads:[~2025-03-17 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 9:17 [PATCH 0/3] Fixes/improvements for SM6350 UFS Luca Weiss
2025-03-14 9:17 ` [PATCH 1/3] arm64: dts: qcom: sm6350: Fix wrong order of freq-table-hz for UFS Luca Weiss
2025-03-14 22:03 ` Konrad Dybcio
2025-09-16 10:10 ` Dmitry Baryshkov
2025-03-14 9:17 ` [PATCH 2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC Luca Weiss
2025-03-14 22:08 ` Konrad Dybcio
2025-03-17 12:12 ` Luca Weiss [this message]
2025-03-18 10:24 ` Konrad Dybcio
2025-09-16 10:10 ` Dmitry Baryshkov
2025-03-14 9:17 ` [PATCH 3/3] arm64: dts: qcom: sm6350: Add interconnect support to UFS Luca Weiss
2025-03-14 22:08 ` Konrad Dybcio
2025-09-16 10:11 ` Dmitry Baryshkov
2025-07-16 7:15 ` [PATCH 0/3] Fixes/improvements for SM6350 UFS Luca Weiss
2025-09-16 9:07 ` Luca Weiss
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=D8IJ5TEHREW1.2FK88ACT1JPYQ@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®