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

On 08/02/2022 08:03, Zenghui Yu wrote:
> 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(-)
> 

Fix is correct but instead entire bindings should be converted to DT schema.


Best regards,
Krzysztof

On Tue, 08 Feb 2022 15:03:00 +0800, Zenghui Yu wrote:
> 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(-)
> 

Applied, thanks!