]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
dt-bindings: opp-v2: Fix example 3 CPU reg value
authorVivian Wang <wangruikang@iscas.ac.cn>
Fri, 3 Apr 2026 10:34:29 +0000 (18:34 +0800)
committerRob Herring (Arm) <robh@kernel.org>
Tue, 7 Apr 2026 11:44:43 +0000 (06:44 -0500)
commit1bf99c2a4b39307988a073bb29b126d1b832b415
treeeab0ba441c90ba9f39b9a170ef11448c9a1a5cca
parent7ed020d84a7b748f322f8e9d57ad7d60a5057130
dt-bindings: opp-v2: Fix example 3 CPU reg value

Example 3 is a dual-cluster example, meaning that the CPU nodes should
have reg values 0x0, 0x1, 0x100, 0x101. The example incorrectly uses
decimal 0, 1, 100, 101 instead, which seems unintended. Use the correct
hexadecimal values.

Even though the value doesn't change for the first two CPUs, 0 and 1 in
example 3 are changed to 0x0 and 0x1 respectively for consistency. Other
examples all have reg less than 10, so they have not been changed.

Signed-off-by: Vivian Wang <wangruikang@iscas.ac.cn>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260403-dt-bindings-opp-v2-hex-cpu-reg-v1-1-38a4968ab515@iscas.ac.cn
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Documentation/devicetree/bindings/opp/opp-v2.yaml