On Mon, 1 Mar 2021 19:08:58 +0200, Codrin Ciubotariu wrote:
SAMA7G5 includes an updated version of I2S-MCC, found previously on SAM9X60. This controller includes 8 data pins, 4 for playback and 4 for capture. For I2S and LEFT_J formats, these pins can be used to send/receive up to 8 audio channels. For DSP_A, with TDM, any pins pair (DIN/DOUT) from these 4 can be selected to send/receive data. This version also includes 2 FIFOs (send and receive). This patch set starts by moving the driver's bindings to yaml and continues with adding a new compatible for the SAMA7G5 variant, followed by the changes needed for I2S/LEFT_J support, TDM pin pair selection and FIFO support, exclusively for SAMA7G5.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] dt-bindings: mchp,i2s-mcc: Add SAMA7G5 to binding commit: 4423a2724e3d1d55adfb1d515a9fa0759e95451e [2/7] ASoC: mchp-i2s-mcc: Add compatible for SAMA7G5 commit: 02d212ce7c72509139ceeee46f631fdf20e4c2fb [3/7] ASoC: mchp-i2s-mcc: Add multi-channel support for I2S and LEFT_J formats commit: 89dcd5cc4bee9f87ef597374a8d7dc0c51436fb2 [4/7] dt-bindings: mchp, i2s-mcc: Add property to specify pin pair for TDM commit: d43f821b8a0162de9e9d392a8f1907c5638f558a [5/7] ASoC: mchp-i2s-mcc: Add support to select TDM pins commit: 1d6257bbe6e9fcaf639f313ccd4cebe1f5e46865 [6/7] ASoC: mchp-i2s-mcc: Add FIFOs support commit: cb43e3692731401d4303c378f530c43bd283716e
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