]> www.infradead.org Git - users/dwmw2/linux.git/commit
dt-bindings: clock: qcom,gcc: sort out power-domains support
authorDmitry Baryshkov <dmitry.baryshkov@linaro.org>
Wed, 29 May 2024 14:47:00 +0000 (17:47 +0300)
committerBjorn Andersson <andersson@kernel.org>
Fri, 31 May 2024 23:07:30 +0000 (18:07 -0500)
commitb0ef3434da07e7516a89a80206af53ea81954a80
tree87d38a1bf4d6c0cb8990fd58f3303b5c94b6394d
parentd99c899d2c42a37d331b8ac6f38c025884df15b2
dt-bindings: clock: qcom,gcc: sort out power-domains support

On some of Qualcomm platforms the Global Clock Controller (GCC) doesn't
provide power domains. Move requirement for the '#power-domain-cells'
out of the common qcom,gcc.yaml into individual schema files. For the
platforms that do not provide power-domains, explicitly forbid having
the '#power-domain-cells' property.

Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link: https://lore.kernel.org/r/20240529-qcom-gdscs-v2-2-69c63d0ae1e7@linaro.org
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
46 files changed:
Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-apq8084.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-ipq4019.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-ipq6018.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-ipq8064.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-ipq8074.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-mdm9607.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8660.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8909.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8916.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8953.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8974.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8976.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8994.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8996.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-msm8998.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-qcm2290.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-qcs404.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sc7180.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sc7280.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sc8180x.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sc8280xp.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sdm660.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sdm845.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sdx55.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sdx65.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm6115.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm6125.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm6350.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm8150.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm8250.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm8350.yaml
Documentation/devicetree/bindings/clock/qcom,gcc-sm8450.yaml
Documentation/devicetree/bindings/clock/qcom,gcc.yaml
Documentation/devicetree/bindings/clock/qcom,ipq5018-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,ipq5332-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,ipq9574-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sa8775p-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sdx75-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sm4450-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sm6375-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sm7150-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sm8550-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,sm8650-gcc.yaml
Documentation/devicetree/bindings/clock/qcom,x1e80100-gcc.yaml