| Message ID | 20250318-fix-nexus-4-v2-0-bcedd1406790@oss.qualcomm.com |
|---|---|
| Headers | show |
| Series | ARM: qcom: fix APQ8064 schema warnings | expand |
On Tue, 18 Mar 2025 15:21:53 +0200, Dmitry Baryshkov wrote: > Rob's bot has reported [1] several warnings for Nexus 4 submisson, > however none of those warnings are specific to that device. Fix all > those warnings for all APQ8064 platforms by extending existing schemas, > adding missing schemas and making APQ8064 DT follow all the schema > files. > > [1]: https://lore.kernel.org/linux-arm-msm/174221818190.3957236.3364090534153729086.robh@kernel.org/ > > [...] Applied, thanks! [01/10] dt-bindings: soc: qcom,rpm: add missing clock-controller node commit: dc4ec780313c698dd75f685250f98f98e07f9f17 [02/10] dt-bindings: soc: qcom: qcom,rpm: add missing clock/-names properties commit: 3022ae40e92b1458901867a114472cff76dd3531 Best regards,
On Tue, 18 Mar 2025 15:21:53 +0200, Dmitry Baryshkov wrote: > Rob's bot has reported [1] several warnings for Nexus 4 submisson, > however none of those warnings are specific to that device. Fix all > those warnings for all APQ8064 platforms by extending existing schemas, > adding missing schemas and making APQ8064 DT follow all the schema > files. > > [1]: https://lore.kernel.org/linux-arm-msm/174221818190.3957236.3364090534153729086.robh@kernel.org/ > > [...] Applied, thanks! [06/10] ARM: dts: qcom: apq8064: add missing clocks to the timer node commit: 4b0eb149df58b6750cd8113e5ee5b3ac7cc51743 [07/10] ARM: dts: qcom: apq8064 merge hw splinlock into corresponding syscon device commit: 325c6a441ae1f8fcb1db9bb945b8bdbd3142141e [08/10] ARM: dts: qcom: apq8064: use new compatible for SFPB device commit: 2a1282861b73a4b8e45904e079ed3279c3f1c93f [09/10] ARM: dts: qcom: apq8064: use new compatible for SPS SIC device commit: 92c377bcafcddd43d4dca1aa60c865cdd2d1dbbb [10/10] ARM: dts: qcom: apq8064: move replicator out of soc node commit: f2420037d90a8354594b3da541e19dcbb60c75e1 Best regards,
Rob's bot has reported [1] several warnings for Nexus 4 submisson, however none of those warnings are specific to that device. Fix all those warnings for all APQ8064 platforms by extending existing schemas, adding missing schemas and making APQ8064 DT follow all the schema files. [1]: https://lore.kernel.org/linux-arm-msm/174221818190.3957236.3364090534153729086.robh@kernel.org/ Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> --- Changes in v2: - Corrected Fixes tag for the clock-controller patch to point to the commit which introduced qcom,rpmcc schema for APQ8064 (Krzysztof) - Switched to syscon.yaml (Krzysztof) - Reordered ports in the static replicator node (Konrad) - Fixed hwmutex node address (Konrad) - Fixed clocks in arm,coresight-static-replicator.yaml (Rob) - Documented clocks /clock-names in qcom,rpm node (Rob) - Link to v1: https://lore.kernel.org/r/20250317-fix-nexus-4-v1-0-655c52e2ad97@oss.qualcomm.com --- Dmitry Baryshkov (10): dt-bindings: soc: qcom,rpm: add missing clock-controller node dt-bindings: soc: qcom: qcom,rpm: add missing clock/-names properties dt-bindings: arm: arm,coresight-static-replicator: add optional clocks dt-bindings: mfd: syscon: add qcom,apq8064-sps-sic dt-bindings: mfd: syscon: add qcom,apq8064-mmss-sfpb ARM: dts: qcom: apq8064: add missing clocks to the timer node ARM: dts: qcom: apq8064 merge hw splinlock into corresponding syscon device ARM: dts: qcom: apq8064: use new compatible for SFPB device ARM: dts: qcom: apq8064: use new compatible for SPS SIC device ARM: dts: qcom: apq8064: move replicator out of soc node .../arm/arm,coresight-static-replicator.yaml | 13 ++++ Documentation/devicetree/bindings/mfd/syscon.yaml | 4 + .../devicetree/bindings/soc/qcom/qcom,rpm.yaml | 15 ++++ arch/arm/boot/dts/qcom/qcom-apq8064.dtsi | 88 +++++++++++----------- 4 files changed, 75 insertions(+), 45 deletions(-) --- base-commit: 9f789dc174dc1a40754507a962a4e9e7c593e2d8 change-id: 20250317-fix-nexus-4-dd0fe3bca987 Best regards,