From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
"Lukas F . Hartmann" <lukas@mntmn.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stefan Agner <stefan@agner.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
imx@lists.linux.dev, kernel@dh-electronics.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm: lcdif: Use adjusted_mode .clock instead of .crtc_clock
Date: Sat, 6 Jul 2024 02:16:58 +0200 [thread overview]
Message-ID: <ab2eb32e-a458-4c9b-8324-27ccb00336c5@denx.de> (raw)
In-Reply-To: <1897634.CQOukoFCf9@steina-w>
On 6/24/24 11:19 AM, Alexander Stein wrote:
> Am Freitag, 31. Mai 2024, 22:27:21 CEST schrieb Marek Vasut:
>> In case an upstream bridge modified the required clock frequency
>> in its .atomic_check callback by setting adjusted_mode.clock ,
>> make sure that clock frequency is generated by the LCDIFv3 block.
>>
>> This is useful e.g. when LCDIFv3 feeds DSIM which feeds TC358767
>> with (e)DP output, where the TC358767 expects precise timing on
>> its input side, the precise timing must be generated by the LCDIF.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>
> With the other rc358767 patches in place, this does the trick.
> Reviewed-by: Alexander Stein <alexander.stein@ew.tq-group.com>
I'll pick this up next week if there is no objection.
next prev parent reply other threads:[~2024-07-06 0:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 20:27 [PATCH] drm: lcdif: Use adjusted_mode .clock instead of .crtc_clock Marek Vasut
2024-06-24 9:19 ` Alexander Stein
2024-07-06 0:16 ` Marek Vasut [this message]
2024-10-07 17:01 ` Isaac Scott
2024-10-07 18:06 ` Marek Vasut
2024-10-08 10:07 ` Isaac Scott
2024-10-08 14:37 ` Marek Vasut
2024-10-08 21:48 ` Marek Vasut
2024-10-09 9:55 ` Isaac Scott
2024-10-09 15:47 ` Marek Vasut
2024-10-09 15:58 ` Isaac Scott
2024-10-10 0:38 ` Marek Vasut
2024-10-10 5:31 ` Liu Ying
2024-10-10 15:54 ` Isaac Scott
2024-10-10 16:02 ` Isaac Scott
2024-10-10 17:29 ` Marek Vasut
2024-10-11 3:10 ` Liu Ying
2024-10-12 20:37 ` Marek Vasut
2024-10-19 21:49 ` Kieran Bingham
2024-10-20 2:49 ` Marek Vasut
2024-10-21 11:10 ` Kieran Bingham
2024-10-21 21:00 ` Marek Vasut
2024-10-21 11:48 ` Maxime Ripard
2024-10-21 21:07 ` 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=ab2eb32e-a458-4c9b-8324-27ccb00336c5@denx.de \
--to=marex@denx.de \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lukas@mntmn.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=tzimmermann@suse.de \
/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