[alsa-devel] HDA regression on Fujitsu S7020 laptop (ALC260 codec)

Jonathan Woithe jwoithe at just42.net
Sat Jan 5 08:16:05 CET 2013

On Sat, Jan 05, 2013 at 02:32:38PM +0800, Raymond Yau wrote:
> > > Does this mean that the internal speaker and line out at Sep right (dock
> > > line out) at same node 0x10 ?
> >
> > Here is what I know:
> >
> >   Node 0x10 = Internal speaker
> -static const struct hda_verb alc260_fujitsu_init_verbs[] = {
> -       /* Disable all GPIOs */
> -       {0x01, AC_VERB_SET_GPIO_MASK, 0},
> -       /* Internal speaker is connected to headphone pin */
> The auto model won't set pin ctls to HP when pin default is line out or
> speaker
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1091868/comments/9

Do you require feedback from me about this?  As far as I can tell it's just
an observation which might partly explain why the speaker doesn't work on
the S7020.

In case it helps clarify things, perhaps I should explain some of the
comments which were previously contained within alc260_quirks.c (since I
wrote them).

  /* Internal speaker is connected to headphone pin */

Node 0x10 is notionally labelled "headphone pin" in the ALC260 datasheet. 
However, on the S7020 it is instead electrically connected to the internal

  /* Headphone/Line-out jack connects to Line1 pin; make it an output */

Node 0x14 is described as "Line1 pin" in the ALC260 datasheet.  On the S7020
the designers have chosen to connect it to the headphone/line-out jack on
the laptop.

  /* Mic/Line-in jack is connected to mic1 pin, so make it an input */

This is perhaps the only consistent pin on the laptop.  The "mic1" pin of
the ALC260 is conected to the "Mic/Line-in" hack on the laptop.

In other words, on this particular laptop (and probably many others) the
designers have been fairly free when connecting pins to physical entities.

> Refer to your 3.3.5 info

What for, exactly?  Sorry, I'm confused as to what you're asking for here.

> Does auto mute work in kernel 3.3.5 since unsolicited event is not enabled ?

No idea - I have no interest in using auto-mute and have never had the
inclination to test it or look into it.

I've just looked now.  3.3.5 was booted, alsamixer does not show any
"automute" control to enable or disable this.  In any case, automute is
certainly not happening, so I'm guessing the answer to your question is no.


More information about the Alsa-devel mailing list