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.
________________________________ De: Takashi Iwai tiwai@suse.de Enviado: viernes, 9 de marzo de 2018 15:25:38 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:24:10 +0100, Jorge Fernandez Monteagudo wrote:
Sorry for the dumb question, but when you say "testing from the speaker" or "testing from the headphone"
it's enough using alsamixer to mute headphone or mute speaker and run an aplay when running alsa-info.sh?
No, I meant actually plugging and unplugging the headphone jack (and the corresponding mixer changes).
Takashi
De: Takashi Iwai tiwai@suse.de Enviado: viernes, 9 de marzo de 2018 14:09:52 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 10:45:35 +0100, Jorge Fernandez Monteagudo wrote:
Hi!
Your little patch works! I've attached the alsa-info for the 4.14.24 kernel once the
system is running and no sound is available.
The nodes are related to audio output. 0x03 DAC2 PCM linked to 0x0A: Line Out1
I suspect nodes 0x09, 0x0A and 0x0B are not able to recover from D3 state.
That explains better. But NID 0x0b has no power control, so it shouldn't be affected by itself. Rather NID 0x04 power-down can be the issue, at least, for speaker outputs. For the headphone, both NID 0x09 and 0x03 are used.
Please try the driver without the patch, and get alsa-info.sh output while testing from the speaker, and while testing the headphone, individually. Attach both outputs for comparison. Maybe better to compressed, otherwise it becomes too long.
thanks,
Please [2 <text/html; us-ascii (quoted-printable)>]