On Sun, 23 Oct 2022 15:33:19 +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!
[1/9] ASoC: jz4740-i2s: Handle independent FIFO flush bits commit: 8b3a9ad86239f80ed569e23c3954a311f66481d6 [2/9] ASoC: jz4740-i2s: Convert to regmap API commit: cf375e693252f4e8ecb6256af631ff381381a3dd [3/9] ASoC: jz4740-i2s: Simplify using regmap fields commit: 0fddb4bce669fd255f6ffade6905da5c8ed3e254 [4/9] ASoC: jz4740-i2s: Use FIELD_PREP() macros in hw_params callback commit: b355ebebb17c438b90c3d339f38a79559f7259df [5/9] ASoC: jz4740-i2s: Align macro values and sort includes commit: dacc06b812f46e0d4cfdda98134a8b5d64375341 [6/9] ASoC: jz4740-i2s: Support S20_LE and S24_LE sample formats commit: 7abd01cfc5428581b21099eb629d88e76a47b67a [7/9] ASoC: jz4740-i2s: Support continuous sample rate commit: 84a914349ba2634e8db6b0815f100697d878d033 [8/9] ASoC: jz4740-i2s: Move component functions near the component driver commit: 165afe6b66aafaafc95484ac2f0f09f78d62386b [9/9] ASoC: jz4740-i2s: Refactor DAI probe/remove ops as component ops commit: 4e02fd6207474ef2d882b8620f4c3db9a02d4ddd
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