ASoC:amd:acp:Add DMI quirk for Lenovo Yoga Pro 7 15ASH11
Subsystems (3)
PATCH 1/1 ASoC:amd:acp:Add DMI quirk for Lenovo Yoga Pro 7 15ASH11
Lenovo Yoga Pro 7 15ASH11 with AMD RYZEN AI MAX+ 388 (Strix Halo, ACP 7.0) uses Realtek ALC287 series codec and no any DMIC connected by ACP. All DMICs directly connet with ALC codec.
Without this quirk, Input Device of Gnome Sound settings shows Internal Stereo Microphone and Digital Microphone by default. In fact, Digital Microphone of ACP doesn't work due to no connecting with ALC287 codec, the Internal Stereo Microphone as analog device based on snd_hda_intel driver can work well.
Add a DMI quirk to override the flag to 0, consistent with the existing entry for the HN7306EA.
--- sound/soc/amd/acp-config.c | 7 +++++++ 1 file changed, 7 insertions(+)
sound/soc/amd/acp-config.c +7 -0
@@ -37,6 +37,13 @@ static const struct dmi_system_id acp70_acpi_flag_override_table[] = { DMI_MATCH(DMI_PRODUCT_NAME, "Zenbook S16 UM5606GA"), }, }, + { + /* Lenovo Yoga Pro 7 15ASH11 (Strix Halo, ACP 7.0) */ + .matches = { + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"), + DMI_MATCH(DMI_PRODUCT_NAME, "83W5"), + }, + }, {} };
Signature · 1 line
2.43.0
Mark Brown
maintainerQuoted 1 line · Jackie Dong
ASoC:amd:acp:Add DMI quirk for Lenovo Yoga Pro 7 15ASH11
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.1
Thanks!
[1/1] ASoC:amd:acp:Add DMI quirk for Lenovo Yoga Pro 7 15ASH11
https://git.kernel.org/broonie/sound/c/fc12cf16df9a
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