From: Thomas Zimmermann <tzimmermann@suse.de>
To: Qinyun Tan <qinyuntan@linux.alibaba.com>,
dri-devel@lists.freedesktop.org
Cc: airlied@redhat.com, jfalempe@redhat.com, kraxel@redhat.com,
dmitry.osipenko@collabora.com, hansg@kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
simona@ffwll.ch, leandro.ribeiro@collabora.com,
daniels@collabora.com, pekka.paalanen@collabora.com,
virtualization@lists.linux.dev,
spice-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] drm/virtio: create blend mode property on cursor plane
Date: Tue, 1 Sep 2026 13:46:00 +0200 [thread overview]
Message-ID: <00e6bf78-aff7-422e-8ec9-024d9f10e4d0@suse.de> (raw)
In-Reply-To: <20260901083234.1828755-4-qinyuntan@linux.alibaba.com>
Am 01.09.26 um 10:32 schrieb Qinyun Tan:
> Since commit 860e748bddcc ("drm: ensure blend mode supported if pixel
> format with alpha exposed"), drm_mode_config_validate() warns when a
> plane exposes an alpha pixel format but not the "pixel blend mode"
> property. The virtio-gpu cursor plane (HOST_ARGB8888) trips this.
>
> The virtio-gpu specification does not define the cursor alpha
> semantics. The host forwards the cursor pixels verbatim to its display
> frontends, and the remote cursor protocols among them (SPICE alpha
> cursors, the VNC "Cursor With Alpha" encoding) both define
> pre-multiplied alpha, matching what userspace has always assumed when
> the property is not attached. Expose a "pixel blend mode" property
> advertising only DRM_MODE_BLEND_PREMULTI to make these semantics
> explicit and silence the warning. The primary plane only exposes
> HOST_XRGB8888, so the call is gated to the cursor. No functional
> change.
>
> Fixes: 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed")
> Signed-off-by: Qinyun Tan <qinyuntan@linux.alibaba.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
> v2: no code change; explain the protocol-level justification for
> PREMULTI in the commit message.
>
> 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 1d1b27ece62a7..640815af40980 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_plane.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_plane.c
> @@ -24,6 +24,7 @@
> */
>
> #include <drm/drm_atomic_helper.h>
> +#include <drm/drm_blend.h>
> #include <drm/drm_damage_helper.h>
> #include <drm/drm_fourcc.h>
> #include <drm/drm_gem_atomic_helper.h>
> @@ -609,6 +610,9 @@ struct drm_plane *virtio_gpu_plane_init(struct virtio_gpu_device *vgdev,
>
> if (type == DRM_PLANE_TYPE_PRIMARY)
> drm_plane_enable_fb_damage_clips(plane);
> + else if (type == DRM_PLANE_TYPE_CURSOR)
> + drm_plane_create_blend_mode_property(plane,
> + BIT(DRM_MODE_BLEND_PREMULTI));
>
> return plane;
> }
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2026-09-01 11:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 8:32 [PATCH v2 0/4] drm: create blend mode property on alpha-capable planes of simple drivers Qinyun Tan
2026-09-01 8:32 ` [PATCH v2 1/4] drm/ast: create blend mode property on cursor plane Qinyun Tan
2026-09-01 8:46 ` sashiko-bot
2026-09-01 11:54 ` Thomas Zimmermann
2026-09-01 12:30 ` Thomas Zimmermann
2026-09-01 12:51 ` Qinyun Tan
2026-09-03 7:05 ` Thomas Zimmermann
2026-09-04 5:31 ` Qinyun Tan
2026-09-03 7:01 ` Thomas Zimmermann
2026-09-01 8:32 ` [PATCH v2 2/4] drm/qxl: create blend mode property on primary and cursor planes Qinyun Tan
2026-09-01 11:45 ` Thomas Zimmermann
2026-09-01 8:32 ` [PATCH v2 3/4] drm/virtio: create blend mode property on cursor plane Qinyun Tan
2026-09-01 11:46 ` Thomas Zimmermann [this message]
2026-09-01 8:32 ` [PATCH v2 4/4] drm/vboxvideo: create blend mode property on planes Qinyun Tan
2026-09-01 8:46 ` sashiko-bot
2026-09-03 7:00 ` 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=00e6bf78-aff7-422e-8ec9-024d9f10e4d0@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=daniels@collabora.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=jfalempe@redhat.com \
--cc=kraxel@redhat.com \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=qinyuntan@linux.alibaba.com \
--cc=simona@ffwll.ch \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux.dev \
/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