mirror of
https://github.com/torvalds/linux.git
synced 2024-12-24 20:01:55 +00:00
e557bca49b
In typical use cases, the peripheral becomes pm_runtime active as a result of the ALSA/ASoC framework starting up a DAI. The parent/child hierarchy guarantees that the manager device will be fully resumed beforehand. There is however a corner case where the manager device may become pm_runtime active, but without ALSA/ASoC requesting any functionality from the peripherals. In this case, the hardware peripheral device will report as ATTACHED and its initialization routine will be executed. If this initialization routine initiates any sort of deferred processing, there is a possibility that the manager could suspend without the peripheral suspend sequence being invoked: from the pm_runtime framework perspective, the peripheral is *already* suspended. To avoid such disconnects between hardware state and pm_runtime state, this patch adds an asynchronous pm_request_resume() upon successful attach/initialization which will result in the proper resume/suspend sequence to be followed on the peripheral side. BugLink: https://github.com/thesofproject/linux/issues/3459 Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com> Reviewed-by: Rander Wang <rander.wang@intel.com> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com> Link: https://lore.kernel.org/r/20220420023241.14335-4-yung-chuan.liao@linux.intel.com Signed-off-by: Vinod Koul <vkoul@kernel.org> |
||
---|---|---|
.. | ||
bus_type.c | ||
bus.c | ||
bus.h | ||
cadence_master.c | ||
cadence_master.h | ||
debugfs.c | ||
dmi-quirks.c | ||
generic_bandwidth_allocation.c | ||
intel_init.c | ||
intel.c | ||
intel.h | ||
Kconfig | ||
Makefile | ||
master.c | ||
mipi_disco.c | ||
qcom.c | ||
slave.c | ||
stream.c | ||
sysfs_local.h | ||
sysfs_slave_dpn.c | ||
sysfs_slave.c |