All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Labisch <clnetbox@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Takashi Iwai <tiwai@suse.com>,
	amadeuszx.slawinski@linux.intel.com
Subject: Re: Haswell audio no longer working with new Catpt driver
Date: Sat, 2 Jan 2021 13:16:12 +0100	[thread overview]
Message-ID: <X/BkDB2CU+Bbyz/0@kroah.com> (raw)
In-Reply-To: <83651c8002ae10e358693adfde65e85b3c95953d.camel@gmail.com>

On Sat, Jan 02, 2021 at 12:50:44PM +0100, Christian Labisch wrote:
> On Fri, 2021-01-01 at 18:24 +0100, Takashi Iwai wrote:
> > On Fri, 01 Jan 2021 14:40:39 +0100,
> > Christian Labisch wrote:
> > > 
> > > $ cat /sys/module/snd_hda_intel/parameters/power_save
> > > 0
> > 
> > Hm, then the best would be to run git bisect for spotting out the
> > breaking commit.  There has been no change in VIA codec driver at all
> > between v5.9 and v5.10, so the rest possibility is either in HD-audio
> > codec helper code or controller code (or both) -- if it's about the
> > changes in the sound driver.
> > 
> > Or you can try the oneliner below as a test shot; it might keep the
> > widget node power D0, which is currently the only possible appearance
> > of the difference between working and non-working cases.
> > 
> > BTW, please avoid top-posting.  It's confusing.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> > -- 8< --
> > --- a/sound/pci/hda/patch_via.c
> > +++ b/sound/pci/hda/patch_via.c
> > @@ -115,7 +115,7 @@ static struct via_spec *via_new_spec(struct hda_codec *codec)
> >         spec->gen.keep_eapd_on = 1;
> >         spec->gen.pcm_playback_hook = via_playback_pcm_hook;
> >         spec->gen.add_stereo_mix_input = HDA_HINT_STEREO_MIX_AUTO;
> > -       codec->power_save_node = 1;
> > +       // codec->power_save_node = 1;
> >         spec->gen.power_down_unused = 1;
> >         codec->patch_ops = via_patch_ops;
> >         return spec;
> 
> Hi Takashi,
> 
> Thank you ! I think we have tried what we could to work around this issue.
> There is obviously something wrong with the kernel which has to get fixed.

Yes, and that is what we are trying to figure out here.  Does the above
change work?

> Hi Greg and Lars,
> 
> From my understanding there are fundamental changes regarding the audio drivers.
> The sound should (and has to) work out-of-the-box without any user interactions.

Of course, but we need to figure out the change that caused the problem
here.  If someone who can reproduce this can run 'git bisect' that is
the fastest way to make this happen.

> As you can see in the post below, other users are facing exactly the same issue.
> It would be great if this could be solved as soon as possible, maybe in 5.10.5 ?
> 
> https://forum.manjaro.org/t/issue-after-kernel-5-10-update-speakers-not-working-on-laptop/45496

5.10.5 will be out next week, and that's not how stable kernels work.
The fix needs to be in Linus's tree first before we can take it in a
stable kernel release.  We need to figure out the fix first before it
can go anywhere...

thanks,

greg k-h

  reply	other threads:[~2021-01-02 12:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 15:26 sound Christian Labisch
2020-12-30 15:36 ` sound Greg KH
2020-12-30 15:45   ` sound Christian Labisch
2020-12-30 18:10     ` sound Christian Labisch
2020-12-31  8:33       ` sound Greg Kroah-Hartman
2020-12-31 10:04         ` Haswell audio no longer working with new Catpt driver (was: sound) Lars-Peter Clausen
2020-12-31 10:04           ` Lars-Peter Clausen
2020-12-31 10:50           ` Christian Labisch
2020-12-31 10:50             ` Christian Labisch
2020-12-31 11:20             ` Haswell audio no longer working with new Catpt driver Amadeusz Sławiński
2020-12-31 11:20               ` Amadeusz Sławiński
2020-12-31 11:31               ` Christian Labisch
2020-12-31 11:31                 ` Christian Labisch
     [not found]                 ` <1ad341b1b0e0eefb83d157ac24d162eaad53ab32.camel@gmail.com>
2020-12-31 15:30                   ` Lars-Peter Clausen
2021-01-01 11:10                     ` Christian Labisch
2021-01-01 12:09                       ` Takashi Iwai
2021-01-01 13:25                         ` Christian Labisch
2021-01-01 13:29                           ` Lars-Peter Clausen
2021-01-01 13:40                             ` Christian Labisch
2021-01-01 17:24                               ` Takashi Iwai
2021-01-02 11:50                                 ` Christian Labisch
2021-01-02 12:16                                   ` Greg KH [this message]
2020-12-31 11:10           ` Haswell audio no longer working with new Catpt driver (was: sound) Christian Labisch
2020-12-31 11:10             ` Christian Labisch

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=X/BkDB2CU+Bbyz/0@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=clnetbox@gmail.com \
    --cc=lars@metafoo.de \
    --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 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.