| Message ID | 20200826131637.421327-2-tomi.valkeinen@ti.com |
|---|---|
| State | New |
| Headers | show |
| Series | None | expand |
diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts index 611e66207010..99b32038a453 100644 --- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts +++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts @@ -55,7 +55,7 @@ sw6 { }; }; - clk_ov5640_fixed: clock { + clk_ov5640_fixed: fixed-clock-ov5640 { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <24000000>;
The fixed clock for OV5640 is named 'clock' which is a very generic name and easily leads to conflicts. I encountered this with a similarly named fixed-clock node in k3-am654-evm-tc358876.dtso, which then overrode the OV5640 fixed clock, causing OV5640 not to work when tc358876 overlay had been loaded. Rename the node to 'fixed-clock-ov5640'. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> --- arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)