Message ID | 20230731094303.185067-1-krzysztof.kozlowski@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: dt-bindings: Add sound-card-common.yaml | expand |
On Mon, 31 Jul 2023 11:42:51 +0200, Krzysztof Kozlowski wrote: > Almost every board machine / sound cards has "audio-routing" and "model" > properties, so we can make things simpler by introducing one common > binding. It is also expected that given property has only one definition. > > If the patchset looks good, then the next steps will be: > 1. Convert more vendor audio-routing properties to audio-routing, > 2. Add dai-links children to common binding. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [02/12] ASoC: dt-bindings: Add common sound card properties commit: a06ce12efb63bad77bd4a6cedc180f181a651920 [03/12] ASoC: dt-bindings: mediatek,mt8188-mt6359: use common sound card commit: 34e7bf1acc33da5b45ded94f459a6e30d4c6acdc [04/12] ASoC: dt-bindings: samsung,aries-wm8994: use common sound card commit: d63cff2ba4d6cb9eed12508469bf8c1b207be4f1 [05/12] ASoC: dt-bindings: samsung,midas-audio: use common sound card commit: e1d776441d7e19cd98d74bb204713940eb6951be [06/12] ASoC: dt-bindings: samsung,odroid: use common sound card commit: 5ddff831f064ee300351ffdd92bfde1e17c88861 [07/12] ASoC: dt-bindings: samsung,tm2: use common sound card commit: 631e9d4b1f3241008bc6f1c62ec0d19d745d02be [08/12] ASoC: samsung: odroid: use of_property_present to check for property commit: ebba2fd5adc2d79afa10c00255a60c79665c091a [09/12] ASoC: samsung: aries_wm8994: parse audio-routing commit: 55ebfafbc32db54259d91383faf65a5bc6bef382 [10/12] ASoC: samsung: midas_wm1811: parse audio-routing commit: c91e67145bc6d03f94416f7fbe566c6f6751cd47 [11/12] ASoC: samsung: odroid: parse audio-routing commit: 2dc8c0366599cb4dfd939e6eafd94010f3aff233 [12/12] ASoC: samsung: tm2_wm5110: parse audio-routing commit: 17b9f4387ebabb19b871bbe2d06562e48e4e7130 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