On Wed, 23 Oct 2024 20:56:56 +1300, Ryan Walklin wrote: > V3 of this patch adding support for the Allwinner H616 (and variant)'s audio codec. Some clarification of comments, particularly regarding the clock driver changes, and a small fix for the device tree binding (apologies I forgot to re-run dt_binding_check on V2). Review comments otherwise addressed and reviews noted. > > Changelog v1..v2: > - Reordered patches to group ASoC changes > - Corrected PLL_AUDIO clock dividers to match values from manual and vendor SDK. > - Remove PLL_AUDIO_4X clock from the device tree binding (not used in the driver). > - Restrict TX-only DMA changes to the H616. > - Change the codec name to fit into the 16 char limit. > - Move the codec (and spdif) blocks in the H616 DTSI to restore address-order. > - Add board enablement (and power/GPIO changes for RG35XX to support speaker amp). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [2/7] dt-bindings: allwinner: add H616 sun4i audio codec binding commit: 542e19c20506953c03eec57b1cb65355164dfb64 [3/7] ASoC: sun4i-codec: Add support for different DAC FIFOC addresses to quirks commit: 5836a9d2ca48bb7473bb10d061c03525d8f4f163 [4/7] ASoC: sun4i-codec: Add playback only flag to quirks commit: 9fde21d6c5d1f75c2651442e5aae463545136aad [5/7] ASoC: sun4i-codec: support allwinner H616 codec commit: 9155c321a1d0220a60878f2c99bc79b5a7e34d95 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
