From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Qiang Yu <yuq825@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Vasily Khoruzhick <anarsoul@gmail.com>,
dri-devel@lists.freedesktop.org, lima@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] drm/lima: fix autosuspend cleanup during teardown
Date: Thu, 20 Aug 2026 16:49:54 +0200 [thread overview]
Message-ID: <5174855b-fe2f-4a6f-8390-959e9d624cf1@kernel.org> (raw)
In-Reply-To: <20260808125953.2842241-1-lgs201920130244@gmail.com>
On 08/08/2026 14:59, Guangshuo Li wrote:
> lima_pdev_probe() calls pm_runtime_use_autosuspend(), but its failure
> path does not call the matching pm_runtime_dont_use_autosuspend()
> before disabling runtime PM. The remove path has the same issue.
>
> In particular, lima_pdev_remove() explicitly sets the autosuspend
> delay to -1 while autosuspend is still enabled. A negative autosuspend
> delay can increase usage_count to prevent runtime suspend. Without
> calling pm_runtime_dont_use_autosuspend(), this reference is not
> dropped before runtime PM is disabled, leaving usage_count unbalanced.
>
> The documentation for pm_runtime_use_autosuspend() also notes that it
> is important to undo it with pm_runtime_dont_use_autosuspend() at
> driver exit time, unless runtime PM was initially enabled with
> devm_pm_runtime_enable().
>
> Add the missing pm_runtime_dont_use_autosuspend() calls to the probe
> failure and remove paths.
>
> This issue was found by manual code inspection.
>
> Fixes: 50de2e9ebbc0 ("drm/lima: enable runtime pm")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
You sent vast amount of patches, all separate, making it very difficult
to track and respond in efficient way. Do not do that.
Group your work per subsystem.
You were asked to clarify and respond to incorrect fixes statement. I do
not see how you clarified and responded at all.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-20 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 12:59 [PATCH] drm/lima: fix autosuspend cleanup during teardown Guangshuo Li
2026-08-08 13:17 ` sashiko-bot
2026-08-20 14:49 ` Krzysztof Kozlowski [this message]
2026-08-26 8:13 ` Guangshuo Li
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=5174855b-fe2f-4a6f-8390-959e9d624cf1@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=anarsoul@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgs201920130244@gmail.com \
--cc=lima@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=yuq825@gmail.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 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.