| Message ID | 20200915071221.72895-9-stephan@gerhold.net |
|---|---|
| State | New |
| Headers | show |
| Series | Cleanup & sort msm8916.dtsi, various minor fixes | expand |
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi b/arch/arm64/boot/dts/qcom/msm8916.dtsi index eca3cd94d3d5..b2669643a12d 100644 --- a/arch/arm64/boot/dts/qcom/msm8916.dtsi +++ b/arch/arm64/boot/dts/qcom/msm8916.dtsi @@ -392,7 +392,7 @@ smem { firmware { scm: scm { - compatible = "qcom,scm"; + compatible = "qcom,scm-msm8916", "qcom,scm"; clocks = <&gcc GCC_CRYPTO_CLK>, <&gcc GCC_CRYPTO_AXI_CLK>, <&gcc GCC_CRYPTO_AHB_CLK>; @@ -1162,7 +1162,7 @@ dsi_phy0: dsi-phy@1a98300 { }; mpss: hexagon@4080000 { - compatible = "qcom,q6v5-pil"; + compatible = "qcom,msm8916-mss-pil", "qcom,q6v5-pil"; reg = <0x04080000 0x100>, <0x04020000 0x040>;
Over the time, the SCM and MSS driver were refactored to use SoC-specific compatibles. While the generic compatibles still work correctly, add the MSM8916-specific compatibles so they are actually used somewhere. For SCM this will ensure that we actually manage to obtain all three of the specified clocks, since those are required on MSM8916. Signed-off-by: Stephan Gerhold <stephan@gerhold.net> --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)