From: Demeter Barna via B4 Relay <devnull+me.fromdisposition.org@kernel.org>
To: 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: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Demeter Barna <me@fromdisposition.org>
Subject: [PATCH v2 1/2] arm64: dts: qcom: sm8350: Add CPU capacities
Date: Mon, 12 Oct 2026 03:56:04 +0000 [thread overview]
Message-ID: <20261012-sm8350-cpu-capacity-v2-1-67ce449becf0@fromdisposition.org> (raw)
In-Reply-To: <20261012-sm8350-cpu-capacity-v2-0-67ce449becf0@fromdisposition.org>
From: Demeter Barna <me@fromdisposition.org>
Without capacity-dmips-mhz every CPU reports a capacity of 1024, so the
scheduler treats the Cortex-A55, Cortex-A78 and Cortex-X1 cores as
equal and sets up no asymmetric CPU capacity.
Take the values from Qualcomm's downstream device tree for SM8350
(lahaina.dtsi in msm-5.4): 1024, 1946 and 2048, halved so that the X1 is
1024. Only their ratios matter, as the kernel normalizes them. The
downstream overlay for v2 silicon (lahaina-v2.dtsi) keeps them.
Assisted-by: LLM
Signed-off-by: Demeter Barna <me@fromdisposition.org>
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi b/arch/arm64/boot/dts/qcom/sm8350.dtsi
index 55b32050c..df6e9d1fa 100644
--- a/arch/arm64/boot/dts/qcom/sm8350.dtsi
+++ b/arch/arm64/boot/dts/qcom/sm8350.dtsi
@@ -60,6 +60,7 @@ cpu0: cpu@0 {
reg = <0x0 0x0>;
clocks = <&cpufreq_hw 0>;
enable-method = "psci";
+ capacity-dmips-mhz = <512>;
next-level-cache = <&l2_0>;
qcom,freq-domain = <&cpufreq_hw 0>;
power-domains = <&cpu_pd0>;
@@ -84,6 +85,7 @@ cpu1: cpu@100 {
reg = <0x0 0x100>;
clocks = <&cpufreq_hw 0>;
enable-method = "psci";
+ capacity-dmips-mhz = <512>;
next-level-cache = <&l2_100>;
qcom,freq-domain = <&cpufreq_hw 0>;
power-domains = <&cpu_pd1>;
@@ -103,6 +105,7 @@ cpu2: cpu@200 {
reg = <0x0 0x200>;
clocks = <&cpufreq_hw 0>;
enable-method = "psci";
+ capacity-dmips-mhz = <512>;
next-level-cache = <&l2_200>;
qcom,freq-domain = <&cpufreq_hw 0>;
power-domains = <&cpu_pd2>;
@@ -122,6 +125,7 @@ cpu3: cpu@300 {
reg = <0x0 0x300>;
clocks = <&cpufreq_hw 0>;
enable-method = "psci";
+ capacity-dmips-mhz = <512>;
next-level-cache = <&l2_300>;
qcom,freq-domain = <&cpufreq_hw 0>;
power-domains = <&cpu_pd3>;
@@ -141,6 +145,7 @@ cpu4: cpu@400 {
reg = <0x0 0x400>;
clocks = <&cpufreq_hw 1>;
enable-method = "psci";
+ capacity-dmips-mhz = <973>;
next-level-cache = <&l2_400>;
qcom,freq-domain = <&cpufreq_hw 1>;
power-domains = <&cpu_pd4>;
@@ -160,6 +165,7 @@ cpu5: cpu@500 {
reg = <0x0 0x500>;
clocks = <&cpufreq_hw 1>;
enable-method = "psci";
+ capacity-dmips-mhz = <973>;
next-level-cache = <&l2_500>;
qcom,freq-domain = <&cpufreq_hw 1>;
power-domains = <&cpu_pd5>;
@@ -179,6 +185,7 @@ cpu6: cpu@600 {
reg = <0x0 0x600>;
clocks = <&cpufreq_hw 1>;
enable-method = "psci";
+ capacity-dmips-mhz = <973>;
next-level-cache = <&l2_600>;
qcom,freq-domain = <&cpufreq_hw 1>;
power-domains = <&cpu_pd6>;
@@ -198,6 +205,7 @@ cpu7: cpu@700 {
reg = <0x0 0x700>;
clocks = <&cpufreq_hw 2>;
enable-method = "psci";
+ capacity-dmips-mhz = <1024>;
next-level-cache = <&l2_700>;
qcom,freq-domain = <&cpufreq_hw 2>;
power-domains = <&cpu_pd7>;
--
2.53.0
next prev parent reply other threads:[~2026-10-12 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 3:56 [PATCH v2 0/2] arm64: dts: qcom: sm8350: Add CPU capacities and power coefficients Demeter Barna via B4 Relay
2026-10-12 3:56 ` Demeter Barna via B4 Relay [this message]
2026-10-15 13:36 ` [PATCH v2 1/2] arm64: dts: qcom: sm8350: Add CPU capacities Konrad Dybcio
2026-10-12 3:56 ` [PATCH v2 2/2] arm64: dts: qcom: sm8350: Add CPU dynamic power coefficients Demeter Barna via B4 Relay
2026-10-15 13:37 ` Konrad Dybcio
2026-11-08 20:20 ` [PATCH v2 0/2] arm64: dts: qcom: sm8350: Add CPU capacities and " Bjorn Andersson
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=20261012-sm8350-cpu-capacity-v2-1-67ce449becf0@fromdisposition.org \
--to=devnull+me.fromdisposition.org@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@fromdisposition.org \
--cc=robh@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®