LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: 藍挺瑋 <lantw44@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, harshapriya.n@intel.com,
	kai.vehmanen@intel.com, linux-kernel@vger.kernel.org,
	mcatanzaro@redhat.com, perex@perex.cz, stable@vger.kernel.org,
	tiwai@suse.com
Subject: Re: [REGRESSION] "ALSA: HDA: Early Forbid of runtime PM" broke my laptop's internal audio
Date: Tue, 17 Aug 2021 00:57:03 +0800	[thread overview]
Message-ID: <54f729b54ffa6226a97c9eac897d5f08f6636e31.camel@gmail.com> (raw)
In-Reply-To: <s5hy293gj3j.wl-tiwai@suse.de>

於 星期日,2021-08-15 於 11:20 +0200,Takashi Iwai 提到:
> On Sat, 14 Aug 2021 16:02:36 +0200,
> 藍挺瑋 wrote:
> > 
> > I am not sure if I should join this old thread, but it seems that I saw the
> > same
> > issue on my ASUS B23E laptop. It couldn't produce any sound after upgrading
> > to
> > Linux 5.10, and 'git bisect' shows it was broken by the same commit
> > a0645daf16101bb9a6d87598c17e9a8b7bd60ea7.
> > 
> > I have tested the latest master branch (v5.14-rc4-322-gcceb634774ef) last
> > week.
> > It still had no sound. If I reverted the broken commit, sound worked.
> 
> > 
> > alsa-info from the broken kernel:
> > https://gist.github.com/lantw44/0660e059c488e3ff3d841bb03b371866
> > 
> > alsa-info from the working kernel:
> > https://gist.github.com/lantw44/9367f425e4f5ba98cf12343cb90f3301
> 
> Thanks for the report.  A quick workaround be a patch like below.
> Could you verify whether it fixes the problem?

Yes, it fixes the problem.

> 
> 
> Takashi
> 
> --- a/sound/pci/hda/patch_via.c
> +++ b/sound/pci/hda/patch_via.c
> @@ -1041,6 +1041,7 @@ static const struct hda_fixup via_fixups[] = {
>  };
>  
>  static const struct snd_pci_quirk vt2002p_fixups[] = {
> +       SND_PCI_QUIRK(0x1043, 0x13f7, "Asus B23E", VIA_FIXUP_POWER_SAVE),
>         SND_PCI_QUIRK(0x1043, 0x1487, "Asus G75", VIA_FIXUP_ASUS_G75),
>         SND_PCI_QUIRK(0x1043, 0x8532, "Asus X202E", VIA_FIXUP_INTMIC_BOOST),
>         SND_PCI_QUIRK_VENDOR(0x1558, "Clevo", VIA_FIXUP_POWER_SAVE),


  reply	other threads:[~2021-08-16 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 22:39 [REGRESSION] "ALSA: HDA: Early Forbid of runtime PM" broke my laptop's internal audio Michael Catanzaro
2021-01-29  1:37 ` N, Harshapriya
     [not found]   ` <U3BPNQ.P8Q6LYEGXHB5@redhat.com>
     [not found]     ` <s5hsg6jlr4q.wl-tiwai@suse.de>
     [not found]       ` <9ACPNQ.AF32G3OJNPHA3@redhat.com>
     [not found]         ` <IECPNQ.0TZXZXWOZX8L2@redhat.com>
     [not found]           ` <8CEPNQ.GAG87LR8RI871@redhat.com>
2021-01-29 16:17             ` Takashi Iwai
2021-01-29 17:24               ` Michael Catanzaro
2021-01-29 18:56                 ` Takashi Iwai
2021-08-14 14:02                   ` 藍挺瑋
2021-08-15  9:20                     ` Takashi Iwai
2021-08-16 16:57                       ` 藍挺瑋 [this message]
2021-08-17  5:25                         ` Takashi Iwai
2021-02-01  4:24               ` Erich Ritz
2021-02-01 13:57                 ` Greg KH

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=54f729b54ffa6226a97c9eac897d5f08f6636e31.camel@gmail.com \
    --to=lantw44@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=harshapriya.n@intel.com \
    --cc=kai.vehmanen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcatanzaro@redhat.com \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --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: 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;
as well as URLs for NNTP newsgroup(s).