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

Jonathan Woithe jwoithe at just42.net
Sat Jan 5 04:12:54 CET 2013


On Sat, Jan 05, 2013 at 09:31:23AM +0800, Raymond Yau wrote:
> > > > > The driver need pin fixup  for the internal speaker and change the pin
> > > > > default of following node to [N/A]
> > > > >
> > > > > Node 0x13 [Jack] Line In at Sep Right
> > > > > Node 0x17 [Fixed] Aux at Oth Mobile-In
> > > > >
> > > > > -/* Initialisation sequence for ALC260 as configured in Fujitsu S702x
> > > > > - * laptops.  ALC260 pin usage: Mic/Line jack = 0x12, HP jack = 0x14, CD
> > > > > - * audio = 0x16, internal speaker = 0x10.
> > > > > - */
> > > > > -static const struct hda_verb alc260_fujitsu_ini
> > > > >
> > > > > Do the notebook really use node 0x16 CD ?
> > > >
> > > > Yes.  That's where the CD audio comes in.
> > > >
> > >
> > > How about those HP and Mic of the port replicator ?
> >
> > I have no idea: I never purchased the replicator.  In the absence of any
> > other information I would assume the replicator's ports are in parallel with
> > those of the laptop itself.  Unless someone with an S7020 and a replicator
> > turns up it will be impossible to know for sure.
> >
> > > If also affect LIFEBOOK E8020
> > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1091868
> 
> 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
  Node 0x12 = Mic/Line jack on laptop
  Node 0x14 = Headphone jack on laptop
  Node 0x16 = CD audio

In terms of nodes that is all I can be sure of because that's all I can
test.  I have no idea of what the dock does or how its jacks are mapped to
codec nodes because I don't have a dock to test with.

Having said that, I find it operationally odd that the internal speaker
would share a node with a line out jack on the dock.  Then again, it
wouldn't be the first time a laptop manufacturer has done something odd.

I've never fully understood the information provided in the codec proc
file.  In my (very limited) experience the output doesn't always match up
with the reality of the hardware.

Regards
  jonathan


More information about the Alsa-devel mailing list