All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: regression: from 3.8 to 3.9: headphones output no sound on Intel HDA, codec VIA VT1802
Date: Fri, 17 May 2013 08:04:01 +0200	[thread overview]
Message-ID: <s5hk3myuoq6.wl%tiwai@suse.de> (raw)
In-Reply-To: <CALxABCa27gVVJGWM-crvFOPmJXdZ0FEBc3=dPZ0pG+AhDB78cA@mail.gmail.com>

At Thu, 16 May 2013 22:10:47 +0200,
Alex Riesen wrote:
> 
> On Thu, May 16, 2013 at 1:00 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > So, we need to disable the widgets power control in patch_via.c
> > completely as a quick workaround.  Could you check whether the patch
> > below is OK (except for the possible headphone mute issue)?
> 
> Well... It seems that something went unnoticed. This command seems
> to be essential for this (and the revised) patch to get the headphone
> output at all:
> 
>         hda-verb /dev/snd/hwC0D0 0x25 SET_PIN_WID 0xc0

Do you mean that the headphone doesn't work without this even after
the patch?  It's weird that the alsa-info.sh output you attached below
already contains it, i.e. 0x25 showing 0xc0.

Or, is the attached output the result after you ran hda-verb like the
above?

> I also used to run the other command after unplugging and re-plugging
> (without it, the headphone is muted after re-plugging):
> 
>         hda-verb /dev/snd/hwC0D0 0x25 SET_EAPD 0x02
> 
> But running
> 
>         hda-verb /dev/snd/hwC0D0 0x24 SET_EAPD 0x03
> 
> also helps to restore the headphone output after re-plugging.
> 
> > Regarding the headphone mute: after confirming the headphone itself
> > is working with the patch, please give alsa-info.sh outputs again
> > with and without the headphone plug.
> 
> Attached.
>
> > Then, at the headphone plugged (and the speaker is still audible
> > wrongly), take a look at /proc/asound/card0/codec#0 file.
> > Look for "Node 0x24", and check whether Pin-ctls item shows 0x00.
> 
> It does. And there is no output from the speakers.

Hmm.  I'm confused.  I thought you mentioned that the speaker is
unmuted?

- Use the patched kernel, play without headphone, confirm that the
  speaker works.  Get alsa-info.sh output at this point.

- Plug the headphone, play, and check whether the headphone works and
  the speaker is muted.
  Again, get alsa-info.sh output at this point, no matter whether the
  headphone works or not.

If something is wrong at this point, try hda-verb things.  Basically,
giving some verbs to 0x25 is to work on the headphone, and 0x24 for
the speaker.  You can check the previous value by the corresponding
GET_* verb.  For example, if you want to change the pin control of
0x25 to 0xc0, check the current value by

	hda-verb /dev/snd/hwC0D0 0x25 GET_PIN_WID 0

(the GET_* takes the last argument 0), then

	hda-verb /dev/snd/hwC0D0 0x25 SET_PIN_WID 0xc0

I'm asking it because, in the case above, if the previous value shows
0xc0 and the headphone doesn't work, and if setting the same value
again fixes the headphone output, it must be new behavior I've never
seen.

In anyway, if you make things working, please give exactly what you
did, and take again alsa-info.sh output, too.


thanks,

Takashi

  reply	other threads:[~2013-05-17  6:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12  9:53 regression: from 3.8 to 3.9: headphones output no sound on Intel HDA, codec VIA VT1802 Alex Riesen
2013-05-12  9:58 ` Fwd: " Alex Riesen
2013-05-13 15:26 ` Takashi Iwai
2013-05-13 15:53   ` Takashi Iwai
2013-05-13 18:24     ` Alex Riesen
2013-05-13 18:24       ` Alex Riesen
2013-05-14  5:59       ` Takashi Iwai
2013-05-14 10:58         ` Takashi Iwai
2013-05-14 19:55           ` Alex Riesen
2013-05-15  5:20             ` Takashi Iwai
2013-05-15 20:17               ` Alex Riesen
2013-05-16 11:00                 ` Takashi Iwai
2013-05-16 20:10                   ` Alex Riesen
2013-05-16 20:10                     ` Alex Riesen
2013-05-17  6:04                     ` Takashi Iwai [this message]
2013-05-18 20:29                       ` Alex Riesen
2013-05-18 20:29                         ` Alex Riesen
2013-05-22 21:06                         ` Alex Riesen
2013-05-23 16:34                           ` Takashi Iwai
2013-05-23 18:38                             ` Alex Riesen
2013-05-24 13:29                         ` Takashi Iwai
2013-05-24 16:36                           ` Alex Riesen
2013-05-24 17:22                             ` Takashi Iwai
2013-05-24 21:32                               ` Alex Riesen
2013-05-29 15:42                                 ` Takashi Iwai
2013-05-31 10:31                                   ` Alex Riesen
2013-05-31 13:05                                     ` Takashi Iwai
2013-05-31 15:32                                       ` Alex Riesen
2013-05-31 18:00                                         ` Takashi Iwai
2013-05-31 19:36                                           ` Alex Riesen
2013-06-03 10:05                                             ` Takashi Iwai
2013-06-03 18:49                                               ` Alex Riesen
2013-06-04  9:48                                                 ` Takashi Iwai
2013-05-14 19:54         ` Alex Riesen

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=s5hk3myuoq6.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raa.lkml@gmail.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.