On Thu, 16 Jun 2022 17:04:16 -0500, Pierre-Louis Bossart wrote: > After a set of SOF-specific changes, this patchset correct problematic > uses of pm_runtime_get_sync() in ASoC, or simplifies the flow with no > functional changes. Two patches for Intel platforms also add a test on > resume success. > > Additional changes were initially suggested to completely remove the > use of pm_runtime_get_sync(). These changes were dropped since they > are way too invasive, specifically in cases where the return values > were not tested, which would lead to duplicate pm_runtime_put(). The > remaining uses of pm_runtime_get_sync() cannot really be blindly > modified without context and knowledge of each driver. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/11] ASoC: Intel: catpt: use pm_runtime_resume_and_get() commit: 82102a24c930986aedc572f89b437cd9e4d44d7e [02/11] ASoC: Intel: skylake: skl-pcm: use pm_runtime_resume_and_get() commit: 7213170a9515109322f75c08b5268d8e9cdad8e4 [04/11] ASoC: wcd-mbhc-v2: use pm_runtime_resume_and_get() commit: ddea4bbf287b6028eaa15a185d0693856956ecf2 [05/11] ASoC: wsa881x: use pm_runtime_resume_and_get() commit: 9a1a28610a1c49bf93777d017aa3fe121eef944e [06/11] ASoC: rockchip: i2s_tdm: use pm_runtime_resume_and_get() commit: 8c8a13e83c29472044d733dfb1fced2ccd025d35 [07/11] ASoC: fsl: fsl_sai: use pm_runtime_resume_and_get() commit: 37cb8a58013fc6ca2febaed355f6559012699542 [08/11] ASoC: img: img-i2s-out: use pm_runtime_resume_and_get() commit: 57d714535051b1baca9ffd92e79fbda1fae3177a [09/11] ASoC: rockchip: pdm: use pm_runtime_resume_and_get() commit: 76a6f4537650e6d2211f34661de35630487c7c64 [10/11] ASoC: tas2552: use pm_runtime_resume_and_get() commit: 05b71fb2a5014d2430ff6c5678db021c67afa9ec [11/11] ASoC: ti: davinci-mcasp: use pm_runtime_resume_and_get() commit: cecc81d6a5deb094bdbc6a1d7f2c014ba9b71cf8 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
