From: Lu Yao <yaolu@kylinos.cn>
To: alexdeucher@gmail.com
Cc: Xinhui.Pan@amd.com, airlied@gmail.com, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
ckoenig.leichtzumerken@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, jfalempe@redhat.com,
linux-kernel@vger.kernel.org, srinivasan.shanmugam@amd.com,
sunil.khatri@amd.com, yaolu@kylinos.cn
Subject: Re: [PATCH] drm/amdgpu: add dce6 drm_panic support
Date: Mon, 12 Aug 2024 10:10:45 +0800 [thread overview]
Message-ID: <20240812021045.36009-1-yaolu@kylinos.cn> (raw)
In-Reply-To: <CADnq5_PDBZ9APfCpSMOSMPQWzcOeLqw_LngE2BBSOxv__7miGA@mail.gmail.com>
On Thu, Aug 8, 2024 at 13:24 PM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> On Thu, Aug 8, 2024 at 12:43 PM Alex Deucher <alexdeucher@gmail.com> wrote:
> >
> > On Thu, Aug 8, 2024 at 2:35 AM Lu Yao <yaolu@kylinos.cn> wrote:
> > >
> > > On 2024/8/5 17:25, Jocelyn Falempe wrote:
> > > >
> > > >
> > > > On 02/08/2024 11:39, Christian König wrote:
> > > >> Am 02.08.24 um 09:17 schrieb Lu Yao:
> > > >>> 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>
> > > >>> ---
> > > >>> drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 32
> > > >>> +++++++++++++++++++++++++++
> > > >>> 1 file changed, 32 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..12c3801c264a 100644
> > > >>> --- a/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
> > > >>> +++ b/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
> > > >>> @@ -28,6 +28,8 @@
> > > >>> #include <drm/drm_modeset_helper.h>
> > > >>> #include <drm/drm_modeset_helper_vtables.h>
> > > >>> #include <drm/drm_vblank.h>
> > > >>> +#include <drm/drm_panic.h>
> > > >>
> > > >>> +#include "../../drm_internal.h"
> > > >>
> > > >> Well that this file is named "internal" and not in a common include
> > > >> directory is a strong indicator that you should absolutely *not*
> > > >> include it in a driver.
> > > >>
> > > >>> #include "amdgpu.h"
> > > >>> #include "amdgpu_pm.h"
> > > >>> @@ -2600,6 +2602,35 @@ 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 drm_gem_object *obj;
> > > >>> + struct amdgpu_bo *abo;
> > > >>> + int ret = 0;
> > > >>> +
> > > >>> + if (!plane->fb || plane->fb->modifier != DRM_FORMAT_MOD_LINEAR)
> > > >>> + return -ENODEV;
> > > >>> +
> > > >>> + fb = plane->fb;
> > > >>> + sb->width = fb->width;
> > > >>> + sb->height = fb->height;
> > > >>> + sb->format = fb->format;
> > > >>> + sb->pitch[0] = fb->pitches[0];
> > > >>> +
> > > >>> + obj = fb->obj[0];
> > > >>> + abo = gem_to_amdgpu_bo(obj);
> > > >>> + if (!abo || abo->flags & AMDGPU_GEM_CREATE_NO_CPU_ACCESS)
> > > >>> + return -EINVAL;
> > > >>> +
> > > >>> + return drm_gem_vmap(obj, &sb->map[0]);
> > > >>
> > > >> Yeah that will almost always not work. Most display buffers are
> > > >> tilled and not CPU accessible.
> > > >
> > > > For the CPU accessible issue, Christian mentioned there was a debug
> > > > interface on AMD GPU that can be used, to work around this:
> > > >
> > > > https://lore.kernel.org/dri-devel/0baabe1f-8924-2c9a-5cd4-59084a37dbb2@gmail.com/
> > > > and
> > > > https://lore.kernel.org/dri-devel/d233c376-ed07-2127-6084-8292d313dac7@amd.com/
> > > >
> > > > And you will need to use the scanout_buffer->set_pixel() callback to
> > > > write the pixels one by one, similar to what I've tried for nouveau with
> > > > https://patchwork.freedesktop.org/series/133963/
> > > >
> > > > For the tiling format, the problem is that it is internal to the GPU,
> > > > and currently the driver don't know which tiling format is being used.
> > > >
> > > > It might be possible to disable tiling and compression, but it
> > > > requires some internal DC knowledge:
> > > > https://lore.kernel.org/dri-devel/f76a3297-7d63-8615-45c5-47f02b64a1d5@amd.com/
> > > >
> > > >
> > > > Best regards,
> > >
> > > From the discussion provided, it is difficult to implement this feature without the relevant data book and knowledge.(Whether how tiled memory storage, or how to disable tiling of DC)
> >
> > For DCE 6, the GRPH_ARRAY_MODE field in mmGRPH_CONTROL controls the
> > display tiling. Set that field to GRPH_ARRAY_LINEAR_GENERAL (0) to
> > disable tiling.
>
> For clarity that register is instanced so use mmGRPH_CONTROL +
> amdgpu_crtc->crtc_offset to get the right instance.
>
It works, I'll submit a new patch soon.
Thanks,
Lu Yao
> Alex
next prev parent reply other threads:[~2024-08-12 2:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 7:17 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 [this message]
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
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=20240812021045.36009-1-yaolu@kylinos.cn \
--to=yaolu@kylinos.cn \
--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=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunil.khatri@amd.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
all inboxes | Powered by JetHome®