Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 12/16] drm/rockchip: dw_dp: Add runtime PM support
Date: Fri, 24 Jul 2026 18:27:36 +0000	[thread overview]
Message-ID: <20260724182736.7934B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724-synopsys-dw-dp-improvements-v6-12-041d99a19c4e@collabora.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The DW DP core driver uses `guard(pm_runtime_noresume)` in its interrupt handler, allowing hardware register accesses while the device is suspended and its clocks are disabled.
--

--- Patch [12]: [PATCH v6 12/16] drm/rockchip: dw_dp: Add runtime PM support ---
commit 76fb970e196b210c9742e601b51113d5f65dd02f
Author: Sebastian Reichel <sebastian.reichel@collabora.com>

drm/rockchip: dw_dp: Add runtime PM support

This commit adds support for runtime PM to the Rockchip RK3576/3588 Synopsys
DesignWare DisplayPort driver.

> diff --git a/drivers/gpu/drm/rockchip/dw_dp-rockchip.c b/drivers/gpu/drm/rockchip/dw_dp-rockchip.c
> index ee0bd696064eb..b8138e796c4d5 100644
> --- a/drivers/gpu/drm/rockchip/dw_dp-rockchip.c
> +++ b/drivers/gpu/drm/rockchip/dw_dp-rockchip.c

[ ... ]

> @@ -247,6 +260,12 @@ static int dw_dp_rockchip_probe(struct platform_device *pdev)
>  	if (IS_ERR(dp->base))
>  		return PTR_ERR(dp->base);
>  
> +	pm_runtime_use_autosuspend(dev);
> +	pm_runtime_set_autosuspend_delay(dev, 500);
> +	ret = devm_pm_runtime_enable(dev);

[Severity: High]
Does enabling runtime PM here expose a bus fault in the core dw_dp_irq
handler on suspended devices?

The core DW DP driver uses guard(pm_runtime_noresume) which only increments
the PM usage counter without checking the actual power state:

drivers/gpu/drm/bridge/synopsys/dw-dp.c:dw_dp_irq() {
	/* interrupt can only trigger for running device */
	guard(pm_runtime_noresume)(dp->dev);

	regmap_read(dp->regmap, DW_DP_GENERAL_INTERRUPT, &value);
	...
}

If a spurious or delayed interrupt fires while the DP controller is
suspended and its clocks are disabled, this allows the handler to execute
and read from DW_DP_GENERAL_INTERRUPT.

Accessing memory-mapped registers over a disabled APB bus can cause a bus
fault (such as an SError on ARM) resulting in a kernel panic.

Should the core driver be updated to use pm_runtime_get_if_active()
to safely verify the device is active before accessing hardware registers?

> +	if (ret)
> +		return ret;
> +
>  	return component_add(&pdev->dev, &dw_dp_rockchip_component_ops);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260724-synopsys-dw-dp-improvements-v6-0-041d99a19c4e@collabora.com?part=12

  reply	other threads:[~2026-07-24 18:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 18:03 [PATCH v6 00/16] Synopsys DisplayPort Controller improvements for Rockchip platforms Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 01/16] drm/bridge: synopsys: dw-dp: Fix incorrect resource lifetimes in bind callback Sebastian Reichel
2026-07-24 18:18   ` sashiko-bot
2026-07-24 18:03 ` [PATCH v6 02/16] drm/bridge: synopsys: dw-dp: Cancel pending HPD work on unbind Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 03/16] drm/bridge: synopsys: dw-dp: Add missing mutex cleanups on module removal Sebastian Reichel
2026-07-24 18:15   ` sashiko-bot
2026-07-24 18:03 ` [PATCH v6 04/16] drm/bridge: synopsys: dw-dp: Add missing reinit_completion Sebastian Reichel
2026-07-24 18:21   ` sashiko-bot
2026-07-24 18:03 ` [PATCH v6 05/16] drm/bridge: synopsys: dw-dp: Free output_fmts when none are valid Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 06/16] drm/bridge: synopsys: dw-dp: Support MEDIA_BUS_FMT_FIXED Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 07/16] drm/bridge: synopsys: dw-dp: Add follow-up bridge support Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 08/16] drm/bridge: Add out-of-band HPD notify handler Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 09/16] drm/bridge: synopsys: dw-dp: Support software triggered OOB HPD Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 10/16] drm/rockchip: dw_dp: Implement out-of-band HPD handling Sebastian Reichel
2026-07-24 18:27   ` sashiko-bot
2026-07-24 18:03 ` [PATCH v6 11/16] drm/bridge: synopsys: dw-dp: Add Runtime PM support Sebastian Reichel
2026-07-24 18:24   ` sashiko-bot
2026-07-24 18:03 ` [PATCH v6 12/16] drm/rockchip: dw_dp: Add runtime " Sebastian Reichel
2026-07-24 18:27   ` sashiko-bot [this message]
2026-07-24 18:03 ` [PATCH v6 13/16] drm/bridge: synopsys: dw-dp: Protect sdp_reg_bank from concurrent access Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 14/16] drm/bridge: synopsys: dw-dp: Use regmap_set_bits in dw_dp_send_sdp Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 15/16] dt-bindings: display: rockchip: dw-dp: Fix sound DAI cells Sebastian Reichel
2026-07-24 18:03 ` [PATCH v6 16/16] drm/bridge: synopsys: dw-dp: Add audio support Sebastian Reichel
2026-07-24 18:34   ` sashiko-bot

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=20260724182736.7934B1F000E9@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=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sebastian.reichel@collabora.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox