From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: Yannick Fertre <yannick.fertre@foss.st.com>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Christophe Roullier <christophe.roullier@foss.st.com>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 12/12] arm64: dts: st: add loopback clocks on LTDC node
Date: Fri, 25 Jul 2025 12:04:04 +0200 [thread overview]
Message-ID: <20250725-drm-misc-next-v1-12-a59848e62cf9@foss.st.com> (raw)
In-Reply-To: <20250725-drm-misc-next-v1-0-a59848e62cf9@foss.st.com>
ck_ker_ltdc has the CLK_SET_RATE_PARENT flag. While having this flag is
semantically correct, it for now leads to an improper setting of the
clock rate. The ck_ker_ltdc parent clock is the flexgen 27, which does
not support changing rates yet. To overcome this issue, a fixed clock
can be used for the kernel clock.
Add the clocks needed for the LTDC to work.
Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
---
arch/arm64/boot/dts/st/stm32mp251.dtsi | 6 ++++++
arch/arm64/boot/dts/st/stm32mp255.dtsi | 7 ++++++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
index c561df51a6001004e45fb53a56d5d42c310e6b61..54dd57e0a98eabbbcfe89459e6d63eb287f5ca04 100644
--- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
+++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
@@ -52,6 +52,12 @@ clk_rcbsec: clk-rcbsec {
compatible = "fixed-clock";
clock-frequency = <64000000>;
};
+
+ clk_flexgen_27_fixed: clk-54000000 {
+ #clock-cells = <0>;
+ compatible = "fixed-clock";
+ clock-frequency = <54000000>;
+ };
};
firmware {
diff --git a/arch/arm64/boot/dts/st/stm32mp255.dtsi b/arch/arm64/boot/dts/st/stm32mp255.dtsi
index a4d965f785fa42c4597494010855aec7e1b9fdd1..82c2fa67b6b91f67d51872ed098aea897fab0197 100644
--- a/arch/arm64/boot/dts/st/stm32mp255.dtsi
+++ b/arch/arm64/boot/dts/st/stm32mp255.dtsi
@@ -5,6 +5,11 @@
*/
#include "stm32mp253.dtsi"
+<dc {
+ clocks = <&rcc CK_BUS_LTDC>, <&clk_flexgen_27_fixed>, <&syscfg>, <&lvds>;
+ clock-names = "bus", "lcd", "ref", "lvds";
+};
+
&rifsc {
lvds: lvds@48060000 {
compatible = "st,stm32mp25-lvds";
@@ -34,4 +39,4 @@ venc: venc@480e0000 {
clocks = <&rcc CK_BUS_VENC>;
access-controllers = <&rifsc 90>;
};
-};
\ No newline at end of file
+};
--
2.25.1
prev parent reply other threads:[~2025-07-25 10:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 10:03 [PATCH 00/12] Enable display support for STM32MP25 Raphael Gallais-Pou
2025-07-25 10:03 ` [PATCH 01/12] dt-bindings: display: st: add new compatible to LTDC device Raphael Gallais-Pou
2025-07-25 12:12 ` Rob Herring (Arm)
2025-07-25 19:49 ` Rob Herring
2025-07-28 10:35 ` Raphael Gallais-Pou
2025-07-25 10:03 ` [PATCH 02/12] dt-bindings: display: st,stm32-ltdc: add access-controllers property Raphael Gallais-Pou
2025-07-25 12:12 ` Rob Herring (Arm)
2025-07-25 19:50 ` Rob Herring (Arm)
2025-07-25 10:03 ` [PATCH 03/12] dt-bindings: display: st,stm32mp25-lvds: " Raphael Gallais-Pou
2025-07-29 16:31 ` Rob Herring
2025-07-25 10:03 ` [PATCH 04/12] dt-bindings: display: st,stm32mp25-lvds: add power-domains property Raphael Gallais-Pou
2025-07-29 16:31 ` Rob Herring (Arm)
2025-07-25 10:03 ` [PATCH 05/12] dt-bindings: arm: stm32: add required #clock-cells property Raphael Gallais-Pou
2025-07-29 16:32 ` Rob Herring (Arm)
2025-07-25 10:03 ` [PATCH 06/12] drm/stm: ltdc: support new hardware version for STM32MP25 SoC Raphael Gallais-Pou
2025-07-25 10:03 ` [PATCH 07/12] drm/stm: ltdc: handle lvds pixel clock Raphael Gallais-Pou
2025-07-25 10:04 ` [PATCH 08/12] arm64: dts: st: add ltdc support on stm32mp251 Raphael Gallais-Pou
2025-07-25 10:04 ` [PATCH 09/12] arm64: dts: st: add lvds support on stm32mp255 Raphael Gallais-Pou
2025-07-25 11:08 ` [Linux-stm32] " Clement LE GOFFIC
2025-07-25 11:13 ` Clement LE GOFFIC
2025-07-25 14:52 ` Raphael Gallais-Pou
2025-07-25 10:04 ` [PATCH 10/12] arm64: dts: st: add clock-cells to syscfg node on stm32mp251 Raphael Gallais-Pou
2025-07-25 10:04 ` [PATCH 11/12] arm64: dts: st: enable display support on stm32mp257f-ev1 board Raphael Gallais-Pou
2025-07-25 10:04 ` Raphael Gallais-Pou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250725-drm-misc-next-v1-12-a59848e62cf9@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=philippe.cornu@foss.st.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=will@kernel.org \
--cc=yannick.fertre@foss.st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).