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 0/3] opp: Add bw_factor support to adjust bandwidth dynamically
Date: Fri, 1 Aug 2025 15:05:31 +0530 [thread overview]
Message-ID: <7f1393ab-5ae2-428a-92f8-3c8a5df02058@oss.qualcomm.com> (raw)
In-Reply-To: <20250801085628.7gdqycsggnqxdr67@vireshk-i7>
On 8/1/2025 2:26 PM, Viresh Kumar wrote:
> On 01-08-25, 13:58, Krishna Chaitanya Chundru wrote:
>> When ever PCIe link speed/width changes we need to update the OPP votes,
>> If we use named properties approach we might not be able to change it
>> dynamically without removing the OPP table first. For that reason only
>> we haven't used that approach.
>
> I am not sure I understand it fully. I thought this was a one time configuration
> you were required to do at boot time based on platform's configuration.
>
I am not fully familiar with OPP here.
> If you need to change the performance at runtime, won't you switch to a
> different OPP ?
>
yes we do set different OPP when we change it.
Currently we are fetching the OPP based on the frequency and setting
that OPP using dev_pm_opp_set_opp().
As you are suggesting to use dev_pm_opp_set_prop_name() here.
This what I understood
First set prop name using dev_pm_opp_set_prop_name then
set opp dev_pm_opp_set_opp()
if you want to change above one we need to first clear using
dev_pm_opp_put_prop_name() then again call dev_pm_opp_set_prop_name
& dev_pm_opp_set_opp()
I was in a impression that once you call dev_pm_opp_put_prop_name()
the previous votes will be removed. we don't want that to happen.
if this is not correct we can use this approach.
If this is not correct assumption can you point me any reference to this
I was not able to find any reference on this.
- Krishna Chaitanya.
> I don't have much knowledge of how PCIe works, maybe that's why the confusion.
>
next prev parent reply other threads:[~2025-08-01 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 14:01 Krishna Chaitanya Chundru
2025-07-17 14:01 ` [PATCH 1/3] " Krishna Chaitanya Chundru
2025-07-17 14:01 ` [PATCH 2/3] PCI: qcom: Use bw_factor to adjust bandwidth based on link width Krishna Chaitanya Chundru
2025-07-17 14:01 ` [PATCH 3/3] arm64: dts: qcom: sm8450: Keep only x1 lane PCIe OPP entries Krishna Chaitanya Chundru
2025-08-01 6:35 ` [PATCH 0/3] opp: Add bw_factor support to adjust bandwidth dynamically Krishna Chaitanya Chundru
2025-08-01 7:28 ` Viresh Kumar
2025-08-01 8:28 ` Krishna Chaitanya Chundru
2025-08-01 8:56 ` Viresh Kumar
2025-08-01 9:35 ` Krishna Chaitanya Chundru [this message]
2025-08-04 11:13 ` Viresh Kumar
2025-08-06 5:05 ` Krishna Chaitanya Chundru
2025-08-11 8:44 ` Viresh Kumar
2025-08-11 10:05 ` Krishna Chaitanya Chundru
2025-08-11 10:17 ` Viresh Kumar
2025-08-11 10:24 ` 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=7f1393ab-5ae2-428a-92f8-3c8a5df02058@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®