From: Jocelyn Falempe <jfalempe@redhat.com>
To: Ryosuke Yasuoka <ryasuoka@redhat.com>,
kraxel@redhat.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch
Cc: virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH drm-next] drm/bochs: Add support for drm_panic
Date: Thu, 19 Jun 2025 08:12:41 +0200 [thread overview]
Message-ID: <30f0ea0c-d8fb-461e-86ab-6e7677beac3c@redhat.com> (raw)
In-Reply-To: <20250613132023.106946-1-ryasuoka@redhat.com>
On 13/06/2025 15:20, Ryosuke Yasuoka wrote:
> Add drm_panic moudle for bochs drm so that panic screen can be displayed
> on panic.
Thanks for the patch, it's simple and looks good to me.
Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
If no objections, I will push it next Monday.
Best regards,
--
Jocelyn
>
> Signed-off-by: Ryosuke Yasuoka <ryasuoka@redhat.com>
> ---
> drivers/gpu/drm/tiny/bochs.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/gpu/drm/tiny/bochs.c b/drivers/gpu/drm/tiny/bochs.c
> index 8706763af8fb..ed42ad5c4927 100644
> --- a/drivers/gpu/drm/tiny/bochs.c
> +++ b/drivers/gpu/drm/tiny/bochs.c
> @@ -19,6 +19,7 @@
> #include <drm/drm_gem_shmem_helper.h>
> #include <drm/drm_managed.h>
> #include <drm/drm_module.h>
> +#include <drm/drm_panic.h>
> #include <drm/drm_plane_helper.h>
> #include <drm/drm_probe_helper.h>
>
> @@ -469,10 +470,28 @@ static void bochs_primary_plane_helper_atomic_update(struct drm_plane *plane,
> bochs_hw_setformat(bochs, fb->format);
> }
>
> +static int bochs_primary_plane_helper_get_scanout_buffer(struct drm_plane *plane,
> + struct drm_scanout_buffer *sb)
> +{
> + struct bochs_device *bochs = to_bochs_device(plane->dev);
> + struct iosys_map map = IOSYS_MAP_INIT_VADDR_IOMEM(bochs->fb_map);
> +
> + if (plane->state && plane->state->fb) {
> + sb->format = plane->state->fb->format;
> + sb->width = plane->state->fb->width;
> + sb->height = plane->state->fb->height;
> + sb->pitch[0] = plane->state->fb->pitches[0];
> + sb->map[0] = map;
> + return 0;
> + }
> + return -ENODEV;
> +}
> +
> static const struct drm_plane_helper_funcs bochs_primary_plane_helper_funcs = {
> DRM_GEM_SHADOW_PLANE_HELPER_FUNCS,
> .atomic_check = bochs_primary_plane_helper_atomic_check,
> .atomic_update = bochs_primary_plane_helper_atomic_update,
> + .get_scanout_buffer = bochs_primary_plane_helper_get_scanout_buffer,
> };
>
> static const struct drm_plane_funcs bochs_primary_plane_funcs = {
>
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
next prev parent reply other threads:[~2025-06-19 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 13:20 [PATCH drm-next] drm/bochs: Add support for drm_panic Ryosuke Yasuoka
2025-06-19 6:12 ` Jocelyn Falempe [this message]
2025-06-19 6:37 ` Ryosuke Yasuoka
2025-06-19 6:42 ` Jocelyn Falempe
2025-06-23 10:12 ` Jocelyn Falempe
2025-07-14 0:04 ` Askar Safin
2025-07-15 8:57 ` Jocelyn Falempe
2025-07-15 20:35 ` Askar Safin
2025-07-15 22:00 ` Jocelyn Falempe
2025-07-16 21:48 ` Askar Safin
2025-07-17 9:54 ` Jocelyn Falempe
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=30f0ea0c-d8fb-461e-86ab-6e7677beac3c@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ryasuoka@redhat.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).