From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: spasswolf@web.de, alexander.deucher@amd.com
Cc: regressions@lists.linux.dev, leandro.ribeiro@collabora.com,
mwen@igalia.com, alex.hung@amd.com, mario.limonciello@amd.com,
jesse.zhang@amd.com, Amber.Lin@amd.com,
amd-gfx@lists.freedesktop.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: warnings from validate_blend_mode_for_alpha_formats() in next-20260715
Date: Wed, 26 Aug 2026 02:28:15 +0500 [thread overview]
Message-ID: <20260825212815.48959-1-mikhail.v.gavrilov@gmail.com> (raw)
In-Reply-To: <20260716152933.6744-1-spasswolf@web.de>
Hi,
this is not a linux-next-only issue any more: 860e748bddcc came in with the
drm-next pull of the 7.3 merge window, so it now warns on plain mainline. Here
it fires 16 times on every boot - 8 per GPU, on the 4 primary and 4 cursor
planes of each of the two cards in this machine:
[PLANE:44:plane-0] pixel format with alpha exposed but blend mode not setup
WARNING: drivers/gpu/drm/drm_mode_config.c:872 at drm_mode_config_validate+0xa16/0x13b0
I ran into it on 7.2.0-2709dd5ae32f, bisected it to 860e748bddcc and confirmed
by reverting that commit, before I found this thread. Hardware:
0000:03:00.0 Navi 31 (DCN 3.2) and 0000:0f:00.0 Raphael iGPU (DCN 3.1.5).
Nobody has put this on regzbot yet, so:
#regzbot introduced: 860e748bddcc
#regzbot title: drm: WARNING at drm_mode_config_validate() for planes exposing alpha without a blend mode property
#regzbot monitor: https://lore.kernel.org/all/20260813143605.106104-1-mwen@igalia.com/
Status as far as I can see it: Melissa Wen's v3 series (monitored above) fixes
amdgpu for both DCN and DCE, has Reviewed-by from Alex Hung and Tested-by from
Daniel Wheeler, and I tested it here too - the warnings are gone on both GPUs.
It is in neither linux-next nor amd-staging-drm-next so far. 271e90eb5f9f
("drm: use drm_warn() in validate_blend_mode_for_alpha_formats()") turns the
splat into a plain warning and went to drm-next on 2026-08-20 as part of
drm-misc-next-fixes-2026-08-20, but has not reached mainline either. Other
drivers are being fixed in separate threads (imx dcss, rockchip, vkms).
Since this was introduced during the 7.3 merge window, the fixes should land
in 7.3 rather than wait for the next one.
--
Thanks,
Mikhail
next prev parent reply other threads:[~2026-08-25 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 15:29 warnings from validate_blend_mode_for_alpha_formats() in next-20260715 Bert Karwatzki
2026-07-17 14:55 ` Alex Deucher
2026-07-17 22:54 ` Leandro Ribeiro
2026-07-18 9:21 ` Bert Karwatzki
2026-07-18 12:22 ` Bert Karwatzki
2026-08-14 15:17 ` [PATCH 1/8] display: fix blend_mode for non-overlay planes Bert Karwatzki
2026-08-21 18:47 ` Joshua Peisach
2026-08-21 19:42 ` Bert Karwatzki
2026-08-21 20:31 ` Alex Hung
2026-08-24 9:33 ` Bert Karwatzki
2026-08-25 21:28 ` Mikhail Gavrilov [this message]
2026-08-26 9:22 ` warnings from validate_blend_mode_for_alpha_formats() in next-20260715 Greg KH
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=20260825212815.48959-1-mikhail.v.gavrilov@gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=Amber.Lin@amd.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mwen@igalia.com \
--cc=regressions@lists.linux.dev \
--cc=spasswolf@web.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.