public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 12 Jan 2022 11:13:44 +0100	[thread overview]
Message-ID: <s5hilup9s87.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220112101249.ya73jvpmqmeh4ggg@localhost.localdomain>

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

  reply	other threads:[~2022-01-12 10:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 17:03 [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 2/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 3/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 15 G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 4/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 17 G8 Jeremy Szu
2021-05-27  2:00 ` [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Jeremy Szu
2021-05-27  6:14   ` Takashi Iwai
2022-01-11 19:52 ` Alexander Sergeyev
2022-01-12  9:45   ` Takashi Iwai
2022-01-12 10:12     ` Alexander Sergeyev
2022-01-12 10:13       ` Takashi Iwai [this message]
2022-01-12 10:48         ` Alexander Sergeyev
2022-01-12 20:18           ` Alexander Sergeyev
2022-01-13  7:14             ` Takashi Iwai
2022-01-13 18:31               ` Alexander Sergeyev
2022-01-13 21:19                 ` Alexander Sergeyev
2022-01-14 16:37                 ` Takashi Iwai
2022-01-14 18:37                   ` Alexander Sergeyev
2022-01-15  7:55                     ` Takashi Iwai
2022-01-15 15:22                       ` Alexander Sergeyev
2022-01-19  9:12                         ` Takashi Iwai
2022-01-19  9:32                           ` Alexander Sergeyev
2022-01-22 19:05                             ` Alexander Sergeyev
2022-01-22 20:56                               ` Alexander Sergeyev
2022-01-26 15:24                                 ` Takashi Iwai
2022-01-29 14:47                                   ` Alexander Sergeyev
2022-01-30 11:10                                     ` Alexander Sergeyev
2022-01-31 14:57                                       ` Takashi Iwai
2022-02-05 15:00                                         ` Alexander Sergeyev
2022-02-05 17:51                                           ` Alexander Sergeyev
2022-02-07 14:21                                             ` Takashi Iwai
2022-02-08 19:49                                               ` Alexander Sergeyev
2022-02-08 14:36                                         ` Takashi Iwai
2022-02-08 19:52                                           ` Alexander Sergeyev

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=s5hilup9s87.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=chenhuacai@kernel.org \
    --cc=hui.wang@canonical.com \
    --cc=jeremy.szu@canonical.com \
    --cc=jhp@endlessos.org \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pshou@realtek.com \
    --cc=sergeev917@gmail.com \
    --cc=tiwai@suse.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