From: Roshan Kumar <roshaen09@gmail.com>
To: linusw@kernel.org, dri-devel@lists.freedesktop.org
Cc: leandro.ribeiro@collabora.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, pimyn@google.com, linux-kernel@vger.kernel.org,
roshaen09@gmail.com
Subject: [PATCH] drm/pl111: Advertise no pixel blending
Date: Tue, 25 Aug 2026 16:24:26 +0530 [thread overview]
Message-ID: <20260825105427.686619-1-roshaen09@gmail.com> (raw)
Commit 860e748bddcc ("drm: ensure blend mode supported if
pixel format with alpha exposed") added validation that warns when a
plane exposes an alpha format without a pixel blend mode property. PL111
exposes several such formats but does not attach the property.
The PL110/PL111 controller scans out a single framebuffer and does not
blend its alpha channel with a background. Advertise
DRM_MODE_BLEND_PIXEL_NONE to match the existing hardware behavior.
With panic_on_warn enabled, this warning prevents the syzkaller
vexpress-a15 manager from booting. The change was tested on current
master with QEMU 10 and the existing production DTB; the guest reached
sshd and returned an SSH banner.
Fixes: 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed")
Link: https://github.com/google/syzkaller/issues/7805
Signed-off-by: Roshan Kumar <roshaen09@gmail.com>
---
drivers/gpu/drm/pl111/pl111_display.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/pl111/pl111_display.c b/drivers/gpu/drm/pl111/pl111_display.c
index 5d10bc5..758b297 100644
--- a/drivers/gpu/drm/pl111/pl111_display.c
+++ b/drivers/gpu/drm/pl111/pl111_display.c
@@ -15,6 +15,7 @@
#include <linux/media-bus-format.h>
#include <linux/of_graph.h>
+#include <drm/drm_blend.h>
#include <drm/drm_fb_dma_helper.h>
#include <drm/drm_fourcc.h>
#include <drm/drm_framebuffer.h>
@@ -596,5 +597,10 @@ int pl111_display_init(struct drm_device *drm)
if (ret)
return ret;
+ ret = drm_plane_create_blend_mode_property(&priv->pipe.plane,
+ BIT(DRM_MODE_BLEND_PIXEL_NONE));
+ if (ret)
+ return ret;
+
return 0;
}
--
2.43.0
next reply other threads:[~2026-08-25 10:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:54 Roshan Kumar [this message]
2026-08-25 11:07 ` [PATCH] drm/pl111: Advertise no pixel blending sashiko-bot
2026-09-08 21:31 ` Leandro Ribeiro
2026-09-09 4:17 ` Roshan Kumar
2026-09-09 8:16 ` Thomas Zimmermann
2026-09-11 13:24 ` Linus Walleij
2026-09-11 13:26 ` Linus Walleij
[not found] ` <d3a928e0-0faa-4cd4-9d2e-cb9be4cf84c0@suse.de>
2026-09-10 5:44 ` Roshan Kumar
2026-09-10 5:45 ` [PATCH v2] drm/pl111: drop alpha formats the hardware cannot scan out Roshan Kumar
2026-09-10 5:51 ` sashiko-bot
2026-09-10 6:15 ` Thomas Zimmermann
2026-09-10 19:25 ` [PATCH] drm/pl111: Advertise no pixel blending Roshan Kumar
2026-09-11 6:33 ` Thomas Zimmermann
2026-09-11 12:58 ` Thomas Zimmermann
2026-09-11 18:07 ` Roshan Kumar
2026-09-11 18:22 ` Linus Walleij
2026-09-11 19:07 ` Roshan Kumar
2026-09-11 20:05 ` Linus Walleij
2026-09-12 19:49 ` Ze Huang
2026-09-10 19:25 ` [PATCH v3] drm/pl111: drop alpha formats the hardware cannot scan out Roshan Kumar
2026-09-10 19:34 ` sashiko-bot
2026-09-11 6:41 ` Thomas Zimmermann
2026-09-11 18:00 ` Linus Walleij
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=20260825105427.686619-1-roshaen09@gmail.com \
--to=roshaen09@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=leandro.ribeiro@collabora.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pimyn@google.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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.