From: <Manikandan.M@microchip.com>
To: <vulab@iscas.ac.cn>, <Laurent.pinchart@ideasonboard.com>
Cc: <airlied@gmail.com>, <andrzej.hajda@intel.com>,
<dharma.b@microchip.com>, <dri-devel@lists.freedesktop.org>,
<hari.prasathge@microchip.com>, <jernej.skrabec@gmail.com>,
<jonas@kwiboo.se>, <linux-kernel@vger.kernel.org>,
<lumag@kernel.org>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <neil.armstrong@linaro.org>,
<rfoss@kernel.org>, <simona@ffwll.ch>, <tzimmermann@suse.de>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] drm/bridge: microchip-lvds: Fix runtime PM leak in mchp_lvds_enable()
Date: Thu, 17 Sep 2026 11:06:06 +0000 [thread overview]
Message-ID: <97b1638e-2d9e-4301-bebb-c033e36da0e5@microchip.com> (raw)
In-Reply-To: <20260916101922.2018259-1-vulab@iscas.ac.cn>
Hi Wentao Liang,
Thanks for the patch, and Sashiko's automated review is correct here —
this needs rework.
pm_runtime_get_sync() bumps the usage count even on failure, so today
that leaked reference is consumed by the put in _disable().Adding
pm_runtime_put_noidle() on the error path makes the later unconditional
pm_runtime_put() underflow the counter.
Also, as of v7.2 the function is mchp_lvds_atomic_enable(), so please
rebase it on to the latest and update the subject/commit message.
On 9/16/26 3:49 PM, Wentao Liang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> mchp_lvds_enable() resumes the device with pm_runtime_get_sync() and
> returns early when the resume fails. pm_runtime_get_sync() increments
> the runtime PM usage count even when it fails, so returning without
> dropping the reference leaks it and prevents the device from ever
> suspending again once the error has been hit.
>
> Drop the runtime PM reference with pm_runtime_put_noidle() on the
> resume failure path before returning.
>
> Fixes: 179b0769fc5f ("drm/bridge: add lvds controller support for sam9x7")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/gpu/drm/bridge/microchip-lvds.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/bridge/microchip-lvds.c b/drivers/gpu/drm/bridge/microchip-lvds.c
> index 9f4ff82bc6b4..b77ec6ae0a97 100644
> --- a/drivers/gpu/drm/bridge/microchip-lvds.c
> +++ b/drivers/gpu/drm/bridge/microchip-lvds.c
> @@ -127,6 +127,7 @@ static void mchp_lvds_enable(struct drm_bridge *bridge)
> ret = pm_runtime_get_sync(lvds->dev);
> if (ret < 0) {
> dev_err(lvds->dev, "failed to get pm runtime: %d\n", ret);
> + pm_runtime_put_noidle(lvds->dev);
> return;
> }
>
> --
> 2.34.1
>
--
Thanks and Regards,
Manikandan M.
prev parent reply other threads:[~2026-09-17 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 10:19 Wentao Liang
2026-09-17 11:06 ` Manikandan.M [this message]
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=97b1638e-2d9e-4301-bebb-c033e36da0e5@microchip.com \
--to=manikandan.m@microchip.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dharma.b@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hari.prasathge@microchip.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®