[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50ee0207-b37a-4a6a-83fe-32a7a43645ce@denx.de>
Date: Mon, 2 Dec 2024 13:56:38 +0100
From: Marek Vasut <marex@...x.de>
To: Liu Ying <victor.liu@....nxp.com>, Nikolaus Voss <nv@...n.de>,
Alexander Stein <alexander.stein@...tq-group.com>,
Liu Ying <victor.liu@....com>, Luca Ceresoli <luca.ceresoli@...tlin.com>,
Fabio Estevam <festevam@...x.de>, Andrzej Hajda <andrzej.hajda@...el.com>,
Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Jonas Karlman <jonas@...boo.se>, Jernej Skrabec <jernej.skrabec@...il.com>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Luca Ceresoli <luca.ceresoli@...tlin.com>
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
nikolaus.voss@...g-streit.com
Subject: Re: [PATCH] drm: bridge: fsl-ldb: fixup mode on freq mismatch
On 12/2/24 7:32 AM, Liu Ying wrote:
> On 11/27/2024, Nikolaus Voss wrote:
>> LDB clock has to be a fixed multiple of the pixel clock.
>> As LDB and pixel clock are derived from different clock sources
>> (at least on imx8mp), this constraint cannot be satisfied for
>> any pixel clock, which leads to flickering and incomplete
>> lines on the attached display.
>>
>> To overcome this, check this condition in mode_fixup() and
>> adapt the pixel clock accordingly.
>>
>> Cc: <stable@...r.kernel.org>
>
> It looks like stable is not effectively Cc'ed.
> Need a Fixes tag?
Isn't this fix effectively superseded by series
[PATCH 0/5] clk: Fix simple video pipelines on i.MX8
?
Powered by blists - more mailing lists