clk: zynqmp: enable COMMON_CLK_ZYNQMP for ARCH_ZYNQMP automatically
Subsystems (2)
PATCH 1/1 clk: zynqmp: enable COMMON_CLK_ZYNQMP for ARCH_ZYNQMP automatically
From: Quanyang Wang <[email protected]>
The Zynqmp Ultrascale clock controller generates clocks for peripherals, so we need to enable it when ARCH_ZYNQMP is selected.
--- drivers/clk/zynqmp/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/clk/zynqmp/Kconfig +1 -0
@@ -4,6 +4,7 @@ config COMMON_CLK_ZYNQMP bool "Support for Xilinx ZynqMP Ultrascale+ clock controllers" depends on ARCH_ZYNQMP || COMPILE_TEST depends on ZYNQMP_FIRMWARE + default ARCH_ZYNQMP help Support for the Zynqmp Ultrascale clock controller. It has a dependency on the PMU firmware.
Signature · 1 line
2.25.1
Hi,
Quoted 15 lines · On 08. 12. 20 13:35, [email protected] wrote:
From: Quanyang Wang <[email protected]>
The Zynqmp Ultrascale clock controller generates clocks for peripherals, so we need to enable it when
ARCH_ZYNQMPis selected.Signed-off-by Quanyang Wang <[email protected]>--- drivers/clk/zynqmp/Kconfig | 1 + 1 file changed, 1 insertion(+)drivers/clk/zynqmp/Kconfig +0
-0
drivers/clk/zynqmp/Kconfig config COMMON_CLK_ZYNQMP · line 7
Quoted 4 lines
drivers/clk/zynqmp/Kconfig +1
-0@@ -4,6 +4,7 @@ config COMMON_CLK_ZYNQMP bool "Support for Xilinx ZynqMP Ultrascale+ clock controllers" depends on ARCH_ZYNQMP || COMPILE_TEST depends on ZYNQMP_FIRMWARE + default ARCH_ZYNQMP
This is not right. If you look 2 lines above.
drivers/clk/zynqmp/Kconfig config COMMON_CLK_ZYNQMP · line 10
Quoted 4 lines
drivers/clk/zynqmp/Kconfig +0
-0help Support for the Zynqmp Ultrascale clock controller. It has a dependency on the PMU firmware.
And we were talking about enabling this driver in defconfig. Not via Kconfig. This fragment was designed in a way that this clock controller doesn't need to be used. It is our default but if you want to use for example fixed clock you also can.
This enables space for being able to use for example different firmware.
Thanks,
Michal
Hi Michal,
Quoted 28 lines · Michal Simek
Hi,
Quoted 15 lines · On 08. 12. 20 13:35, [email protected] wrote:
From: Quanyang Wang <[email protected]>
The Zynqmp Ultrascale clock controller generates clocks for peripherals, so we need to enable it when
ARCH_ZYNQMPis selected.Signed-off-by Quanyang Wang <[email protected]>--- drivers/clk/zynqmp/Kconfig | 1 + 1 file changed, 1 insertion(+)drivers/clk/zynqmp/Kconfig +0
-0drivers/clk/zynqmp/Kconfig config COMMON_CLK_ZYNQMP · line 7
Quoted 4 lines
drivers/clk/zynqmp/Kconfig +1
-0@@ -4,6 +4,7 @@ config COMMON_CLK_ZYNQMP bool "Support for Xilinx ZynqMP Ultrascale+ clock controllers" depends on ARCH_ZYNQMP || COMPILE_TEST depends on ZYNQMP_FIRMWARE + default ARCH_ZYNQMPThis is not right. If you look 2 lines above.
drivers/clk/zynqmp/Kconfig config COMMON_CLK_ZYNQMP · line 10
Quoted 4 lines
drivers/clk/zynqmp/Kconfig +0
-0help Support for the Zynqmp Ultrascale clock controller. It has a dependency on the PMU firmware.
Quoted 5 lines
And we were talking about enabling this driver in defconfig. Not via
Kconfig. This fragment was designed in a way that this clock controller doesn't need to be used. It is our default but if you want to use for example fixed clock you also can.
This enables space for being able to use for example different firmware.
Thanks for your reply. I will enable this driver in defconfig.
Best Regards
Quanyang
Quoted 3 lines
Thanks,
Michal