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

Oh, thanks! That's really explain our behaviour...

I'll follow your instructions in order to disable the power_save_node

flag.


Thanks again!


________________________________
De: Takashi Iwai <tiwai@suse.de>
Enviado: viernes, 9 de marzo de 2018 15:50:47
Para: Jorge Fernandez Monteagudo
Cc: alsa-devel@alsa-project.org
Asunto: Re: [alsa-devel] Cirrus CS4207 not working on 4.14.24

On Fri, 09 Mar 2018 15:30:59 +0100,
Jorge Fernandez Monteagudo wrote:
>
> Oh, I know... That's not possible. It's a custom carrier and we only have connected
>
> the Line Out 1 (node 0x03, node 0x0A) and the S/PDIF Out 1 (node 0x08, node 0x10)
>
> to external devices.

Ah, that explains why the driver doesn't work.
As default, the driver does the dynamic codec power-down depending on
the jack detection.  And in your case, it's soldered.

That said, it's no real "bug" in the driver, but it's rather a special
use case.

As already mentioned, the power_save_node flag can be turned off via
codec hints.  You can write a codec "patch" file containing the lines
like the following:

[codec]
0x10134207 0x10134207 0
[hint]
power_save_node = no

and put it in e.g. /lib/firmware/alsa/cs4207-hack, and pass it via a
module option, e.g. add the following line

  options snd-hda-intel patch=,alsa/cs4207-hack

in any /etc/modprobe.d/*.conf file.
The comma (,) before "alsa/cs4207-hack" is no typo, it means to pass
to the secondary card.

The brief instruction is found in
Documentation/sound/hd-audio/notes.rst.


Takashi

      reply	other threads:[~2018-03-09 15:00 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
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 [this message]

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=DB5PR0701MB20077AFBA816D6737BAB4416A1DE0@DB5PR0701MB2007.eurprd07.prod.outlook.com \
    --to=jorgefm@cirsa.com \
    --cc=alsa-devel@alsa-project.org \
    --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.