linux-kernel - Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hilup9s87.wl-tiwai@suse.de>
Date:   Wed, 12 Jan 2022 11:13:44 +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 Wed, 12 Jan 2022 11:12:49 +0100,
Alexander Sergeyev wrote:
> 
> On Wed, Jan 12, 2022 at 10:45:46AM +0100, Takashi Iwai wrote:
> > The problem is about the built-in drivers, or do you see the very
> > same problem even with modules?
> 
> The problem is definitely there for the built-in drivers which I've
> tested quite a lot. It's the primary usecase for me, as I tend to
> build minimal device-specific and self-contained kernels in Gentoo.
> 
> For builds with modules things are not very consistent. Live Ubuntu
> with an older (and probably vendor-patched) kernel works just fine,
> but when I pull Ubuntu kernel sources and build it with the mostly
> same config (including modules) it boots with no sound in
> Gentoo. Mostly same -- because I need nvme drivers to be built-in as I
> don't use initrd.

Sounds like some timing issue, then.  It's pretty hard to debug,
unfortunately.

You may try to get the codec proc dump with COEF by passing
snd_hda_codec.dump_coef=1 module option for both working and
non-working cases.  Check the difference of the COEF and apply the
difference with hda-verb manually.


> > AFAIK, quite a few AMD platforms tend to have some issues with
> > various devices showing initialization problems at the early
> > boot. Just reloading / rebinding the device later often helps.
> 
> Is it possible to do with the built-in drivers?

You can unbind and re-bind the PCI (HD-audio controller) device via
sysfs.


Takashi