On 12/11/23 23:05, Dario Binacchi wrote:
As described in [1], the "clocks" property contains "a phandle to the clock device node, an index selecting between gated clocks (0) and other clocks (1), and an index specifying the clock to use." The current version of the clock driver, unlike the kernel, is currently able to properly handle nodes with "clocks" properties with an index set to 0.
This patch is preparatory for future developments that require the use of the LTDC clock.
[1] Documentation/devicetree/bindings/clock/st,stm32-rcc.txt Signed-off-by: Dario Binacchi dario.binacchi@amarulasolutions.com Reviewed-by: Patrice Chotard patrice.chotard@foss.st.com
(no changes since v2)
Changes in v2:
- Add Patrice Chotard's Reviewed-by tag.
arch/arm/dts/stm32f469-disco-u-boot.dtsi | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/arch/arm/dts/stm32f469-disco-u-boot.dtsi b/arch/arm/dts/stm32f469-disco-u-boot.dtsi index c07e2022e4a8..dcc70369cd0d 100644 --- a/arch/arm/dts/stm32f469-disco-u-boot.dtsi +++ b/arch/arm/dts/stm32f469-disco-u-boot.dtsi @@ -134,6 +134,10 @@ bootph-all; };
+<dc {
- clocks = <&rcc 0 STM32F4_APB2_CLOCK(LTDC)>;
+};
&pinctrl { bootph-all;
Applied to u-boot-stm32/next
Thanks Patrice