Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 19 Jan 2022 10:12:43 +0100
Message-ID: <s5hilugw0l0.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Alexander Sergeyev <sergeev917@gmail.com>
Cc:     Jeremy Szu <jeremy.szu@canonical.com>, tiwai@suse.com,
        "moderated list:SOUND" <alsa-devel@alsa-project.org>,
        Kailang Yang <kailang@realtek.com>,
        open list <linux-kernel@vger.kernel.org>,
        Huacai Chen <chenhuacai@kernel.org>,
        Jian-Hong Pan <jhp@endlessos.org>,
        Hui Wang <hui.wang@canonical.com>,
        PeiSen Hou <pshou@realtek.com>
Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8
In-Reply-To: <20220115152215.kprws5nja2i43qax@localhost.localdomain>
References: <s5ho84h9tit.wl-tiwai@suse.de>
        <20220112101249.ya73jvpmqmeh4ggg@localhost.localdomain>
        <s5hilup9s87.wl-tiwai@suse.de>
        <20220112104827.4aymoth7ua65nwge@localhost.localdomain>
        <20220112201824.qmphnz2hx4frda6e@localhost.localdomain>
        <s5h8rvk85uy.wl-tiwai@suse.de>
        <20220113183141.kla37mbqmo4x6wxp@localhost.localdomain>
        <s5ha6fy46jt.wl-tiwai@suse.de>
        <20220114183720.n46wealclg6spxkp@localhost.localdomain>
        <s5hsftp3027.wl-tiwai@suse.de>
        <20220115152215.kprws5nja2i43qax@localhost.localdomain>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

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