Re: regression: from 3.8 to 3.9: headphones output no sound on IntelHDA, codec VIA VT1802

[Alex Riesen]

On Tue, May 14, 2013 at 7:59 AM, Takashi Iwai <tiwai@xxxxxxx> wrote:
>> > Also, what happens if you apply the patch below?
>> > -       spec->set_widgets_power_state =  set_widgets_power_state_vt2002P;
>> > +       //spec->set_widgets_power_state =  set_widgets_power_state_vt2002P;
>>
>> This helps as well. Yay!
>> Thanks :) Whatever the outcome, I have them back more or less (more,
>> for me) properly.
>
> OK, then we know the place to fix now.
> Try the patch below instead.  Does it fix the problem as well?

Sadly, no. Now there is no headphone output at all. Not even to the
alternate PCM.

>> Probably unrelated, but I better mention it anyway: the "Auto-Mute Mode"
>> works strangely, it never mutes anything but headphones. It might work
>> as designed, but it is useless in this case: one still has to mute the
>> speaker manually when plugging headphones (or do something with input
>> events, which I failed to get to work).
>
> Does the problem still happen with the patch?
>

Well... Kind of no. As I said, there is no headphone output, BUT the laptop
built-in speakers ARE muted when the headphones plugged in.

>> And "Independent HP" has absolutely no effect, which is probably as it
>> should be on this laptop.
>
> With the independent HP turned on, there should be no output to the
> headphone through the normal PCM.  There is a secondary PCM device,
> and this is routed to the headphone when the independent HP is on.

Ah. I misunderstood (miscounted?) the playback PCMs: this card has three
(VT1802 Analog, VT1802 Alt Analog and ID 2806 Digital), the last one being
HDMI (just deconfigured, while I was trying to figure the headphones out).
The first two named appropriately (if one looks at them), and when tried
(hw:0,2. Strangely, there is no hw:0,1) it indeed works (with the revised
patch. Not with this one).

Regards,
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/