[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220113211903.tnzyqxb47lf3uw7z@localhost.localdomain>
Date: Fri, 14 Jan 2022 00:19:03 +0300
From: Alexander Sergeyev <sergeev917@...il.com>
To: Takashi Iwai <tiwai@...e.de>
Cc: Jeremy Szu <jeremy.szu@...onical.com>, tiwai@...e.com,
"moderated list:SOUND" <alsa-devel@...a-project.org>,
Kailang Yang <kailang@...ltek.com>,
open list <linux-kernel@...r.kernel.org>,
Huacai Chen <chenhuacai@...nel.org>,
Jian-Hong Pan <jhp@...lessos.org>,
Hui Wang <hui.wang@...onical.com>,
PeiSen Hou <pshou@...ltek.com>
Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855
G8
On Thu, Jan 13, 2022 at 09:31:43PM +0300, Alexander Sergeyev wrote:
>This is the only change in /proc/asound after the first arecord run. Overall,
>seems like a small annoyance, but I'm curious -- is it how it's supposed to
>work?
Just to clarify, this particular Digital control behavior is the same on live
Ubuntu (which uses modules and supposedly works correctly).
Also, I've posted a patch for review. It adds the quirk for my PCI subdevice id
which is not present in the current set of SND_PCI_QUIRK. The former micmute
quirk was picked up by the codec SSID and not PCI id. The patch fixes the
speakers problem for me (including the built-in drivers usecase).
Powered by blists - more mailing lists