From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: "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>
Cc: 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,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Subject: [PATCH 0/3] opp: Add bw_factor support to adjust bandwidth dynamically
Date: Thu, 17 Jul 2025 19:31:15 +0530 [thread overview]
Message-ID: <20250717-opp_pcie-v1-0-dde6f452571b@oss.qualcomm.com> (raw)
The existing OPP table in the device tree for PCIe is shared across
different link configurations such as data rates 8GT/s x2 and 16GT/s x1.
These configurations often operate at the same frequency, allowing them
to reuse the same OPP entries. However, 8GT/s and 16 GT/s may have
different characteristics beyond frequency—such as RPMh votes in QCOM
case, which cannot be represented accurately when sharing a single OPP.
To avoid conflicts and duplication in the device tree, we now define only
one set of OPP entries per table and introduce a new mechanism to adjust
bandwidth dynamically using a `bw_factor`.
The `bw_factor` is a multiplier applied to the average and peak bandwidth
values of an OPP entry. This allows PCIe drivers to modify the effective
bandwidth at runtime based on the actual link width without needing
separate OPP entries for each configuration.
Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
---
Krishna Chaitanya Chundru (3):
opp: Add bw_factor support to adjust bandwidth dynamically
PCI: qcom: Use bw_factor to adjust bandwidth based on link width
arm64: dts: qcom: sm8450: Keep only x1 lane PCIe OPP entries
arch/arm64/boot/dts/qcom/sm8450.dtsi | 17 ++--------------
drivers/opp/core.c | 37 ++++++++++++++++++++++++++++++++--
drivers/opp/opp.h | 2 ++
drivers/pci/controller/dwc/pcie-qcom.c | 8 ++++++--
include/linux/pm_opp.h | 7 +++++++
5 files changed, 52 insertions(+), 19 deletions(-)
---
base-commit: e2291551827fe5d2d3758c435c191d32b6d1350e
change-id: 20250717-opp_pcie-793160b2b113
Best regards,
--
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
next reply other threads:[~2025-07-17 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 14:01 Krishna Chaitanya Chundru [this message]
2025-07-17 14:01 ` [PATCH 1/3] opp: Add bw_factor support to adjust bandwidth dynamically 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
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=20250717-opp_pcie-v1-0-dde6f452571b@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=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;
as well as URLs for NNTP newsgroup(s).