diff options
author | Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> | 2023-08-03 08:52:19 +0200 |
---|---|---|
committer | Vinod Koul <vkoul@kernel.org> | 2023-08-11 08:54:56 +0200 |
commit | 3d71f43f8a59a62c6ab832d4e73a69bae22e13b7 (patch) | |
tree | 83330cb44019ac8014296b1d8abe6d74ea684a71 /samples | |
parent | soundwire: Explicitly include correct DT includes (diff) | |
download | linux-3d71f43f8a59a62c6ab832d4e73a69bae22e13b7.tar.xz linux-3d71f43f8a59a62c6ab832d4e73a69bae22e13b7.zip |
soundwire: intel_auxdevice: enable pm_runtime earlier on startup
As soon as the bus starts, physical peripheral devices may report as
ATTACHED and set their status with pm_runtime_set_active() in their
update_status()/io_init().
This is problematic with the existing code, since the parent
pm_runtime status is changed to "active" after starting the bus. This
creates a time window where the pm_runtime framework can report an
issue, e.g.
"rt711 sdw:0:025d:0711:00: runtime PM trying to activate child device
sdw:0:025d:0711:00 but parent (sdw-master-0) is not active"
This patch enables runtime_pm earlier to make sure the auxiliary
device is pm_runtime active after powering-up, but before starting the
bus.
This problem was exposed by recent changes in the timing of the bus
reset, but was present in this driver since we introduced pm_runtime
support.
Closes: https://github.com/thesofproject/linux/issues/4328
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>
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Link: https://lore.kernel.org/r/20230803065220.3823269-2-yung-chuan.liao@linux.intel.com
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions