From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org, Frank.Li@kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH 2/4] drm/imx: ipuv3-plane: add the pixel blend mode property
Date: Mon, 10 Aug 2026 15:02:21 +0000 [thread overview]
Message-ID: <20260810150222.54F301F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260810-imx53-fix-hdmi-v1-2-fff9b1b17f25@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Plane atomic update callback calls functions that acquire a sleeping lock (mutex).
--
--- Patch [2]: [PATCH 2/4] drm/imx: ipuv3-plane: add the pixel blend mode property ---
commit 166d0e9ef492a9f6b268953776bb8c6c929a2acc
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
drm/imx: ipuv3-plane: add the pixel blend mode property
This commit adds a pixel blend mode property to IPUv3 planes. It configures
the planes to support coverage or none based on whether they are part of a
DP flow, and uses this blend mode to decide between global and per-pixel
alpha during plane updates.
> diff --git a/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c b/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
> index a0fd39eebbbc2..bde5892264f4a 100644
> --- a/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
> +++ b/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
[ ... ]
> @@ -593,8 +621,8 @@ static void ipu_plane_atomic_update(struct drm_plane *plane,
> case IPU_DP_FLOW_SYNC_BG:
> if (new_state->normalized_zpos == 1) {
> ipu_dp_set_global_alpha(ipu_plane->dp,
> - !fb->format->has_alpha, 0xff,
> - true);
> + !ipu_plane_use_pixel_alpha(new_state),
> + 0xff, true);
[Severity: High]
This isn't a bug introduced by this patch, but is it safe to call
ipu_dp_set_global_alpha() from the atomic update callback?
The DRM core invokes ipu_plane_atomic_update() in an atomic context
where sleeping is forbidden. However, ipu_dp_set_global_alpha()
unconditionally acquires a sleeping lock:
drivers/gpu/ipu-v3/ipu-dp.c:ipu_dp_set_global_alpha() {
...
mutex_lock(&priv->mutex);
...
}
Could this trigger kernel warnings or deadlocks if the thread is scheduled
out while executing in a non-blocking DRM atomic commit phase?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260810-imx53-fix-hdmi-v1-0-fff9b1b17f25@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-08-10 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:51 [PATCH 0/4] drm/imx: fix TVE / HDMI coexistence Dmitry Baryshkov
2026-08-10 14:51 ` [PATCH 1/4] drm/imx: ipuv3-plane: do not advertise separate alpha formats on DC planes Dmitry Baryshkov
2026-08-10 14:51 ` [PATCH 2/4] drm/imx: ipuv3-plane: add the pixel blend mode property Dmitry Baryshkov
2026-08-10 15:02 ` sashiko-bot [this message]
2026-08-10 14:51 ` [PATCH 3/4] drm/imx: imx-tve: probe DDC before claiming the connector is connected Dmitry Baryshkov
2026-08-10 15:01 ` sashiko-bot
2026-08-10 14:51 ` [PATCH 4/4] gpu: ipu-v3: di: report an unattainable pixel clock Dmitry Baryshkov
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=20260810150222.54F301F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=sashiko-reviews@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 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.