arm64: dts: exynosautov9: add specific compatibles to several blocks

ExynosAutov9 reuses several devices from older designs, thus historically
we kept the old (block's) compatible only.  This works fine and there is
no bug here, however guidelines expressed in
Documentation/devicetree/bindings/writing-bindings.rst state that:
1. Compatibles should be specific.
2. We should add new compatibles in case of bugs or features.

Add compatibles specific to ExynosAutov9 in front of all old-SoC-like
compatibles.  This will also help reviews of new code using existing
DTS as template.  No functional impact on Linux drivers behavior.

Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Link: https://lore.kernel.org/r/20231108104343.24192-18-krzysztof.kozlowski@linaro.org
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

diff --git a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
index b228cd7e351e9972e89f1915206b350d7b91eadf..417aa56a81f68253fcdf7437bf54465b3a2a6b12 100644 (file)
--- a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
+++ b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi
@@ -166,7 +166,8 @@
                ranges = <0x0 0x0 0x0 0x20000000>;
 
                chipid@10000000 {
-                       compatible = "samsung,exynos850-chipid";
+                       compatible = "samsung,exynosautov9-chipid",
+                                    "samsung,exynos850-chipid";
                        reg = <0x10000000 0x24>;
                };
 
@@ -349,7 +350,8 @@
                };
 
                pmu_system_controller: system-controller@10460000 {
-                       compatible = "samsung,exynos7-pmu", "syscon";
+                       compatible = "samsung,exynosautov9-pmu",
+                                    "samsung,exynos7-pmu", "syscon";
                        reg = <0x10460000 0x10000>;
 
                        reboot: syscon-reboot {