Message ID | 20230130120647.638049-1-claudiu.beznea@microchip.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: mchp-spdifrx: add runtime PM support and fixes | expand |
On Mon, 30 Jan 2023 14:06:39 +0200, Claudiu Beznea wrote: > This series adds runtime PM support for Microchip SPDIFRX driver. > Along with it I added few fixes identified while going though the code > and playing with Microchip SPDIFRX controller. > > Thank you, > Claudiu Beznea > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/8] ASoC: mchp-spdifrx: fix controls which rely on rsr register commit: fa09fa60385abbf99342494b280da8b4aebbc0e9 [2/8] ASoC: mchp-spdifrx: fix return value in case completion times out commit: a4c4161d6eae3ef5f486d1638ef452d9bc1376b0 [3/8] ASoC: mchp-spdifrx: fix controls that works with completion mechanism commit: d3681df44e856aab523a6eb7ba15b5e41efcbb1c [4/8] ASoC: mchp-spdifrx: disable all interrupts in mchp_spdifrx_dai_remove() commit: aaecdc32b7e35b4f9b457fb3509414aa9a932589 [5/8] ASoC: mchp-spdifrx: use unsigned long to store clk_get_rate() value commit: 36187a67ab931eae8b7d13d80fccd097971b7bac [6/8] ASoC: mchp-spdifrx: remove struct mchp_spdifrx_dev::fmt member commit: ddce4aeccacb6f575cbfad623da5f0deb2592baf [7/8] ASoC: mchp-spdifrx: add runtime pm support commit: c7db2a59438959bc881bc5722abf0d0a38681c2b [8/8] ASoC: mchp-spdifrx: document data structures commit: 514d7f9df3f409cbb0ad59e726b4923d83251e4f 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