From: Zenghui Yu <yuzenghui@huawei.com>
To: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski@canonical.com>
Cc: <kernel.yuz@gmail.com>, <wanghaibin.wang@huawei.com>,
<wangjingyi11@huawei.com>, Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH] dt-bindings: arm: Trivial typo fixes in cpu-capacity.txt
Date: Tue, 8 Feb 2022 15:03:00 +0800 [thread overview]
Message-ID: <20220208070300.1610-1-yuzenghui@huawei.com> (raw)
Correct the spelling of 'cluster1@max-freq' and fix the wrong
capacity-dmips-mhz value 576 (which should be 578 instead).
Signed-off-by: Zenghui Yu <yuzenghui@huawei.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@max-freq=1100 and
-custer1@max-freq=850, final capacities are 1024 for cluster0 and
-446 for cluster1 (576*850/1100).
+cluster1@max-freq=850, final capacities are 1024 for cluster0 and
+446 for cluster1 (578*850/1100).
cpus {
#address-cells = <2>;
--
2.19.1
next reply other threads:[~2022-02-08 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 7:03 Zenghui Yu [this message]
2022-02-08 8:00 ` [PATCH] dt-bindings: arm: Trivial typo fixes in cpu-capacity.txt Krzysztof Kozlowski
2022-02-11 16:37 ` Rob Herring
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=20220208070300.1610-1-yuzenghui@huawei.com \
--to=yuzenghui@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel.yuz@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wanghaibin.wang@huawei.com \
--cc=wangjingyi11@huawei.com \
/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).