From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: Bilal Elmoussaoui <belmouss@redhat.com>,
Jocelyn Falempe <jfalempe@redhat.com>,
Enric Balletbo i Serra <eballetb@redhat.com>,
Christian Hergert <chergert@redhat.com>,
Albert Esteve <aesteve@redhat.com>, Chia-I Wu <olvaffe@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] drm/virtio: Enable fb damage clips property for the primary plane
Date: Fri, 10 Mar 2023 14:27:42 +0100 [thread overview]
Message-ID: <87fsac7n3l.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <6c556799-6a78-4b67-a4c7-4de0a8f082fa@suse.de>
Thomas Zimmermann <tzimmermann@suse.de> writes:
Hello Thomas,
> Hi Javier
>
> Am 10.03.23 um 13:59 schrieb Javier Martinez Canillas:
>> Christian Hergert reports that the driver doesn't enable the property and
>> that leads to always doing a full plane update, even when the driver does
>> support damage clipping for the primary plane.
>>
>> Don't enable it for the cursor plane, because its .atomic_update callback
>> doesn't handle damage clips.
>>
>> Reported-by: Christian Hergert <chergert@redhat.com>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
>> ---
>>
>> drivers/gpu/drm/virtio/virtgpu_plane.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c
>> index 4c09e313bebc..a2e045f3a000 100644
>> --- a/drivers/gpu/drm/virtio/virtgpu_plane.c
>> +++ b/drivers/gpu/drm/virtio/virtgpu_plane.c
>> @@ -390,5 +390,9 @@ struct drm_plane *virtio_gpu_plane_init(struct virtio_gpu_device *vgdev,
>
> virtio_gpu_plane_init() should really be two separate functions. But
> withing the constrains of the current code
>
Agreed, I thought the same. I may post a follow-up patch once this lands.
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
>
Thanks!
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-03-10 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 12:59 Javier Martinez Canillas
2023-03-10 13:20 ` Thomas Zimmermann
2023-03-10 13:27 ` Javier Martinez Canillas [this message]
2023-03-13 8:52 ` Gerd Hoffmann
2023-03-13 17:28 ` Javier Martinez Canillas
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=87fsac7n3l.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=aesteve@redhat.com \
--cc=airlied@redhat.com \
--cc=belmouss@redhat.com \
--cc=chergert@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eballetb@redhat.com \
--cc=gurchetansingh@chromium.org \
--cc=jfalempe@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olvaffe@gmail.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
/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®