From: Alexander Sergeyev <sergeev917@gmail.com> To: Takashi Iwai <tiwai@suse.de> 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: Fri, 14 Jan 2022 21:37:20 +0300 [thread overview] Message-ID: <20220114183720.n46wealclg6spxkp@localhost.localdomain> (raw) In-Reply-To: <s5ha6fy46jt.wl-tiwai@suse.de> On Fri, Jan 14, 2022 at 05:37:42PM +0100, Takashi Iwai wrote: > > I assume that the referred repository is the one at [1]. I've tried > > 081c73701ef0 "ALSA: hda: intel-dsp-config: reorder the config > > table". It crashed with nearly identical logs. > > OK, then it's still something to do with the led cdev > unregisteration. > > Could you try the patch below? This patch solved the BUG problem. But after unbind/bind micmute LED stopped working. Speakers and mute LED are fine though. Dmesg: snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff840 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff840 flags=0x0020] ... snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:90170118 snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:411111f0 snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:270300 ... snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffb80 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffb80 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:80000000 snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:20010b > > I got some time to poke the internal microphone. It works, but > > oddities are there as well. Initially I get "Mic Boost", "Capture" and > > "Internal Mic Boost" controls in alsamixer. When I run arecord, > > "Digital" control appears, but it cannot be changed until arecord is > > stopped. Subsequent arecord calls do not lock "Digital" control. This > > control affects sensitivity of the microphone and seems useful. > > That's presumably an alsa-lib softvol stuff. It's created > dynamically. So not really a kernel problem. Okay, that's good to know.
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Sergeyev <sergeev917@gmail.com> To: Takashi Iwai <tiwai@suse.de> Cc: "moderated list:SOUND" <alsa-devel@alsa-project.org>, Kailang Yang <kailang@realtek.com>, Jeremy Szu <jeremy.szu@canonical.com>, Huacai Chen <chenhuacai@kernel.org>, open list <linux-kernel@vger.kernel.org>, tiwai@suse.com, Hui Wang <hui.wang@canonical.com>, PeiSen Hou <pshou@realtek.com>, Jian-Hong Pan <jhp@endlessos.org> Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Date: Fri, 14 Jan 2022 21:37:20 +0300 [thread overview] Message-ID: <20220114183720.n46wealclg6spxkp@localhost.localdomain> (raw) In-Reply-To: <s5ha6fy46jt.wl-tiwai@suse.de> On Fri, Jan 14, 2022 at 05:37:42PM +0100, Takashi Iwai wrote: > > I assume that the referred repository is the one at [1]. I've tried > > 081c73701ef0 "ALSA: hda: intel-dsp-config: reorder the config > > table". It crashed with nearly identical logs. > > OK, then it's still something to do with the led cdev > unregisteration. > > Could you try the patch below? This patch solved the BUG problem. But after unbind/bind micmute LED stopped working. Speakers and mute LED are fine though. Dmesg: snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff820 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff840 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff840 flags=0x0020] ... snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:90170118 snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:411111f0 snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:270300 ... snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffb80 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffb80 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:80000000 snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffba0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffffbc0 flags=0x0020] snd_hda_codec_realtek hdaudioC1D0: out of range cmd 0:20:400:20010b > > I got some time to poke the internal microphone. It works, but > > oddities are there as well. Initially I get "Mic Boost", "Capture" and > > "Internal Mic Boost" controls in alsamixer. When I run arecord, > > "Digital" control appears, but it cannot be changed until arecord is > > stopped. Subsequent arecord calls do not lock "Digital" control. This > > control affects sensitivity of the microphone and seems useful. > > That's presumably an alsa-lib softvol stuff. It's created > dynamically. So not really a kernel problem. Okay, that's good to know.
next prev parent reply other threads:[~2022-01-14 18:31 UTC|newest] Thread overview: 66+ 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 ` 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 ` 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 ` 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-19 17:03 ` 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 2:00 ` Jeremy Szu 2021-05-27 6:14 ` Takashi Iwai 2021-05-27 6:14 ` Takashi Iwai 2022-01-11 19:52 ` Alexander Sergeyev 2022-01-11 19:52 ` Alexander Sergeyev 2022-01-12 9:45 ` Takashi Iwai 2022-01-12 9:45 ` Takashi Iwai 2022-01-12 10:12 ` Alexander Sergeyev 2022-01-12 10:12 ` Alexander Sergeyev 2022-01-12 10:13 ` Takashi Iwai 2022-01-12 10:13 ` Takashi Iwai 2022-01-12 10:48 ` Alexander Sergeyev 2022-01-12 10:48 ` Alexander Sergeyev 2022-01-12 20:18 ` Alexander Sergeyev 2022-01-12 20:18 ` Alexander Sergeyev 2022-01-13 7:14 ` Takashi Iwai 2022-01-13 7:14 ` Takashi Iwai 2022-01-13 18:31 ` Alexander Sergeyev 2022-01-13 18:31 ` Alexander Sergeyev 2022-01-13 21:19 ` Alexander Sergeyev 2022-01-13 21:19 ` Alexander Sergeyev 2022-01-14 16:37 ` Takashi Iwai 2022-01-14 16:37 ` Takashi Iwai 2022-01-14 18:37 ` Alexander Sergeyev [this message] 2022-01-14 18:37 ` Alexander Sergeyev 2022-01-15 7:55 ` Takashi Iwai 2022-01-15 7:55 ` Takashi Iwai 2022-01-15 15:22 ` Alexander Sergeyev 2022-01-15 15:22 ` Alexander Sergeyev 2022-01-19 9:12 ` Takashi Iwai 2022-01-19 9:12 ` Takashi Iwai 2022-01-19 9:32 ` Alexander Sergeyev 2022-01-19 9:32 ` Alexander Sergeyev 2022-01-22 19:05 ` Alexander Sergeyev 2022-01-22 19:05 ` Alexander Sergeyev 2022-01-22 20:56 ` Alexander Sergeyev 2022-01-22 20:56 ` Alexander Sergeyev 2022-01-26 15:24 ` Takashi Iwai 2022-01-26 15:24 ` Takashi Iwai 2022-01-29 14:47 ` Alexander Sergeyev 2022-01-29 14:47 ` Alexander Sergeyev 2022-01-30 11:10 ` Alexander Sergeyev 2022-01-30 11:10 ` Alexander Sergeyev 2022-01-31 14:57 ` Takashi Iwai 2022-01-31 14:57 ` Takashi Iwai 2022-02-05 15:00 ` Alexander Sergeyev 2022-02-05 15:00 ` Alexander Sergeyev 2022-02-05 17:51 ` Alexander Sergeyev 2022-02-05 17:51 ` Alexander Sergeyev 2022-02-07 14:21 ` Takashi Iwai 2022-02-07 14:21 ` Takashi Iwai 2022-02-08 19:49 ` Alexander Sergeyev 2022-02-08 19:49 ` Alexander Sergeyev 2022-02-08 14:36 ` Takashi Iwai 2022-02-08 14:36 ` Takashi Iwai 2022-02-08 19:52 ` Alexander Sergeyev 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=20220114183720.n46wealclg6spxkp@localhost.localdomain \ --to=sergeev917@gmail.com \ --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=tiwai@suse.com \ --cc=tiwai@suse.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.