From: Bjorn Andersson <andersson@kernel.org>
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>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
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
Subject: Re: (subset) [PATCH v5 0/5] OPP: Add support to find OPP for a set of keys
Date: Mon, 27 Oct 2025 17:37:05 -0500 [thread overview]
Message-ID: <176160465218.73268.17091212801966002684.b4-ty@kernel.org> (raw)
In-Reply-To: <20251013-opp_pcie-v5-0-eb64db2b4bd3@oss.qualcomm.com>
On Mon, 13 Oct 2025 16:23:27 +0530, Krishna Chaitanya Chundru wrote:
> 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.
>
> [...]
Applied, thanks!
[1/5] arm64: dts: qcom: sm8450: Add opp-level to indicate PCIe data rates
commit: 367c2f473f5f5a84cdf633df96e0f9b4a16e443d
[2/5] arm64: dts: qcom: sm8550: Add opp-level to indicate PCIe data rates
commit: fc0ed54869be3a40c92879411b6db553d271de4d
[3/5] arm64: dts: qcom: sm8650: Add opp-level to indicate PCIe data rates
commit: 860d514f09f0ccecd233808b44918ac5b2c10627
[4/5] arm64: dts: qcom: x1e80100: Add opp-level to indicate PCIe data rates
commit: cfd8f45ddf8944fa95ae3e8cb5159c62fef95e34
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-10-27 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:53 [PATCH v5 0/5] OPP: Add support to find OPP for a set of keys Krishna Chaitanya Chundru
2025-10-13 10:53 ` [PATCH v5 1/5] arm64: dts: qcom: sm8450: Add opp-level to indicate PCIe data rates Krishna Chaitanya Chundru
2025-10-13 10:53 ` [PATCH v5 2/5] arm64: dts: qcom: sm8550: " Krishna Chaitanya Chundru
2025-10-13 10:53 ` [PATCH v5 3/5] arm64: dts: qcom: sm8650: " Krishna Chaitanya Chundru
2025-10-13 10:53 ` [PATCH v5 4/5] arm64: dts: qcom: x1e80100: " Krishna Chaitanya Chundru
2025-10-13 10:53 ` [PATCH v5 5/5] PCI: qcom: Use frequency and level based OPP lookup Krishna Chaitanya Chundru
2025-10-22 16:37 ` Konrad Dybcio
2025-10-26 16:26 ` Manivannan Sadhasivam
2025-10-29 20:39 ` Bjorn Helgaas
2025-10-31 6:28 ` Manivannan Sadhasivam
2025-10-26 16:25 ` (subset) [PATCH v5 0/5] OPP: Add support to find OPP for a set of keys Manivannan Sadhasivam
2025-10-26 16:27 ` Manivannan Sadhasivam
2025-10-27 22:37 ` Bjorn Andersson [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=176160465218.73268.17091212801966002684.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--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