All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jorge Fernandez Monteagudo <jorgefm@cirsa.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Cirrus CS4207 not working on 4.14.24
Date: Fri, 09 Mar 2018 10:11:16 +0100	[thread overview]
Message-ID: <s5h8tb17gwb.wl-tiwai@suse.de> (raw)
In-Reply-To: <DB5PR0701MB2007E6A97934EB7DC869DEA6A1DE0@DB5PR0701MB2007.eurprd07.prod.outlook.com>

On Fri, 09 Mar 2018 08:56:08 +0100,
Jorge Fernandez Monteagudo wrote:
> 
> Hi all!
> 
> 
> I've updated my system from a 3.16.7 kernel to a 4.14.24 kernel and sound stops working.
> 
> I have a Cirrus logic CS4207 codec. I've tracked down the problem using the '/proc/asound/card0/codec\#0'
> 
> info. With the 3.16.7 kernel all nodes power states are:
> 
> 
> Node 0x03: Power: setting=D0, actual=D0
> Node 0x0a: Power: setting=D0, actual=D0
> 
> and with 4.14.24 they are on
> 
> 
> Node 0x03: Power: setting=D0, actual=D3
> Node 0x0a: Power: setting=D3, actual=D3

And what nodes are these?
At best, please give alsa-info.sh output.


> Once in this situation I'm able to go to D0 again and make the sound works. I've used
> hda-verb 0.4 to SET_POWER_STATE to 0 with no luck. Finally, I've patched the 4.14.24
> to avoid changing to D3 and now the sound is working again. I know it's not the way to go
> but I need the sound...

It's the feature of power-saving, and can be turned off by passing the
hint via "patch" firmware.  If you can compile, the easiest way would
be the oneliner like:

--- a/sound/pci/hda/patch_cirrus.c
+++ b/sound/pci/hda/patch_cirrus.c
@@ -589,7 +589,7 @@ static struct cs_spec *cs_alloc_spec(struct hda_codec *codec, int vendor_nid)
 		return NULL;
 	codec->spec = spec;
 	spec->vendor_nid = vendor_nid;
-	codec->power_save_node = 1;
+	// codec->power_save_node = 1;
 	snd_hda_gen_spec_init(&spec->gen);
 
 	return spec;

If the widgets 0x03 and/or 0x0a have to be always turned on, we can
keep them on.  There are several ways to do that.


Takashi

  reply	other threads:[~2018-03-09  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  7:56 Cirrus CS4207 not working on 4.14.24 Jorge Fernandez Monteagudo
2018-03-09  9:11 ` Takashi Iwai [this message]
2018-03-09  9:45   ` Jorge Fernandez Monteagudo
2018-03-09 13:09     ` Takashi Iwai
2018-03-09 14:24       ` Jorge Fernandez Monteagudo
2018-03-09 14:25         ` Takashi Iwai
2018-03-09 14:30           ` Jorge Fernandez Monteagudo
2018-03-09 14:50             ` Takashi Iwai
2018-03-09 15:00               ` Jorge Fernandez Monteagudo

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=s5h8tb17gwb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jorgefm@cirsa.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 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.