From: Johannes Schneider <johannes.schneider@leica-geosystems.com>
To: barebox@lists.infradead.org, a.fatoum@pengutronix.de,
mgr@kernel.org, l.stach@pengutronix.de
Cc: thomas.haemmerle@leica-geosystems.com
Subject: [PATCH v2 09/11] video: lcdif: drain write-combine framebuffer in fb_damage
Date: Thu, 4 Jun 2026 06:50:04 +0000 [thread overview]
Message-ID: <20260604065006.2933142-10-johannes.schneider@leica-geosystems.com> (raw)
In-Reply-To: <20260604065006.2933142-1-johannes.schneider@leica-geosystems.com>
From: Thomas Haemmerle <thomas.haemmerle@leica-geosystems.com>
The framebuffer is allocated Normal Non-Cacheable (write-combine).
After the splash command's memcpy() from a cached shadow buffer into
the hardware framebuffer (see gu_screen_blit()), stores may still
reside in the CPU write-combine buffer when scanout next fetches --
visible as partial / corrupted rendering at the bottom of the image.
dsb() alone is not sufficient: it orders subsequent instructions
against the outstanding writes but doesn't actively drain the WC
buffer to memory. A readback of any byte inside the WC region does,
since the load cannot complete until prior stores to the buffer have
been retired.
Wire lcdif_fb_damage to do that readback after each blit. Keep
fb_flush bound to lcdif_crtc_atomic_flush so the SHADOW_LOAD_EN
re-latch still fires on fb_close / fbtest paths.
Suggested-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Thomas Haemmerle <thomas.haemmerle@leica-geosystems.com>
---
drivers/video/lcdif_kms.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/video/lcdif_kms.c b/drivers/video/lcdif_kms.c
index e3d1985dc9..57ca92b4be 100644
--- a/drivers/video/lcdif_kms.c
+++ b/drivers/video/lcdif_kms.c
@@ -396,10 +396,17 @@ static void lcdif_disable_fb_controller(struct fb_info *info)
lcdif_disable_controller(lcdif);
}
+static void lcdif_fb_damage(struct fb_info *info, const struct fb_rect *rect)
+{
+ /* readback drains the write-combine buffer (dsb() doesn't) */
+ (void)*(volatile u8 *)info->screen_base;
+}
+
static struct fb_ops lcdif_fb_ops = {
.fb_enable = lcdif_enable_fb_controller,
.fb_disable = lcdif_disable_fb_controller,
.fb_flush = lcdif_crtc_atomic_flush,
+ .fb_damage = lcdif_fb_damage,
};
/* -----------------------------------------------------------------------------
--
2.43.0
next prev parent reply other threads:[~2026-06-04 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 6:49 [PATCH v2 00/11] video: enable boot splash on i.MX8MP with LVDS panel Johannes Schneider
2026-06-04 6:49 ` [PATCH v2 01/11] clk: imx8mp: add 700 MHz rate entry for VIDEO_PLL1 Johannes Schneider
2026-06-04 6:49 ` [PATCH v2 02/11] clk: imx8mp: add 1039.5 MHz and 519.75 MHz rate entries " Johannes Schneider
2026-06-04 6:49 ` [PATCH v2 03/11] pmdomain: imx8mp-blk-ctrl: add media blk-ctrl power domain support Johannes Schneider
2026-06-04 6:49 ` [PATCH v2 04/11] video: backlight-pwm: make power-supply and enable-gpio optional Johannes Schneider
2026-06-04 6:50 ` [PATCH v2 05/11] video: lcdif: make functional on i.MX8MP Johannes Schneider
2026-06-04 6:50 ` [PATCH v2 06/11] video: lcdif: use 128B AXI bursts to avoid right-edge gap Johannes Schneider
2026-06-04 6:50 ` [PATCH v2 07/11] video: lcdif: default to RGB888_1X24 on VPL_GET_BUS_FORMAT failure Johannes Schneider
2026-06-04 6:50 ` [PATCH v2 08/11] video: lcdif: register simplefb fixup and enable framebuffer at probe Johannes Schneider
2026-06-04 6:50 ` Johannes Schneider [this message]
2026-06-04 6:50 ` [PATCH v2 10/11] video: simple-panel: support panel-lvds DT bindings Johannes Schneider
2026-06-04 6:50 ` [PATCH v2 11/11] video: simple-panel: lazily resolve backlight without failing Johannes Schneider
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=20260604065006.2933142-10-johannes.schneider@leica-geosystems.com \
--to=johannes.schneider@leica-geosystems.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
--cc=mgr@kernel.org \
--cc=thomas.haemmerle@leica-geosystems.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