From: Takashi Iwai <tiwai@suse.de>
To: Alexander Sergeyev <sergeev917@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jeremy Szu <jeremy.szu@canonical.com>,
Werner Sembach <wse@tuxedocomputers.com>,
Hui Wang <hui.wang@canonical.com>,
Cameron Berkenpas <cam@neo-zeon.de>,
Kailang Yang <kailang@realtek.com>, Sami Loone <sami@loone.fi>,
Elia Devito <eliadevito@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ALSA: hda/realtek: fix speakers and micmute on HP 855 G8
Date: Fri, 14 Jan 2022 17:54:48 +0100 [thread overview]
Message-ID: <s5h5yqm45rb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220114165050.ouw2nknuspclynro@localhost.localdomain>
On Fri, 14 Jan 2022 17:50:50 +0100,
Alexander Sergeyev wrote:
>
> There are several PCI ids associated with HP EliteBook 855 G8 Notebook
> PC. Commit 0e68c4b11f1e6 ("ALSA: hda/realtek: fix mute/micmute LEDs for
> HP 855 G8") covers 0x103c:0x8896, while this commit covers 0x103c:0x8895
> which needs some additional work on top of the quirk from 0e68c4b11f1e6.
>
> Note that the device can boot up with working speakers and micmute LED
> without this patch, but the success rate would be quite low (order of
> 16 working boots across 709 boots) at least for the built-in drivers
> scenario. This also means that there are some timing issues during early
> boot and this patch is a workaround.
>
> With this patch applied speakers and headphones are consistenly working,
> as well as mute/micmute LEDs and the internal microphone.
>
> Signed-off-by: Alexander Sergeyev <sergeev917@gmail.com>
Thanks, applied now.
Takashi
next prev parent reply other threads:[~2022-01-14 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 16:49 [PATCH v2 0/1] ALSA: hda/realtek: fix speakers and micmute on HP 855 Alexander Sergeyev
2022-01-14 16:50 ` [PATCH v2 1/1] ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 Alexander Sergeyev
2022-01-14 16:54 ` Takashi Iwai [this message]
2022-01-15 15:47 ` Kai-Heng Feng
2022-01-15 16:32 ` Alexander Sergeyev
2022-01-17 0:12 ` Kai-Heng Feng
2022-01-17 18:11 ` Alexander Sergeyev
2022-01-19 0:18 ` Kai-Heng Feng
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=s5h5yqm45rb.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cam@neo-zeon.de \
--cc=eliadevito@gmail.com \
--cc=hui.wang@canonical.com \
--cc=jeremy.szu@canonical.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sami@loone.fi \
--cc=sergeev917@gmail.com \
--cc=tiwai@suse.com \
--cc=wse@tuxedocomputers.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;
as well as URLs for NNTP newsgroup(s).