From: Greg KH <gregkh@linuxfoundation.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, jeffbai@aosc.io,
broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, mario.limonciello@amd.com, me@jwang.link,
end.to.start@mail.ru, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1+] ASoC: amd: yc: fix internal mic on Xiaomi Book Pro 14 2022
Date: Tue, 12 Nov 2024 09:30:27 +0100 [thread overview]
Message-ID: <2024111221-brittle-mumbo-d475@gregkh> (raw)
In-Reply-To: <2948220EEF71E78E+20241111070804.979792-1-wangyuli@uniontech.com>
On Mon, Nov 11, 2024 at 03:08:04PM +0800, WangYuli wrote:
> From: Mingcong Bai <jeffbai@aosc.io>
>
> [ Upstream commit de156f3cf70e17dc6ff4c3c364bb97a6db961ffd ]
>
> Xiaomi Book Pro 14 2022 (MIA2210-AD) requires a quirk entry for its
> internal microphone to be enabled.
>
> This is likely due to similar reasons as seen previously on Redmi Book
> 14/15 Pro 2022 models (since they likely came with similar firmware):
>
> - commit dcff8b7ca92d ("ASoC: amd: yc: Add Xiaomi Redmi Book Pro 15 2022
> into DMI table")
> - commit c1dd6bf61997 ("ASoC: amd: yc: Add Xiaomi Redmi Book Pro 14 2022
> into DMI table")
>
> A quirk would likely be needed for Xiaomi Book Pro 15 2022 models, too.
> However, I do not have such device on hand so I will leave it for now.
>
> Signed-off-by: Mingcong Bai <jeffbai@aosc.io>
> Link: https://patch.msgid.link/20241106024052.15748-1-jeffbai@aosc.io
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
> ---
> sound/soc/amd/yc/acp6x-mach.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-11-12 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 7:08 [PATCH 6.1+] ASoC: amd: yc: fix internal mic on Xiaomi Book Pro 14 2022 WangYuli
2024-11-12 8:30 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024111221-brittle-mumbo-d475@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=end.to.start@mail.ru \
--cc=jeffbai@aosc.io \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=me@jwang.link \
--cc=perex@perex.cz \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=wangyuli@uniontech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox