[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <766908de-922c-4d71-bb04-29dbe4d1d64d@suse.de>
Date: Tue, 11 Jun 2024 09:50:55 +0200
From: Thomas Zimmermann <tzimmermann@...e.de>
To: Peng Fan <peng.fan@....com>, "Peng Fan (OSS)" <peng.fan@....nxp.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Javier Martinez Canillas <javierm@...hat.com>
Cc: "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/fbdev-dma: fix getting smem_start
Hi
Am 11.06.24 um 03:00 schrieb Peng Fan:
>> Subject: Re: [PATCH] drm/fbdev-dma: fix getting smem_start
>>
>> Hi
>>
>> Am 04.06.24 um 10:03 schrieb Peng Fan (OSS):
>>> From: Peng Fan <peng.fan@....com>
>>>
>>> If 'info->screen_buffer' locates in vmalloc address space,
>>> virt_to_page will not be able to get correct results. With
>>> CONFIG_DEBUG_VM and CONFIG_DEBUG_VIRTUAL enabled on ARM64,
>> there is dump below:
>>
>> Which graphics driver triggers this bug?
> It is NXP i.MX95 DPU driver which is still in NXP downstream repo.
Which DRM memory manager does that driver use?
I'm asking because if the driver allocates BOs via vmalloc(), should it
really use fbdev-dma?
Best regards
Thomas
>
> Thanks,
> Peng.
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
Powered by blists - more mailing lists