From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Viresh Kumar" <vireshk@kernel.org>, "Nishanth Menon" <nm@ti.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: sm8450: Add opp-level to indicate PCIe data rates
Date: Mon, 18 Aug 2025 14:37:03 +0530 [thread overview]
Message-ID: <5f3261c3-3e44-42a5-bac7-624ce4e7041f@oss.qualcomm.com> (raw)
In-Reply-To: <20250818090240.in7frzv4pudvnl6q@vireshk-i7>
On 8/18/2025 2:32 PM, Viresh Kumar wrote:
> On 18-08-25, 13:52, Krishna Chaitanya Chundru wrote:
>> @@ -2210,45 +2213,67 @@ pcie1_opp_table: opp-table {
>> compatible = "operating-points-v2";
>>
>> /* GEN 1 x1 */
>> - opp-2500000 {
>> + opp-2500000-1 {
>
> Why mention -1 here when there is only one entry with this freq value
> ?
>
>> opp-hz = /bits/ 64 <2500000>;
>> required-opps = <&rpmhpd_opp_low_svs>;
>> opp-peak-kBps = <250000 1>;
>> + opp-level = <1>;
>> };
>>
>> - /* GEN 1 x2 and GEN 2 x1 */
>> - opp-5000000 {
>> + /* GEN 1 x2 */
>> + opp-5000000-1 {
>> + opp-hz = /bits/ 64 <5000000>;
>> + required-opps = <&rpmhpd_opp_low_svs>;
>> + opp-peak-kBps = <500000 1>;
>> + opp-level = <1>;
>> + };
>> +
>> + /* GEN 2 x1 */
>> + opp-5000000-2 {
>> opp-hz = /bits/ 64 <5000000>;
>> required-opps = <&rpmhpd_opp_low_svs>;
>> opp-peak-kBps = <500000 1>;
>> + opp-level = <2>;
>> };
>
> This looks okay.
>
>>
>> /* GEN 2 x2 */
>> - opp-10000000 {
>> + opp-10000000-2 {
>
> Why -2 here ?
>
>> opp-hz = /bits/ 64 <10000000>;
>> required-opps = <&rpmhpd_opp_low_svs>;
>> opp-peak-kBps = <1000000 1>;
>> + opp-level = <2>;
>> };
>>
>> /* GEN 3 x1 */
>> - opp-8000000 {
>> + opp-8000000-3 {
>
> same.
>
>> opp-hz = /bits/ 64 <8000000>;
>> required-opps = <&rpmhpd_opp_nom>;
>> opp-peak-kBps = <984500 1>;
>> + opp-level = <3>;
>> + };
>> +
>> + /* GEN 3 x2 */
>> + opp-16000000-3 {
>
> Shouldn't this be opp-16000000-1 only ? This is the first occurrence
> 16000000.
>
>> + opp-hz = /bits/ 64 <16000000>;
>> + required-opps = <&rpmhpd_opp_nom>;
>> + opp-peak-kBps = <1969000 1>;
>> + opp-level = <3>;
>> };
>>
>> - /* GEN 3 x2 and GEN 4 x1 */
>> - opp-16000000 {
>> + /* GEN 4 x1 */
>> + opp-16000000-4 {
>
> opp-16000000-2 ?
I tried to add the level as prefix as that will indicate the PCIe date
rate also instead of 1, 2 to make more aligned with the PCIe
representations. I will update this in the commit text in my next
series.
- Krishna Chaitanya.
>
next prev parent reply other threads:[~2025-08-18 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 8:22 [PATCH v2 0/3] PM/OPP: Support to match OPP based on both frequency and level Krishna Chaitanya Chundru
2025-08-18 8:22 ` [PATCH v2 1/3] " Krishna Chaitanya Chundru
2025-08-18 8:55 ` Viresh Kumar
2025-08-18 8:57 ` Viresh Kumar
2025-08-18 9:04 ` Krishna Chaitanya Chundru
2025-08-18 23:46 ` kernel test robot
2025-08-18 23:46 ` kernel test robot
2025-08-18 8:22 ` [PATCH v2 2/3] arm64: dts: qcom: sm8450: Add opp-level to indicate PCIe data rates Krishna Chaitanya Chundru
2025-08-18 9:02 ` Viresh Kumar
2025-08-18 9:07 ` Krishna Chaitanya Chundru [this message]
2025-08-18 9:13 ` Viresh Kumar
2025-08-18 8:22 ` [PATCH v2 3/3] PCI: qcom: Use frequency and level based OPP lookup Krishna Chaitanya Chundru
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=5f3261c3-3e44-42a5-bac7-624ce4e7041f@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/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®