[BUG] Device unbound in a resumed state

From	Krzysztof Kozlowski <k.kozlowski@samsung.com>
Newsgroups	linux.kernel
Subject	[BUG] Device unbound in a resumed state
Date	2016-03-11 08:10 +0100
Message-ID	<rbpmV-2wR-1@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi,


Could be related (the same?) with [0].

I have a driver (hwrng/exynos-rng) which in probe does:
pm_runtime_set_autosuspend_delay(&pdev->dev, EXYNOS_AUTOSUSPEND_DELAY);
pm_runtime_use_autosuspend(&pdev->dev);
pm_runtime_enable(&pdev->dev);

and in remove:
pm_runtime_disable(&pdev->dev)

Just before unbinding in __device_release_driver() the device is resumed
but unfortunately not suspended later. I mean the
__device_release_driver()->pm_runtime_put_sync() does not trigger
runtime suspend.

This leads to leaving the device in active state (e.g. clocks enabled).

It does not happen after removal of autosuspend. Also runtime suspend
happens after very fast unbind-bind.


Best regards,
Krzysztof

[0] PM regression with commit 5de85b9d57ab PM runtime re-init in v4.5-rc1
http://comments.gmane.org/gmane.linux.power-management.general/70690

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[BUG] Device unbound in a resumed state Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-03-11 08:10 +0100
  Re: [BUG] Device unbound in a resumed state Alan Stern <stern@rowland.harvard.edu> - 2016-03-11 19:50 +0100
    Re: [BUG] Device unbound in a resumed state Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-03-12 06:30 +0100

csiph-web