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
Subject: Re: [PATCH] drm/pl111: Advertise no pixel blending
Date: Thu, 10 Sep 2026 19:25:11 -0000 [thread overview]
Message-ID: <178906831180.136984.3208749717777263252@gmail.com> (raw)
In-Reply-To: <20260825105427.686619-1-roshaen09@gmail.com>
No physical PL111 hardware here; I tested under QEMU vexpress with
panic_on_warn, which is also how the syzkaller instance hits this.
On current master (7.3-rc2) the unpatched driver registers and
immediately warns: "[PLANE:35:plane-0] pixel format with alpha exposed
but blend mode not setup", which kills the boot with panic_on_warn.
With v3 below, the same boot registers pl111 with no warnings at all.
One note: 860e748bddcc is not in v7.2, so the splat only shows up on
master/7.3 and later.
v3 also removes the alpha formats from the board-specific tables in
pl111_versatile.c that the sashiko review caught v2 missing.
next prev parent reply other threads:[~2026-09-11 7:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:54 [PATCH] drm/pl111: Advertise no pixel blending Roshan Kumar
2026-08-25 11:07 ` 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 ` Roshan Kumar [this message]
2026-09-11 6:33 ` [PATCH] drm/pl111: Advertise no pixel blending 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=178906831180.136984.3208749717777263252@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.