From: Andi Shyti <andi.shyti@kernel.org>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ben Dooks <ben-linux@fluff.org>,
Dirk Brandewie <dirk.brandewie@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] i2c: designware-pci: fix autosuspend cleanup during teardown
Date: Fri, 21 Aug 2026 12:42:10 +0200 [thread overview]
Message-ID: <aogiXF11b7z16U2G@zenone.zhora.eu> (raw)
In-Reply-To: <20260809073055.2980971-1-lgs201920130244@gmail.com>
Hi Guangshuo,
On Sun, Aug 09, 2026 at 03:30:55PM +0800, Guangshuo Li wrote:
> i2c_dw_pci_probe() calls pm_runtime_use_autosuspend(), but
> i2c_dw_pci_remove() does not call the matching
> pm_runtime_dont_use_autosuspend() during teardown.
>
> If the autosuspend delay is set to a negative value while autosuspend
> is enabled, the runtime PM core increments usage_count to prevent
> runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
> during teardown, this reference is not dropped.
>
> 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() call to the driver
> remove path.
>
> This issue was found by manual code inspection.
>
> Fixes: 18dbdda89f5c ("i2c-designware: Add runtime power management support")
This Fixes: is wrong because there was no autosuspend here. Maybe
you are referring to:
Fixes: 43452335224b ("i2c-designware: switch to use runtime PM autosuspend")
Cc: <stable@vger.kernel.org> # v3.10+
?
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> drivers/i2c/busses/i2c-designware-pcidrv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-pcidrv.c b/drivers/i2c/busses/i2c-designware-pcidrv.c
> index 468287922363..f1f4955f9a3f 100644
> --- a/drivers/i2c/busses/i2c-designware-pcidrv.c
> +++ b/drivers/i2c/busses/i2c-designware-pcidrv.c
> @@ -300,6 +300,7 @@ static void i2c_dw_pci_remove(struct pci_dev *pdev)
>
> i2c_dw_disable(dev);
>
> + pm_runtime_dont_use_autosuspend(device);
If I haven't missed anything, pm_runtime_dont_use_autosuspend()
can drop the reference and trigger a suspend, which then calls
i2c_dw_runtime_suspend() and eventually i2c_dw_disable() for the
second time.
If this is correct, pm_runtime_dont_use_autosuspend() should be
moved towards the end, followed by i2c_dw_disable(), which would
then need to become the final cleanup step.
Intel folks need to verify the order anyway.
Thanks,
Andi
> pm_runtime_forbid(device);
> pm_runtime_get_noresume(device);
>
> --
> 2.43.0
>
prev parent reply other threads:[~2026-08-21 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 7:30 Guangshuo Li
2026-08-10 4:44 ` Mika Westerberg
2026-08-20 14:49 ` Krzysztof Kozlowski
2026-08-26 8:11 ` Guangshuo Li
2026-08-21 10:42 ` Andi Shyti [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=aogiXF11b7z16U2G@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ben-linux@fluff.org \
--cc=dirk.brandewie@gmail.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@vger.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 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®