On Thu, 8 Sep 2022 12:11:44 -0400, Nícolas F. R. A. Prado wrote:
The i2s ports on MediaTek SoCs only support a single data lane. In order to achieve full-duplex operation thus two i2s ports, one for input and one for output, need to be used together and sharing a single clock from one of the ports.
This clock sharing setting was previously read by the sound platform driver from the devicetree, but given that the input/output pairing is closely related to which codecs are connected to which ports, the machine sound driver can infer and set it, so that no DT property is required.
[...]
Applied to
broonie/sound.git for-next
Thanks!
[01/10] ASoC: mediatek: mt8192: Allow setting shared clocks from machine driver commit: 8ae4fcfd5b11b5c33154732fcad99ad0f5843ce2 [02/10] ASoC: mediatek: mt8192-mt6359: Make i2s9 share the clock from i2s8 commit: 3ffb9fa3963964a730c34f48e502ac0625efc145 [03/10] ASoC: mediatek: mt8192: Remove clock share parsing from DT commit: 9ccd51ce396a46d9d4d0c87aa6a82dd26a2f281a [04/10] ASoC: mediatek: mt8183: Allow setting shared clocks from machine driver commit: fea84890e5c1fb65ae8e25b2f9b86363af1f45f2 [05/10] ASoC: mediatek: mt8183: Configure shared clocks commit: 4583392a135cc30409f5a6ceebb8374e550b03e0 [06/10] ASoC: mediatek: mt8183: Remove clock share parsing from DT commit: cbebe67859a0e8d51e578fdd9f927f8ef2504ba4 [07/10] arm64: dts: mediatek: kukui: Remove i2s-share properties commit: b3821f7839c2ec322926d16557aff29f4be1f4dc [08/10] ASoC: mediatek: mt8186: Allow setting shared clocks from machine driver commit: 4132a778e806f77c2bd01a9a34b07edc9dd99d76 [09/10] ASoC: mediatek: mt8186: Configure shared clocks commit: 9986bdaee4776c5d595933cace9d54c6bc084e91 [10/10] ASoC: mediatek: mt8186: Remove clock share parsing from DT commit: 62da80c6a124dd68b12c4d2197ecc74b79823571
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