On Fri, 8 Jul 2022 17:02:33 +0100, Aidan MacDonald wrote: > This series is a preparatory cleanup of the jz4740-i2s driver before > adding support for a new SoC. The two improvements are lifting > unnecessary restrictions on sample rates and formats -- the existing > ones appear to be derived from the limitations of the JZ4740's internal > codec and don't reflect the actual capabilities of the I2S controller. > > I'm unable to test the series on any JZ47xx SoCs, but I have tested > on an X1000 (which is the SoC I'll be adding in a followup series). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [02/11] ASoC: jz4740-i2s: Remove unused 'mem' resource commit: cd57272c4e686d4ad2d2e775a40a3eac9f96ec7c [04/11] ASoC: jz4740-i2s: Simplify using regmap fields (no commit info) [05/11] ASoC: jz4740-i2s: Use FIELD_PREP() macros in hw_params callback (no commit info) [06/11] ASoC: jz4740-i2s: Align macro values and sort includes (no commit info) [07/11] ASoC: jz4740-i2s: Make the PLL clock name SoC-specific (no commit info) [08/11] ASoC: jz4740-i2s: Support S20_LE and S24_LE sample formats (no commit info) [09/11] ASoC: jz4740-i2s: Support continuous sample rate (no commit info) [10/11] ASoC: jz4740-i2s: Move component functions near the component driver (no commit info) 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
