From: sashiko-bot@kernel.org
To: "Michal Wilczynski" <m.wilczynski@samsung.com>
Cc: linux-phy@lists.infradead.org, linux-clk@vger.kernel.org,
conor+dt@kernel.org, dri-devel@lists.freedesktop.org,
neil.armstrong@linaro.org, devicetree@vger.kernel.org,
vkoul@kernel.org, robh@kernel.org, olteanv@gmail.com,
mfd@lists.linux.dev, lee@kernel.org
Subject: Re: [PATCH v2 06/15] drm/bridge: inno-hdmi: Add .disable platform operation
Date: Fri, 28 Aug 2026 13:57:46 +0000 [thread overview]
Message-ID: <20260828135746.EC4391F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828-jh7110-clean-send-v2-6-331680c8b9d1@samsung.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Atomic Context Violation: Invoking sleeping functions from atomic context
--
commit 2003c6678c3684f19742ce18515a5d05db18fc6c
Author: Michal Wilczynski <m.wilczynski@samsung.com>
drm/bridge: inno-hdmi: Add .disable platform operation
This commit adds a new .disable platform operation to the inno_hdmi_plat_ops
struct. It invokes this hook at the beginning of
inno_hdmi_bridge_atomic_disable() to allow platform-specific drivers to
implement their own power down sequences.
> diff --git a/drivers/gpu/drm/bridge/inno-hdmi.c b/drivers/gpu/drm/bridge/inno-hdmi.c
> index ebc5093f13ac4..952cc55c10f7d 100644
> --- a/drivers/gpu/drm/bridge/inno-hdmi.c
> +++ b/drivers/gpu/drm/bridge/inno-hdmi.c
> @@ -884,6 +884,10 @@ static void inno_hdmi_bridge_atomic_disable(struct drm_bridge *bridge,
> struct drm_atomic_commit *state)
> {
> struct inno_hdmi *hdmi = bridge_to_inno_hdmi(bridge);
> + const struct inno_hdmi_plat_ops *plat_ops = hdmi->plat_data->ops;
> +
> + if (plat_ops && plat_ops->disable)
> + plat_ops->disable(hdmi->dev);
[Severity: High]
The commit message mentions this hook allows platform drivers to implement
power down sequences by calling clk_disable_unprepare(). Since
inno_hdmi_bridge_atomic_disable() is called from the atomic commit pipeline
(drm_atomic_helper_commit_tail()), where sleeping is strictly forbidden,
can this lead to an atomic context violation?
Because clk_disable_unprepare() acquires a mutex internally, it is a
sleeping function. Calling it from this path could cause system instability,
kernel warnings, or deadlocks during a display modeset, DPMS state change,
or system suspend.
>
> inno_hdmi_standby(hdmi);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828-jh7110-clean-send-v2-0-331680c8b9d1@samsung.com?part=6
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Michal Wilczynski" <m.wilczynski@samsung.com>
Cc: linux-phy@lists.infradead.org, linux-clk@vger.kernel.org,
conor+dt@kernel.org, dri-devel@lists.freedesktop.org,
neil.armstrong@linaro.org, devicetree@vger.kernel.org,
vkoul@kernel.org, robh@kernel.org, olteanv@gmail.com,
mfd@lists.linux.dev, lee@kernel.org
Subject: Re: [PATCH v2 06/15] drm/bridge: inno-hdmi: Add .disable platform operation
Date: Fri, 28 Aug 2026 13:57:46 +0000 [thread overview]
Message-ID: <20260828135746.EC4391F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828-jh7110-clean-send-v2-6-331680c8b9d1@samsung.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Atomic Context Violation: Invoking sleeping functions from atomic context
--
commit 2003c6678c3684f19742ce18515a5d05db18fc6c
Author: Michal Wilczynski <m.wilczynski@samsung.com>
drm/bridge: inno-hdmi: Add .disable platform operation
This commit adds a new .disable platform operation to the inno_hdmi_plat_ops
struct. It invokes this hook at the beginning of
inno_hdmi_bridge_atomic_disable() to allow platform-specific drivers to
implement their own power down sequences.
> diff --git a/drivers/gpu/drm/bridge/inno-hdmi.c b/drivers/gpu/drm/bridge/inno-hdmi.c
> index ebc5093f13ac4..952cc55c10f7d 100644
> --- a/drivers/gpu/drm/bridge/inno-hdmi.c
> +++ b/drivers/gpu/drm/bridge/inno-hdmi.c
> @@ -884,6 +884,10 @@ static void inno_hdmi_bridge_atomic_disable(struct drm_bridge *bridge,
> struct drm_atomic_commit *state)
> {
> struct inno_hdmi *hdmi = bridge_to_inno_hdmi(bridge);
> + const struct inno_hdmi_plat_ops *plat_ops = hdmi->plat_data->ops;
> +
> + if (plat_ops && plat_ops->disable)
> + plat_ops->disable(hdmi->dev);
[Severity: High]
The commit message mentions this hook allows platform drivers to implement
power down sequences by calling clk_disable_unprepare(). Since
inno_hdmi_bridge_atomic_disable() is called from the atomic commit pipeline
(drm_atomic_helper_commit_tail()), where sleeping is strictly forbidden,
can this lead to an atomic context violation?
Because clk_disable_unprepare() acquires a mutex internally, it is a
sleeping function. Calling it from this path could cause system instability,
kernel warnings, or deadlocks during a display modeset, DPMS state change,
or system suspend.
>
> inno_hdmi_standby(hdmi);
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828-jh7110-clean-send-v2-0-331680c8b9d1@samsung.com?part=6
next prev parent reply other threads:[~2026-08-28 13:57 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260828134813eucas1p1bd003a66706ed251017185fc14f13cc9@eucas1p1.samsung.com>
2026-08-28 13:47 ` [PATCH v2 00/15] drm: starfive: jh7110: Enable display subsystem Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` [PATCH v2 01/15] dt-bindings: phy: Add starfive,jh7110-inno-hdmi-phy Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:54 ` sashiko-bot
2026-08-28 13:54 ` sashiko-bot
2026-08-28 16:43 ` Conor Dooley
2026-08-28 16:43 ` Conor Dooley
2026-08-28 16:43 ` Conor Dooley
2026-08-28 16:43 ` Conor Dooley
2026-08-28 13:47 ` [PATCH v2 02/15] dt-bindings: display: bridge: Add starfive,jh7110-inno-hdmi-controller Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:54 ` sashiko-bot
2026-08-28 13:54 ` sashiko-bot
2026-08-28 14:04 ` Icenowy Zheng
2026-08-28 14:04 ` Icenowy Zheng
2026-08-28 14:04 ` Icenowy Zheng
2026-08-28 14:04 ` Icenowy Zheng
2026-08-28 16:47 ` Conor Dooley
2026-08-28 16:47 ` Conor Dooley
2026-08-28 16:47 ` Conor Dooley
2026-08-28 16:47 ` Conor Dooley
2026-08-28 13:47 ` [PATCH v2 03/15] dt-bindings: mfd: Add starfive,jh7110-hdmi-subsystem Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:54 ` sashiko-bot
2026-08-28 13:54 ` sashiko-bot
2026-08-28 16:50 ` Conor Dooley
2026-08-28 16:50 ` Conor Dooley
2026-08-28 16:50 ` Conor Dooley
2026-08-28 16:50 ` Conor Dooley
2026-08-28 13:47 ` [PATCH v2 04/15] drm/bridge: inno-hdmi: Split probe out of bind Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:01 ` sashiko-bot
2026-08-28 14:01 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 05/15] drm/bridge: inno-hdmi: Allow the register map to come from a parent Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:54 ` sashiko-bot
2026-08-28 13:54 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 06/15] drm/bridge: inno-hdmi: Add .disable platform operation Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:57 ` sashiko-bot [this message]
2026-08-28 13:57 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 07/15] drm/bridge: inno-hdmi: Add .mode_valid " Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:52 ` sashiko-bot
2026-08-28 13:52 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 08/15] soc: starfive: Add jh7110-hdmi-subsystem driver Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:59 ` sashiko-bot
2026-08-28 13:59 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 09/15] clk: starfive: jh7110-vout: Allow pixel clock rate propagation Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:01 ` sashiko-bot
2026-08-28 14:01 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 10/15] drm/bridge: starfive: Add JH7110 HDMI controller driver Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:59 ` sashiko-bot
2026-08-28 13:59 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 11/15] phy: Add common Innosilicon HDMI PHY helpers Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:00 ` sashiko-bot
2026-08-28 14:00 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 12/15] phy: rockchip: inno-hdmi: Use the common Innosilicon " Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:12 ` sashiko-bot
2026-08-28 14:12 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 13/15] phy: starfive: Add jh7110-inno-hdmi-phy driver Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:04 ` sashiko-bot
2026-08-28 14:04 ` sashiko-bot
2026-08-28 13:47 ` [PATCH v2 14/15] riscv: dts: starfive: jh7110: Update DT for display subsystem Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:06 ` sashiko-bot
2026-08-28 14:06 ` sashiko-bot
2026-08-28 14:06 ` Icenowy Zheng
2026-08-28 14:06 ` Icenowy Zheng
2026-08-28 14:06 ` Icenowy Zheng
2026-08-28 14:06 ` Icenowy Zheng
2026-08-28 13:47 ` [PATCH v2 15/15] MAINTAINERS: Add StarFive JH7110 display subsystem entry Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 13:47 ` Michal Wilczynski
2026-08-28 14:01 ` Icenowy Zheng
2026-08-28 14:01 ` Icenowy Zheng
2026-08-28 14:01 ` Icenowy Zheng
2026-08-28 14:01 ` Icenowy Zheng
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=20260828135746.EC4391F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=m.wilczynski@samsung.com \
--cc=mfd@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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.