From: Marek Vasut <marex@nabladev.com>
To: "Krzysztof Hałasa" <khalasa@piap.pl>,
"Stefan Agner" <stefan@agner.ch>, "Liu Ying" <victor.liu@nxp.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: i.MX8MP: Fix HDMI LCDIF FIFO underruns
Date: Fri, 20 Mar 2026 03:39:35 +0100 [thread overview]
Message-ID: <32317022-3c44-4ead-9e2d-04caa12b28cb@nabladev.com> (raw)
In-Reply-To: <m3ms04caaj.fsf@t19.piap.pl>
On 3/19/26 12:45 PM, Krzysztof Hałasa wrote:
> Running (and terminating) Weston on i.MX8MP sometimes produced black
> or grey screens. The LCDIF3 INT_STATUS_D0 register showed a FIFO underrun:
>
> 32FC6024: 1000002
>
> The PANIC0_THRES register was set to:
>
> 32FC6238: AA0154
>
> which apparently meant low = 2736 bytes (0xAA * 16 + 16), high = 5456 bytes
> (0x154 * 16 + 16).
>
> With this patch (based on NXP's driver) the watermarks are only 16 bytes
> higher (register values increased by 1) and the underruns are gone.
>
> Tested on Solidrun Hummingboard Mate with a 1080p60 HDMI display.
>
> Signed-off-by: Krzysztof Hałasa <khalasa@piap.pl>
>
> --- a/drivers/gpu/drm/mxsfb/lcdif_kms.c
> +++ b/drivers/gpu/drm/mxsfb/lcdif_kms.c
> @@ -353,8 +353,8 @@ static void lcdif_enable_controller(struct lcdif_drm_private *lcdif)
> u32 reg;
>
> /* Set FIFO Panic watermarks, low 1/3, high 2/3 . */
> - writel(FIELD_PREP(PANIC0_THRES_LOW_MASK, 1 * PANIC0_THRES_MAX / 3) |
> - FIELD_PREP(PANIC0_THRES_HIGH_MASK, 2 * PANIC0_THRES_MAX / 3),
> + writel(FIELD_PREP(PANIC0_THRES_LOW_MASK, DIV_ROUND_UP(1 * PANIC0_THRES_MAX, 3)) |
> + FIELD_PREP(PANIC0_THRES_HIGH_MASK, DIV_ROUND_UP(2 * PANIC0_THRES_MAX, 3)),
I am starting to wonder, whether this should be configurable in DT,
because it seems there might be users that need to tweak the watermarks
one way or the other for different video outputs ?
+CC Liu
next prev parent reply other threads:[~2026-03-20 3:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 11:45 Krzysztof Hałasa
2026-03-20 2:39 ` Marek Vasut [this message]
2026-03-20 8:04 ` Marco Felsch
2026-03-20 9:25 ` Maxime Ripard
2026-03-20 13:20 ` Krzysztof Hałasa
2026-03-23 8:18 ` Liu Ying
2026-03-23 12:54 ` Krzysztof Hałasa
2026-03-30 16:20 ` Paul Kocialkowski
2026-03-25 12:40 ` Krzysztof Hałasa
2026-03-30 16:09 ` Paul Kocialkowski
2026-03-30 16:44 ` Lucas Stach
2026-03-30 21:16 ` Paul Kocialkowski
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=32317022-3c44-4ead-9e2d-04caa12b28cb@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@nxp.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=khalasa@piap.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=simona@ffwll.ch \
--cc=stefan@agner.ch \
--cc=tzimmermann@suse.de \
--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
all inboxes | Powered by JetHome®