arm64: zynqmp: Enable fclk nodes

CCF requires all PL IPs to have CCF compliant drivers and manage the clocks
they depend on. Currently not all PL IP drivers are CCF compliant and some
IPs may not have drivers. Since CCF accounts only for clock usage by CCF
compliant drivers, PL clocks may be gated and could cause malfunction of PL
IPs/Drivers that are not CCF compliant. So, keep all PL clocks always
enabled by enabling fclk nodes.
For cases which require active PL clock management, it should first be
ensured that all IPs have CCF compliant drivers and then fclk nodes can
be disabled.

Signed-off-by: Jyotheeswar Reddy Mutthareddyvari <jyotheeswar.reddy.mutthareddyvari@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>

diff --git a/arch/arm/dts/zynqmp-clk-ccf.dtsi b/arch/arm/dts/zynqmp-clk-ccf.dtsi
index 46d7f51fce207637f5ce3f5b5b04bd697fe0387f..91dfb560a680696c7279778d5989ba2f6130ad25 100644 (file)
--- a/arch/arm/dts/zynqmp-clk-ccf.dtsi
+++ b/arch/arm/dts/zynqmp-clk-ccf.dtsi
@@ -10,25 +10,25 @@
 #include <dt-bindings/clock/xlnx,zynqmp-clk.h>
 / {
        fclk0: fclk0 {
-               status = "disabled";
+               status = "okay";
                compatible = "xlnx,fclk";
                clocks = <&zynqmp_clk PL0_REF>;
        };
 
        fclk1: fclk1 {
-               status = "disabled";
+               status = "okay";
                compatible = "xlnx,fclk";
                clocks = <&zynqmp_clk PL1_REF>;
        };
 
        fclk2: fclk2 {
-               status = "disabled";
+               status = "okay";
                compatible = "xlnx,fclk";
                clocks = <&zynqmp_clk PL2_REF>;
        };
 
        fclk3: fclk3 {
-               status = "disabled";
+               status = "okay";
                compatible = "xlnx,fclk";
                clocks = <&zynqmp_clk PL3_REF>;
        };