From: Jocelyn Falempe <jfalempe@redhat.com>
To: Alex Deucher <alexdeucher@gmail.com>, Lu Yao <yaolu@kylinos.cn>
Cc: ckoenig.leichtzumerken@gmail.com, daniel@ffwll.ch,
Xinhui.Pan@amd.com, airlied@gmail.com, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
srinivasan.shanmugam@amd.com, sunil.khatri@amd.com
Subject: Re: [PATCH v2] drm/amdgpu: add dce6 drm_panic support
Date: Fri, 20 Sep 2024 17:36:26 +0200 [thread overview]
Message-ID: <16352ae0-7e61-440d-8c04-7ec912f9bf9a@redhat.com> (raw)
In-Reply-To: <CADnq5_OcUgV9dgAynDCQnm9NS+QCvhBiHvxWnhWqi2qqhh=zXg@mail.gmail.com>
On 17/09/2024 15:21, Alex Deucher wrote:
> On Mon, Aug 12, 2024 at 2:10 AM Lu Yao <yaolu@kylinos.cn> wrote:
>>
>> Add support for the drm_panic module, which displays a pretty user
>> friendly message on the screen when a Linux kernel panic occurs.
>>
>> Signed-off-by: Lu Yao <yaolu@kylinos.cn>
>
> Patch looks good to me. Any chance you want to convert the other
> non-DC dce files (dce_v8_0.c, dce_v10_0.c, dce_v11_0.c) while you are
> at it?
I've made a similar patch in amdgpu_dm_plane.c, and it works on a Radeon
pro w6400.
But it only works when I'm in a VT terminal (so the framebuffer is
linear and CPU accessible).
When under Gnome/Wayland, the flag AMDGPU_GEM_CREATE_NO_CPU_ACCESS is
set, so that means I can't vmap it ?
Also I don't know if there is a similar way to disable
tiling/compression on this hardware.
Best regards,
--
Jocelyn
>
> Alex
>
>
>> ---
>> Changes in v2:
>> 1. Drop include "drm_internal.h"
>> 2. Add disabling DC tiling ops.
>> Per suggestion from previous thread:
>> https://patchwork.freedesktop.org/patch/606879/?series=136832&rev=1
>> ---
>> drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 48 +++++++++++++++++++++++++++
>> 1 file changed, 48 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c b/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
>> index 05c0df97f01d..ba1b7a36caa3 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
>> @@ -28,6 +28,7 @@
>> #include <drm/drm_modeset_helper.h>
>> #include <drm/drm_modeset_helper_vtables.h>
>> #include <drm/drm_vblank.h>
>> +#include <drm/drm_panic.h>
>>
>> #include "amdgpu.h"
>> #include "amdgpu_pm.h"
>> @@ -2600,6 +2601,52 @@ static const struct drm_crtc_helper_funcs dce_v6_0_crtc_helper_funcs = {
>> .get_scanout_position = amdgpu_crtc_get_scanout_position,
>> };
>>
>> +static int dce_v6_0_drm_primary_plane_get_scanout_buffer(struct drm_plane *plane,
>> + struct drm_scanout_buffer *sb)
>> +{
>> + struct drm_framebuffer *fb;
>> + struct amdgpu_bo *abo;
>> + struct amdgpu_crtc *amdgpu_crtc;
>> + struct amdgpu_device *adev;
>> + uint32_t fb_format;
>> +
>> + if (!plane->fb)
>> + return -EINVAL;
>> +
>> + fb = plane->fb;
>> +
>> + abo = gem_to_amdgpu_bo(fb->obj[0]);
>> + amdgpu_crtc = to_amdgpu_crtc(plane->crtc);
>> + adev = drm_to_adev(fb->dev);
>> +
>> + if (!abo->kmap.virtual &&
>> + ttm_bo_kmap(&abo->tbo, 0, PFN_UP(abo->tbo.base.size), &abo->kmap)) {
>> + DRM_WARN("amdgpu bo map failed, panic won't be displayed\n");
>> + return -ENOMEM;
>> + }
>> +
>> + if (abo->kmap.bo_kmap_type & TTM_BO_MAP_IOMEM_MASK)
>> + iosys_map_set_vaddr_iomem(&sb->map[0], abo->kmap.virtual);
>> + else
>> + iosys_map_set_vaddr(&sb->map[0], abo->kmap.virtual);
>> +
>> + sb->width = fb->width;
>> + sb->height = fb->height;
>> + sb->format = fb->format;
>> + sb->pitch[0] = fb->pitches[0];
>> +
>> + /* Disable DC tiling */
>> + fb_format = RREG32(mmGRPH_CONTROL + amdgpu_crtc->crtc_offset);
>> + fb_format &= ~GRPH_ARRAY_MODE(0x7);
>> + WREG32(mmGRPH_CONTROL + amdgpu_crtc->crtc_offset, fb_format);
>> +
>> + return 0;
>> +}
>> +
>> +static const struct drm_plane_helper_funcs dce_v6_0_drm_primary_plane_helper_funcs = {
>> + .get_scanout_buffer = dce_v6_0_drm_primary_plane_get_scanout_buffer
>> +};
>> +
>> static int dce_v6_0_crtc_init(struct amdgpu_device *adev, int index)
>> {
>> struct amdgpu_crtc *amdgpu_crtc;
>> @@ -2627,6 +2674,7 @@ static int dce_v6_0_crtc_init(struct amdgpu_device *adev, int index)
>> amdgpu_crtc->encoder = NULL;
>> amdgpu_crtc->connector = NULL;
>> drm_crtc_helper_add(&amdgpu_crtc->base, &dce_v6_0_crtc_helper_funcs);
>> + drm_plane_helper_add(amdgpu_crtc->base.primary, &dce_v6_0_drm_primary_plane_helper_funcs);
>>
>> return 0;
>> }
>> --
>> 2.25.1
>>
>
next prev parent reply other threads:[~2024-09-20 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 7:17 [PATCH] " Lu Yao
2024-08-02 9:39 ` Christian König
2024-08-05 2:14 ` yaolu
2024-08-05 9:25 ` Jocelyn Falempe
2024-08-08 6:15 ` Lu Yao
2024-08-08 16:43 ` Alex Deucher
2024-08-08 17:24 ` Alex Deucher
2024-08-12 2:10 ` Lu Yao
2024-08-12 6:09 ` [PATCH v2] " Lu Yao
2024-09-17 12:25 ` Jocelyn Falempe
2024-09-17 13:21 ` Alex Deucher
2024-09-18 6:04 ` Lu Yao
2024-09-20 15:36 ` Jocelyn Falempe [this message]
2024-09-24 14:02 ` Alex Deucher
2024-09-25 7:55 ` Michel Dänzer
2024-09-25 8:33 ` Jocelyn Falempe
2024-10-01 12:43 ` Jocelyn Falempe
2024-10-29 14:28 ` Alex Deucher
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=16352ae0-7e61-440d-8c04-7ec912f9bf9a@redhat.com \
--to=jfalempe@redhat.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunil.khatri@amd.com \
--cc=yaolu@kylinos.cn \
/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®