From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Martin Kepplinger <martink@posteo.de>
Cc: Nikolaus Voss <nv@vosn.de>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Liu Ying <victor.liu@nxp.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Fabio Estevam <festevam@denx.de>, Marek Vasut <marex@denx.de>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
nikolaus.voss@haag-streit.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] drm: bridge: fsl-ldb: fixup mode on freq mismatch
Date: Mon, 23 Dec 2024 20:01:22 +0100 [thread overview]
Message-ID: <87ldw6rzp9.fsf@bootlin.com> (raw)
In-Reply-To: <80cdb6d83f37c1c87a71ad567b2c4f2433219465.camel@posteo.de> (Martin Kepplinger's message of "Thu, 19 Dec 2024 12:39:05 +0000")
Hello Martin,
On 19/12/2024 at 12:39:05 GMT, Martin Kepplinger <martink@posteo.de> wrote:
> Am Donnerstag, dem 19.12.2024 um 11:54 +0100 schrieb Nikolaus Voss:
>> LDB clock has to be a fixed multiple of the pixel clock.
>> Although LDB and pixel clock have a common source, this
>> constraint cannot be satisfied for any pixel clock at a
>> fixed source clock.
>>
>> Violating this constraint leads to flickering and distorted
>> lines on the attached display.
>>
>> To overcome this, there are these approches:
>>
>> 1. Modify the base PLL clock statically by changing the
>> device tree, implies calculating the PLL clock by
>> hand, e.g. commit 4fbb73416b10 ("arm64: dts:
>> imx8mp-phyboard-pollux: Set Video PLL1 frequency to 506.8 MHz")
>>
>> 2. Walk down the clock tree and modify the source clock.
>> Proposed patch series by Miquel Raynal:
>> [PATCH 0/5] clk: Fix simple video pipelines on i.MX8
>>
>> 3. This patch: check constraint violation in
>> drm_bridge_funcs.atomic_check() and adapt the pixel
>> clock in drm_display_mode.adjusted_mode accordingly.
>>
>> Fixes: 463db5c2ed4a ("drm: bridge: ldb: Implement simple Freescale
>> i.MX8MP LDB bridge")
>> Cc: <stable@vger.kernel.org> # 6.12.x, 6.6.x
>> Signed-off-by: Nikolaus Voss <nv@vosn.de>
>>
>> ---
I didn't investigate further, but FYI this approach does not fix my
situation with iMX8MP. I am not saying it's wrong, because I am not
experienced enough with drm, but at least that it is not a replacement
of point #2 above.
Cheers,
Miquèl
prev parent reply other threads:[~2024-12-23 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 10:54 [PATCH v4] drm: bridge: fsl-ldb: fixup mode on freq mismatch Nikolaus Voss
2024-12-19 12:39 ` Martin Kepplinger
2024-12-23 19:01 ` Miquel Raynal [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=87ldw6rzp9.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@denx.de \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=marex@denx.de \
--cc=martink@posteo.de \
--cc=neil.armstrong@linaro.org \
--cc=nikolaus.voss@haag-streit.com \
--cc=nv@vosn.de \
--cc=rfoss@kernel.org \
--cc=victor.liu@nxp.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