From: Marek Vasut <marex@denx.de>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Abel Vesa <abelvesa@kernel.org>,
linux-clk@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
"Lukas F . Hartmann" <lukas@mntmn.com>,
Michael Turquette <mturquette@baylibre.com>,
Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
imx@lists.linux.dev, kernel@dh-electronics.com,
linux-arm-kernel@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Anson Huang <Anson.Huang@nxp.com>
Subject: Re: [PATCH] clk: imx: clk-imx8mp: Allow media_disp pixel clock reconfigure parent rate
Date: Sat, 16 Nov 2024 20:47:07 +0100 [thread overview]
Message-ID: <6bc5b8d7-ff10-4860-ac46-1460a7d850da@denx.de> (raw)
In-Reply-To: <20241115180936.4ab56be3@booty>
On 11/15/24 6:09 PM, Luca Ceresoli wrote:
> Hi Marek,
Hi,
>> Commit 4fbb73416b10 ("arm64: dts: imx8mp-phyboard-pollux: Set Video PLL1
>> frequency to 506.8 MHz") configures the Video PLL1 to a frequency from
>> which both your panel pixel clock and LDB serializer clock can be
>> successfully divided down.
>>
>> Which panel do you use ?
>>
>> Try this -- Revert this patch, check /sys/kernel/debug/clk/clk_summary
>> and compare it with (I assume) panel-simple.c entry for the panel you
>> use, and notice the disp_pix clock are likely a bit off. That's because
>> the lcdif driver did its best to divide those pixel clock down from
>> 1039500000 set in imx8mp.dtsi .
>>
>> If you really want accurate pixel clock for your panel, you need similar
>> change to 4fbb73416b10 and configure the Video PLL such that the
>> accurate pixel clock can be derived from it. The Video PLL cannot be set
>> to pixel clock, because the LDB serializer clock are either 7x the pixel
>> clock, or 3.5x the pixel clock (for dual link LVDS), so the Video PLL
>> has to be set to 7x or 3.5x pixel clock of the panel, then you should
>> get accurate pixel clock and a working panel again.
>
> I found that I'm having the same issue that has been discussed in some
> related threads: the lcdif2 configures the video_pll1 to ~72 MHz, and
> later LDB tries to set it to 7x that value, failing.
Right, which is solved by configuring the Video PLL to the correct
frequency in DT up front ... unless you have more than one output
supplied by that Video PLL.
> I would have guessed your "[PATCH 1/2] clk: imx: clk-imx8mp: Allow LDB
> serializer clock reconfigure parent rate" would have fixed it, and it
> actually allwos the LDB to set a proper (7x) rate for video_pll1, but
> then also the media_disp2 goes to the same rate. Apparently the
> video_pll1 is not propagated to media_disp2. I haven't dug into this.
>
> So this is not the bug I had suspected about video_pll1 rate
> computation.
>
> For now my workaround is to set the exact rate to video_pll1 via
> assigned-clock-rates.
>
> However this breaks the case of using both lcdif1 and lcdif2. For that
> I have added a reparenting of media_disp1 to sys_pll3 and it looks like
> working.
See the patch link in the previous email, if you can use one Audio PLL
as PLL for the other DISP PIX, then you will be able to achieve accurate
pixel clock on both outputs. Can you do that ?
> Would you mind keeping Miquèl and me in Cc in following discussions
> about the imx8mp video clocks? We are also facing this topic and we are
> happy to contribute.
Sure
next prev parent reply other threads:[~2024-11-16 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 20:26 [PATCH] clk: imx: clk-imx8mp: Allow media_disp pixel clock reconfigure parent rate Marek Vasut
2024-06-21 4:48 ` Abel Vesa
2024-06-21 6:38 ` Abel Vesa
2024-06-21 17:52 ` Adam Ford
2024-06-21 20:22 ` Marek Vasut
2024-11-12 22:42 ` Luca Ceresoli
2024-11-12 23:14 ` Marek Vasut
2024-11-13 11:06 ` Luca Ceresoli
2024-11-13 21:19 ` Marek Vasut
2024-11-15 17:09 ` Luca Ceresoli
2024-11-16 19:47 ` Marek Vasut [this message]
2024-11-18 8:15 ` Miquel Raynal
2024-11-18 14:30 ` Marek Vasut
2024-11-19 15:41 ` Miquel Raynal
2024-11-19 21:21 ` Marek Vasut
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=6bc5b8d7-ff10-4860-ac46-1460a7d850da@denx.de \
--to=marex@denx.de \
--cc=Anson.Huang@nxp.com \
--cc=abelvesa@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=lukas@mntmn.com \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@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