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 14:24:10 +0000	[thread overview]
Message-ID: <DB5PR0701MB20073FB08658E720786A69D6A1DE0@DB5PR0701MB2007.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <s5hlgf15ra7.wl-tiwai@suse.de>

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?

________________________________
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

  reply	other threads:[~2018-03-09 14:24 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 [this message]
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=DB5PR0701MB20073FB08658E720786A69D6A1DE0@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.