From: "Martin Krastev (VMware)" <martinkrastev768@gmail.com>
To: Zack Rusin <zackr@vmware.com>, dri-devel@lists.freedesktop.org
Cc: javierm@redhat.com, banackm@vmware.com, krastevm@vmware.com,
ppaalanen@gmail.com, iforbes@vmware.com, mombasawalam@vmware.com
Subject: Re: [PATCH v3 3/8] drm/vmwgfx: Use the hotspot properties from cursor planes
Date: Tue, 27 Jun 2023 16:08:20 +0300 [thread overview]
Message-ID: <1e7aa2c9-9de4-cd14-1068-5b05f081f82e@gmail.com> (raw)
In-Reply-To: <20230627035839.496399-4-zack@kde.org>
From: Martin Krastev <krastevm@vmware.com>
Looks good.
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Regards,
Martin
On 27.06.23 г. 6:58 ч., Zack Rusin wrote:
> From: Zack Rusin <zackr@vmware.com>
>
> Atomic modesetting got support for mouse hotspots via the hotspot
> properties. Port the legacy kms hotspot handling to the new properties
> on cursor planes.
>
> Signed-off-by: Zack Rusin <zackr@vmware.com>
> Cc: Martin Krastev <krastevm@vmware.com>
> Cc: Maaz Mombasawala <mombasawalam@vmware.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> index b62207be3363..de294dfe05d0 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
> @@ -768,13 +768,8 @@ vmw_du_cursor_plane_atomic_update(struct drm_plane *plane,
> struct vmw_plane_state *old_vps = vmw_plane_state_to_vps(old_state);
> s32 hotspot_x, hotspot_y;
>
> - hotspot_x = du->hotspot_x;
> - hotspot_y = du->hotspot_y;
> -
> - if (new_state->fb) {
> - hotspot_x += new_state->fb->hot_x;
> - hotspot_y += new_state->fb->hot_y;
> - }
> + hotspot_x = du->hotspot_x + new_state->hotspot_x;
> + hotspot_y = du->hotspot_y + new_state->hotspot_y;
>
> du->cursor_surface = vps->surf;
> du->cursor_bo = vps->bo;
next prev parent reply other threads:[~2023-06-27 13:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:58 [PATCH v3 0/8] Fix cursor planes with virtualized drivers Zack Rusin
2023-06-27 3:58 ` [PATCH v3 1/8] drm: Disable the cursor plane on atomic contexts " Zack Rusin
2023-06-27 8:18 ` Pekka Paalanen
2023-06-27 8:26 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 2/8] drm/atomic: Add support for mouse hotspots Zack Rusin
2023-06-27 8:26 ` Pekka Paalanen
2023-06-27 8:56 ` Javier Martinez Canillas
2023-06-27 10:30 ` Pekka Paalanen
2023-06-27 10:54 ` Javier Martinez Canillas
2023-06-27 8:49 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 3/8] drm/vmwgfx: Use the hotspot properties from cursor planes Zack Rusin
2023-06-27 9:49 ` Javier Martinez Canillas
2023-06-27 13:08 ` Martin Krastev (VMware) [this message]
2023-06-27 3:58 ` [PATCH v3 4/8] drm/qxl: " Zack Rusin
2023-06-27 9:50 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 5/8] drm/vboxvideo: " Zack Rusin
2023-06-27 10:02 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 6/8] drm/virtio: " Zack Rusin
2023-06-27 10:03 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 7/8] drm: Remove legacy cursor hotspot code Zack Rusin
2023-06-27 10:16 ` Javier Martinez Canillas
2023-06-27 3:58 ` [PATCH v3 8/8] drm: Introduce DRM_CLIENT_CAP_VIRTUALIZED_CURSOR_PLANE Zack Rusin
2023-06-27 8:38 ` Pekka Paalanen
2023-06-27 10:19 ` 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=1e7aa2c9-9de4-cd14-1068-5b05f081f82e@gmail.com \
--to=martinkrastev768@gmail.com \
--cc=banackm@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iforbes@vmware.com \
--cc=javierm@redhat.com \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.com \
--cc=ppaalanen@gmail.com \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).