diff options
| author | Alexander Usyskin <alexander.usyskin@intel.com> | 2016-11-24 13:34:02 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-01-09 08:07:47 +0100 |
| commit | abb78811e242b5692fb4d8a53014b27831bb9173 (patch) | |
| tree | 0935e9e2c40c313ed2a7986b4c59f4cafb32816e /fs | |
| parent | 1f9c91a37542b24374c160c0139b8943183124bb (diff) | |
mei: request async autosuspend at the end of enumeration
commit d5f8e166c25750adc147b0adf64a62a91653438a upstream.
pm_runtime_autosuspend can take synchronous or asynchronous
paths, Because we are calling pm_runtime_mark_last_busy just before
this most of the cases it takes the asynchronous way. However,
when the FW or driver resets during already running runtime suspend,
the call will result in calling to the driver's rpm callback and results
in a deadlock on device_lock.
The simplest fix is to replace pm_runtime_autosuspend with
asynchronous pm_request_autosuspend.
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions