From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: hs@denx.de, abelvesa@kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@denx.de>
Subject: [PATCH 2/3] ARM: dts: imx6sx: Describe the default LCDIF1 parent
Date: Fri, 2 Jun 2023 19:16:03 -0300 [thread overview]
Message-ID: <20230602221604.155027-2-festevam@gmail.com> (raw)
In-Reply-To: <20230602221604.155027-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
A suitable default for the LCDIF parent is the PLL5 clock, so
describe it in the device tree.
The imx6sx clock driver harcodes PLL5 as the LCDIF1 parent, but
in preparation for removing such hardcoding, describe the parent
relationship via devicetree.
There are some boards that may want to use a different parent
for the LCDIF due to EMI reasons, for example.
With this approch, the user can change the LCDIF parent in the board
devicetree if needed.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
arch/arm/boot/dts/imx6sx.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dtsi
index 41c900929758..0d549e1f3ced 100644
--- a/arch/arm/boot/dts/imx6sx.dtsi
+++ b/arch/arm/boot/dts/imx6sx.dtsi
@@ -1305,6 +1305,10 @@ lcdif1: lcdif@2220000 {
<&clks IMX6SX_CLK_LCDIF_APB>,
<&clks IMX6SX_CLK_DISPLAY_AXI>;
clock-names = "pix", "axi", "disp_axi";
+ assigned-clocks = <&clks IMX6SX_CLK_LCDIF1_PRE_SEL>,
+ <&clks IMX6SX_CLK_LCDIF1_SEL>;
+ assigned-clock-parents = <&clks IMX6SX_CLK_PLL5_VIDEO_DIV>,
+ <&clks IMX6SX_CLK_LCDIF1_PODF>;
power-domains = <&pd_disp>;
status = "disabled";
--
2.34.1
next prev parent reply other threads:[~2023-06-02 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 22:16 [PATCH 1/3] ARM: dts: imx6sx: Remove LDB endpoint Fabio Estevam
2023-06-02 22:16 ` Fabio Estevam [this message]
2023-06-02 22:16 ` [PATCH 3/3] clk: imx: imx6sx: Remove hardcoded LCDIF1 parent Fabio Estevam
2023-06-09 0:24 ` Stephen Boyd
2023-06-09 3:17 ` Fabio Estevam
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=20230602221604.155027-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=abelvesa@kernel.org \
--cc=festevam@denx.de \
--cc=hs@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=shawnguo@kernel.org \
/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).