From: Jocelyn Falempe <jfalempe@redhat.com>
To: 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>,
Jocelyn Falempe <jfalempe@redhat.com>,
Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH v2 0/3] drm/panic: Add kunit tests for drm_panic
Date: Mon, 8 Sep 2025 11:00:28 +0200 [thread overview]
Message-ID: <20250908090341.762049-1-jfalempe@redhat.com> (raw)
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).
Jocelyn Falempe (3):
drm/panic: Rename draw_panic_static_* to draw_panic_screen_*
drm/panic: Add kunit tests for drm_panic
drm/panic: Add a drm_panic/draw_test in debugfs
MAINTAINERS | 1 +
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/drm_panic.c | 150 +++++++++++++++++--
drivers/gpu/drm/tests/drm_panic_test.c | 198 +++++++++++++++++++++++++
4 files changed, 336 insertions(+), 15 deletions(-)
create mode 100644 drivers/gpu/drm/tests/drm_panic_test.c
base-commit: 685e8dae19df73d5400734ee5ad9e96470f9c0b4
--
2.51.0
next reply other threads:[~2025-09-08 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 9:00 Jocelyn Falempe [this message]
2025-09-08 9:00 ` [PATCH v2 1/3] drm/panic: Rename draw_panic_static_* to draw_panic_screen_* Jocelyn Falempe
2025-09-08 9:00 ` [PATCH v2 2/3] drm/panic: Add kunit tests for drm_panic Jocelyn Falempe
2025-09-10 8:33 ` Maxime Ripard
2025-09-10 15:16 ` Jocelyn Falempe
2025-09-23 9:57 ` Maxime Ripard
2025-09-25 15:50 ` Jocelyn Falempe
2025-09-08 9:00 ` [PATCH v2 3/3] drm/panic: Add a drm_panic/draw_test in debugfs Jocelyn Falempe
2025-09-10 10:49 ` Maxime Ripard
2025-09-11 12:00 ` Jocelyn Falempe
2025-09-23 10:15 ` Maxime Ripard
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=20250908090341.762049-1-jfalempe@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.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
all inboxes | Powered by JetHome®