From: Jocelyn Falempe <jfalempe@redhat.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Lu Yao <yaolu@kylinos.cn>,
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: Tue, 1 Oct 2024 14:43:01 +0200 [thread overview]
Message-ID: <9f86a94a-02da-496d-81cd-5a2306520c6d@redhat.com> (raw)
In-Reply-To: <8a1afe12-4d59-4cbd-aede-fce22f8fb979@redhat.com>
On 25/09/2024 10:33, Jocelyn Falempe wrote:
> On 24/09/2024 16:02, Alex Deucher wrote:
>> On Fri, Sep 20, 2024 at 11:36 AM Jocelyn Falempe <jfalempe@redhat.com>
>> wrote:
>>>
>>> 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 ?
>>
>> It just means that the application does not need CPU access. Whether
>> or not the CPU can access the buffer or not depends on the size of the
>> PCI BAR. E.g., if the driver or bios has resized the PCI BAR, then
>> the CPU can access the entire BAR, but if not you are generally
>> limited to the first 256M of framebuffer.
>
> I tried to use ttm_bo_kmap() anyway, it returns a valid virtual address,
> but writing to it has no effect on the display.
>>
>>>
>>> Also I don't know if there is a similar way to disable
>>> tiling/compression on this hardware.
>>
>> UNP_GRPH_CONTROL on chips with DCE display hardware and
>> DCSURF_ADDR_CONFIG and DCSURF_TILING_CONFIG on DCN display hardware.
I've now a working Prototype on a Radeon pro W6400.
Here is what I do to disable tiling:
REG_UPDATE(DCHUBP_REQ_SIZE_CONFIG, SWATH_HEIGHT, 0);
REG_UPDATE(DCSURF_TILING_CONFIG, SW_MODE, DC_SW_LINEAR);
REG_UPDATE_6(DCSURF_SURFACE_CONTROL,
PRIMARY_SURFACE_DCC_EN, 0,
PRIMARY_SURFACE_DCC_IND_BLK, 0,
PRIMARY_SURFACE_DCC_IND_BLK_C, 0,
SECONDARY_SURFACE_DCC_EN, 0,
SECONDARY_SURFACE_DCC_IND_BLK, 0,
SECONDARY_SURFACE_DCC_IND_BLK_C, 0);
I also need to call this, to refresh the display:
hubp->funcs->hubp_program_surface_flip_and_addr(hubp,
&dc_plane_state->address, dc_plane_state->flip_immediate);
And I use a modified version of amdgpu_ttm_access_memory() to write to
the framebuffer.
I will send a patch when I've time to make a clean version.
Best regards,
--
Jocelyn
next prev parent reply other threads:[~2024-10-01 12:43 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
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 [this message]
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=9f86a94a-02da-496d-81cd-5a2306520c6d@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®