From: Mark Pearson <markpearson@lenovo.com>
To: Mark Brown <broonie@kernel.org>
Cc: stable@kernel.org, alsa-devel@alsa-project.org,
lgirdwood@gmail.com, Gabriel Craciunescu <nix.or.die@gmail.com>,
tiwai@suse.com
Subject: Re: [External] Re: [PATCH] ASoC: AMD Renoir - add DMI entry for Lenovo 2020 AMD platforms
Date: Wed, 2 Jun 2021 12:19:25 -0400 [thread overview]
Message-ID: <8d6916ed-af82-e9ff-7728-411a5e2a48eb@lenovo.com> (raw)
In-Reply-To: <162265045454.22459.12647691279142134758.b4-ty@kernel.org>
Hi mark
On 2021-06-02 12:16 p.m., Mark Brown wrote:
> On Mon, 31 May 2021 10:55:02 -0400, Mark Pearson wrote:
>> More laptops identified where the AMD ACP bridge needs to be blocked
>> or the microphone will not work when connected to HDMI.
>>
>> Use DMI to block the microphone PCM device for these platforms.
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
>
> [1/1] ASoC: AMD Renoir - add DMI entry for Lenovo 2020 AMD platforms
> commit: 19a0aa9b04c5ab9a063b6ceaf7211ee7d9a9d24d
>
> 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
>
My apologies - I found out just now that this patch causes problems for
the microphone that I'd missed so need to revert it. I was writing the
email to pull the patch when I got your update :(
Sorry for the confusion and churn - I need to go and work with the
firmware team to solve this one.
Mark
next prev parent reply other threads:[~2021-06-02 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 14:55 [PATCH] ASoC: AMD Renoir - add DMI entry for Lenovo 2020 AMD platforms Mark Pearson
2021-06-02 16:16 ` Mark Brown
2021-06-02 16:19 ` Mark Pearson [this message]
2021-06-02 16:23 ` [External] " Mark Brown
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=8d6916ed-af82-e9ff-7728-411a5e2a48eb@lenovo.com \
--to=markpearson@lenovo.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=nix.or.die@gmail.com \
--cc=stable@kernel.org \
--cc=tiwai@suse.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