On some of the Qualcomm platforms the Global Clock Controller doesn't
provide power domains to the platform. However the existing
qcom,gcc.yaml common schema requires the '#power-domain-cells' property.
This results either in a platforms having incorrect property or in DT
validation errors. Fix this by splitting the qcom,gcc-nopd.yaml schema,
which doesn't define the offensive property and use it for such
platforms.
Also, while we are at it, fix GCC node name for two platforms and
enforce node name in the DT schema.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
---
Dmitry Baryshkov (10):
dt-bindings: clock: qcom: split the non-PD schema for GCC
dt-bindings: clock: qcom,gcc-apq8064: use non-power-domain version of GCC schema
dt-bindings: clock: qcom,gcc-msm8660: use non-power-domain version of GCC schema
dt-bindings: clock: qcom,gcc-ipq6018: use non-power-domain version of GCC schema
dt-bindings: clock: qcom,gcc-nopd.yaml: force node name
ARM: dts: qcom: apq8064: drop #power-domain-cells property of GCC
ARM: dts: qcom: msm8660: drop #power-domain-cells property of GCC
ARM: dts: qcom: msm8960: drop #power-domain-cells property of GCC
arm64: dts: qcom: ipq6018: fix GCC node name
arm64: dts: qcom: ipq8074: fix GCC node name
.../bindings/clock/qcom,gcc-apq8064.yaml | 2 +-
.../bindings/clock/qcom,gcc-ipq6018.yaml | 2 +-
.../bindings/clock/qcom,gcc-msm8660.yaml | 2 +-
.../devicetree/bindings/clock/qcom,gcc-nopd.yaml | 43 ++++++++++++++++++++++
.../devicetree/bindings/clock/qcom,gcc.yaml | 19 ++--------
arch/arm/boot/dts/qcom/qcom-apq8064.dtsi | 1 -
arch/arm/boot/dts/qcom/qcom-msm8660.dtsi | 1 -
arch/arm/boot/dts/qcom/qcom-msm8960.dtsi | 1 -
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 2 +-
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 2 +-
10 files changed, 51 insertions(+), 24 deletions(-)
---
base-commit: ee3122766a21b81f4014bf7888dee5b9c5af15fa
change-id: 20240528-qcom-gdscs-b5e6cafdab9d
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
