Message ID | 20211214142049.20422-1-stephan@gerhold.net (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: qcom: Parse "pin-switches" and "widgets" from DT | expand |
On Tue, 14 Dec 2021 15:20:45 +0100, Stephan Gerhold wrote: > Some sound card setups might require extra pin switches to allow > turning off certain audio components. simple-card supports this > already using the "pin-switches" and "widgets" device tree property. > This series makes it possible to use the same properties for the Qcom > sound cards. > > To implement that, the function that parses the "pin-switches" property > in simple-card-utils.c is first moved into the ASoC core. Then two > simple function calls are added to the common Qcom sound card DT parser. > Finally there is a small patch for the msm8916-wcd-analog codec to make > it possible to model sound card setups used in some MSM8916 smartphones. > (See PATCH 2/4 for an explanation of some real example use cases.) > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/4] ASoC: core: Add snd_soc_of_parse_pin_switches() from simple-card-utils commit: 3d4641a42ccf1593b3f3a474ee7541727acbb8e0 [2/4] ASoC: dt-bindings: qcom: sm8250: Document "pin-switches" and "widgets" commit: 37a49da9a7d5ac1f7128000de42ff222da46ba7a [3/4] ASoC: qcom: common: Parse "pin-switches" and "widgets" from DT commit: 2623e66de125ba153e41be6a0b8af24cae8aa436 [4/4] ASoC: msm8916-wcd-analog: Use separate outputs for HPH_L/HPH_R commit: 319a05330f4ff3f951f9c42094958c6cdef393b3 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