[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251216082524.115980-1-jfalempe@redhat.com>
Date: Tue, 16 Dec 2025 09:20:37 +0100
From: Jocelyn Falempe <jfalempe@...hat.com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Jocelyn Falempe <jfalempe@...hat.com>,
Javier Martinez Canillas <javierm@...hat.com>,
linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: [PATCH v4 0/2] drm/panic: Add kunit tests for drm_panic
This series adds some kunit tests to drm_panic, and a debugfs interface to easily test the panic screen rendering at different resolutions/pixel format.
The kunit tests draws the panic screens to different framebuffer size and format, and ensure it doesn't crash or draw outside of the buffer.
However it doesn't check the resulting image, because it depends on other Kconfig options, like logo, fonts, or panic colors.
v2:
* Use debugfs instead of sending the framebuffer through the kunit logs. (Thomas Zimmermann).
* Add a few checks, and more comments in the kunit tests. (Maxime Ripard).
v3:
* Check the framebuffer content in drm_test_panic_screen_user_page().
* Fix memory leaks, when the test fails (Maxime Ripard).
v4:
* Run QR code test only if QR code panic screen is built.
* Drop the last patch to add a draw_test debugfs.
Jocelyn Falempe (2):
drm/panic: Rename draw_panic_static_* to draw_panic_screen_*
drm/panic: Add kunit tests for drm_panic
MAINTAINERS | 1 +
drivers/gpu/drm/drm_panic.c | 22 ++-
drivers/gpu/drm/tests/drm_panic_test.c | 220 +++++++++++++++++++++++++
3 files changed, 234 insertions(+), 9 deletions(-)
create mode 100644 drivers/gpu/drm/tests/drm_panic_test.c
base-commit: 20de1b0080b9889094d703927871da8f21fb624e
--
2.52.0
Powered by blists - more mailing lists