mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
	oushixiong1025@163.com, David Airlie <airlied@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	Gurchetan Singh <gurchetansingh@chromium.org>,
	Chia-I Wu <olvaffe@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org, Shixiong Ou <oushixiong@kylinos.cn>,
	Ye Liu <liuye@kylinos.cn>
Subject: Re: [PATCH] drm/virtio: Add pixel blend mode property to cursor plane
Date: Thu, 1 Oct 2026 20:00:56 +0200	[thread overview]
Message-ID: <ce84d3d2-e78b-4939-aecf-9ef7267bd42a@samsung.com> (raw)
In-Reply-To: <c627ced6-1bdb-4508-b010-46df53eab2b3@collabora.com>

On 20.09.2026 20:21, Dmitry Osipenko wrote:
> On 8/28/26 12:01, oushixiong1025@163.com wrote:
>> From: Shixiong Ou <oushixiong@kylinos.cn>
>>
>> The cursor plane exposes a format with an alpha channel
>> (DRM_FORMAT_ARGB8888) without a pixel blend mode property. Since
>> commit 860e748bddcc ("drm: ensure blend mode supported if pixel
>> format with alpha exposed") this triggers a warning during
>> drm_mode_config_validate():
>>
>> [    0.649020] ------------[ cut here ]------------
>> [    0.649040] [PLANE:36:plane-1] pixel format with alpha exposed but blend mode not setup
>> [    0.649081] WARNING: drivers/gpu/drm/drm_mode_config.c:872 at drm_mode_config_validate
>> ......
>> [    0.649761] Call trace:
>> [    0.649764]  drm_mode_config_validate+0x398/0x558 [drm] (P)
>> [    0.649912]  drm_dev_register+0x1cc/0x2a0 [drm]
>> [    0.650058]  virtio_gpu_probe+0xd4/0x1c0 [virtio_gpu]
>> [    0.650088]  virtio_dev_probe+0x1c8/0x310
>> ......
>> [    0.650261] ---[ end trace 0000000000000000 ]---
>>
>>
>> Create the property with the only supported blend mode,
>> DRM_MODE_BLEND_PREMULTI, which is also the property's default and
>> matches what userspace had to assume before the property existed.
>>
>> Reported-by: Ye Liu <liuye@kylinos.cn>
>> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
>> ---
>>  drivers/gpu/drm/virtio/virtgpu_plane.c | 14 ++++++++++++++
>>  1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c
>> index 1d1b27ece62a..11771c943ea6 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>
>> @@ -588,6 +589,7 @@ struct drm_plane *virtio_gpu_plane_init(struct virtio_gpu_device *vgdev,
>>  	struct drm_plane *plane;
>>  	const uint32_t *formats;
>>  	int nformats;
>> +	int ret;
>>  
>>  	if (type == DRM_PLANE_TYPE_CURSOR) {
>>  		formats = virtio_gpu_cursor_formats;
>> @@ -610,5 +612,17 @@ 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);
>>  
>> +	if (type == DRM_PLANE_TYPE_CURSOR) {
>> +		/*
>> +		 * The cursor plane exposes a format with an alpha channel,
>> +		 * which requires a blend mode property. The host blends
>> +		 * premultiplied alpha, matching the property's default.
>> +		 */
>> +		ret = drm_plane_create_blend_mode_property(plane,
>> +							   BIT(DRM_MODE_BLEND_PREMULTI));
>> +		if (ret)
>> +			return ERR_PTR(ret);
>> +	}
>> +
>>  	return plane;
>>  }
> Applied to misc-fixes, thanks!


This duplicates commit f2e64f450c16 ("drm/virtio: create blend mode property on cursor
plane") merged a bit earlier, what in turn results in double call to
drm_plane_create_blend_mode_property() what confuses userspace (modetest tool crashes).

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


  parent reply	other threads:[~2026-10-01 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  9:01 oushixiong1025
2026-09-20 18:21 ` Dmitry Osipenko
     [not found]   ` <CGME20261001180058eucas1p1506f92fdf0e1417404bb8025f181ae30@eucas1p1.samsung.com>
2026-10-01 18:00     ` Marek Szyprowski [this message]
2026-10-02 10:26       ` Dmitry Osipenko

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=ce84d3d2-e78b-4939-aecf-9ef7267bd42a@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=airlied@redhat.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gurchetansingh@chromium.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuye@kylinos.cn \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=oushixiong1025@163.com \
    --cc=oushixiong@kylinos.cn \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --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

all inboxes | Powered by JetHome®