[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220208070300.1610-1-yuzenghui@huawei.com>
Date: Tue, 8 Feb 2022 15:03:00 +0800
From: Zenghui Yu <yuzenghui@...wei.com>
To: <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<robh+dt@...nel.org>, <krzysztof.kozlowski@...onical.com>
CC: <kernel.yuz@...il.com>, <wanghaibin.wang@...wei.com>,
<wangjingyi11@...wei.com>, Zenghui Yu <yuzenghui@...wei.com>
Subject: [PATCH] dt-bindings: arm: Trivial typo fixes in cpu-capacity.txt
Correct the spelling of 'cluster1@...-freq' and fix the wrong
capacity-dmips-mhz value 576 (which should be 578 instead).
Signed-off-by: Zenghui Yu <yuzenghui@...wei.com>
---
Documentation/devicetree/bindings/arm/cpu-capacity.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/cpu-capacity.txt b/Documentation/devicetree/bindings/arm/cpu-capacity.txt
index 380e21c5fc7e..cc5e190390b7 100644
--- a/Documentation/devicetree/bindings/arm/cpu-capacity.txt
+++ b/Documentation/devicetree/bindings/arm/cpu-capacity.txt
@@ -62,8 +62,8 @@ Example 1 (ARM 64-bit, 6-cpu system, two clusters):
The capacities-dmips-mhz or DMIPS/MHz values (scaled to 1024)
are 1024 and 578 for cluster0 and cluster1. Further normalization
is done by the operating system based on cluster0@...-freq=1100 and
-custer1@...-freq=850, final capacities are 1024 for cluster0 and
-446 for cluster1 (576*850/1100).
+cluster1@...-freq=850, final capacities are 1024 for cluster0 and
+446 for cluster1 (578*850/1100).
cpus {
#address-cells = <2>;
--
2.19.1
Powered by blists - more mailing lists