[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hilugw0l0.wl-tiwai@suse.de>
Date: Wed, 19 Jan 2022 10:12:43 +0100
From: Takashi Iwai <tiwai@...e.de>
To: Alexander Sergeyev <sergeev917@...il.com>
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 Sat, 15 Jan 2022 16:22:15 +0100,
Alexander Sergeyev wrote:
>
> On Sat, Jan 15, 2022 at 08:55:28AM +0100, Takashi Iwai wrote:
> > > This patch solved the BUG problem. But after unbind/bind micmute LED
> > > stopped working. Speakers and mute LED are fine though.
> > Does the corresponding sysfs entry exist in /sys/class/leds/*?
>
> Yes.
>
> > And can you control LED over there?
>
> After "out of range cmd" messages the sysfs entry remains present, but writing
> ones to the brightness file stops to produce any effect.
>
> Actually, the timing issues are present here as well. Sometimes unbind & bind
> works fine. But fails on the second round.
Here "fails" means the kernel Oops / crash? If yes, the back trace
would be helpful.
thanks,
Takashi
Powered by blists - more mailing lists