From: Thomas Zimmermann <tzimmermann@suse.de>
To: Peng Fan <peng.fan@nxp.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/fbdev-dma: fix getting smem_start
Date: Tue, 11 Jun 2024 09:50:55 +0200 [thread overview]
Message-ID: <766908de-922c-4d71-bb04-29dbe4d1d64d@suse.de> (raw)
In-Reply-To: <AM6PR04MB59415B3F01D02024A255BFB988C72@AM6PR04MB5941.eurprd04.prod.outlook.com>
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@nxp.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)
next prev parent reply other threads:[~2024-06-11 7:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 8:03 [PATCH] drm/fbdev-dma: fix getting smem_start Peng Fan (OSS)
2024-06-10 8:47 ` Thomas Zimmermann
2024-06-11 1:00 ` Peng Fan
2024-06-11 7:50 ` Thomas Zimmermann [this message]
2024-06-11 8:23 ` Peng Fan
2024-06-11 9:29 ` Thomas Zimmermann
2024-06-12 8:45 ` Daniel Vetter
2024-06-12 13:03 ` Thomas Zimmermann
2024-06-12 6:48 ` Thomas Zimmermann
2024-06-12 7:49 ` Javier Martinez Canillas
2024-06-12 8:37 ` Thomas Zimmermann
2024-06-12 15:00 ` Daniel Vetter
2024-06-13 10:14 ` Thomas Zimmermann
2024-06-13 10:18 ` Thomas Zimmermann
2024-06-17 14:04 ` Daniel Vetter
2024-06-17 14:26 ` Thomas Zimmermann
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=766908de-922c-4d71-bb04-29dbe4d1d64d@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.