On 1/27/26 8:26 PM, Jagadeesh Kona wrote:
quoted hunk ↗ jump to hunk
Update the compatible for videocc and camcc nodes to match with their
respective purwa(X1P42100) specific drivers.
Signed-off-by: Jagadeesh Kona <redacted>
---
arch/arm64/boot/dts/qcom/purwa.dtsi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/purwa.dtsi b/arch/arm64/boot/dts/qcom/purwa.dtsi
index 2cecd2dd0de8c39f0702d6983bead2bc2adccf9b..63599ba0a4f488d8f40f3e4d849645a8fa9ebf59 100644
--- a/arch/arm64/boot/dts/qcom/purwa.dtsi
+++ b/arch/arm64/boot/dts/qcom/purwa.dtsi
@@ -6,6 +6,8 @@
/* X1P42100 is heavily based on hamoa, with some meaningful differences */
#include "hamoa.dtsi"
+#include <dt-bindings/clock/qcom,x1p42100-videocc.h>
+
/delete-node/ &bwmon_cluster0;
/delete-node/ &cluster_pd2;
/delete-node/ &cpu_map_cluster2;
@@ -22,10 +24,18 @@
/delete-node/ &pcie3_phy;
/delete-node/ &thermal_zones;
+&camcc {
+ compatible = "qcom,x1p42100-camcc";
+};
Squash with patch(n-1) please
+
&gcc {
compatible = "qcom,x1p42100-gcc", "qcom,x1e80100-gcc";
};
+&videocc {
+ compatible = "qcom,x1p42100-videocc";
+};
This should be a 'fixes' commit, as since Commit a8a5ea012471
("arm64: dts: qcom: x1e80100: Add videocc") Purwa has been ""happily""
running the wrong driver
Konrad