On Thu, 16 Jun 2022 16:40:42 -0500, Pierre-Louis Bossart wrote: > This patchset adds the missing jack pin remapping needed by upstream > UCM on Chromebooks, suggested by Jaroslav Kysela [1]. > > These patches were succesfully tested on GeminiLake and JasperLake > platforms, and generalized to other Chromebooks. > > [1] https://mailman.alsa-project.org/pipermail/sound-open-firmware/2022-June/004468.html > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: Intel: skl_nau88l25_max98357a: remap jack pins commit: e33ea0685a219543f3e23d88186bc6c3259b3ff4 [02/13] ASoC: Intel: skl_nau88l25_ssm4567: remap jack pins commit: 4864ef4a67edfbf802ba36c921c5e9f66e1530bf [03/13] ASoC: Intel: kbl_rt5663_max98927: remap jack pins commit: decdbf3dd7ec3e3522548f50e22d81558d151118 [04/13] ASoC: Intel: kbl_da7219_max98357a: remap jack pins commit: c2065d43ae8546668f8f187138eda8a18f7625fd [05/13] ASoC: Intel: kbl_da7219_max98927: remap jack pins commit: b9f53b9fc14e26ef3b3c33160afb094ad7ae192b [06/13] ASoC: Intel: kbl_rt5663_rt5514_max98927: remap jack pins commit: c0703be996c343b4d1036b6ba258133d88b7932b [07/13] ASoC: Intel: bxt_da7219_max98357a: remap jack pins commit: bbdd4ea2190b4712c0cd9989a5e402c7f99fc122 [08/13] ASoC: Intel: glk_rt5682_max98357a: remap jack pins commit: 4c3a68e9026ad7d3aa61278ce5702407d91d5dd9 [09/13] ASoC: Intel: cml_rt1011_rt5682: remap jack pins commit: 77a036e8b074a679c0177f61c9d3b8e942673141 [10/13] ASoC: Intel: sof_cs42l42: remap jack pins commit: 7459c8940a506280908f8b5e9e4227784a0b6569 [11/13] ASoC: Intel: sof_da7219_max98373: remap jack pins commit: 2913bb1f6830251416659dbb04c392bbc9592f14 [12/13] ASoC: Intel: sof_nau8825: remap jack pins commit: 2a172d2f06c155ea7c9b34f47febdfe9b9bbe1c2 [13/13] ASoC: Intel: sof_rt5682: remap jack pins commit: c3ce12b27e562bf3a255bc9f3096dacea2194dd8 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
