kernel-packages team mailing list archive

["James M. Leddy" <1183125@xxxxxxxxxxxxxxxxxx>]

The machines that have this as a preinstall are shipping with a dkms,
and as yet I have not seen any requests to fix this in Quantal. If you
would like a Quantal fix, please fill out the sru template.

** Changed in: intel
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1183125

Title:
  Haswell: Ensuring HDA codec pins refer to physical outputs

Status in intel:
  Fix Released
Status in System76:
  Fix Committed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Quantal:
  Won't Fix
Status in “linux” source package in Raring:
  Fix Released

Bug description:
  From David's email:

  http://mailman.alsa-project.org/pipermail/alsa-
  devel/2013-May/062105.html

  The HDA driver assumes that a codec pin widget node always refers to the 
  same physical output. With Haswell, it seems like this is not guaranteed 
  to be true. I would like to see this fixed on the graphics side. If not, 
  I don't know how to work around it on the audio side.

  The problems that occur on the audio side are:

    1) Some BIOSes set default pin config. E g, if the machine has a 
  single HDMI out, it can set two of the codec pins to "not connected" and 
  let the third remain "jack". As a result, the HDA driver will ignore the 
  two codec pins and only enable the third. As such, HDMI audio will not 
  work correctly, unless it's the third codec pin that is connected to the 
  physical output.

    2) Saving and restoring mutes, volumes etc is done on a per-pin basis. 
  E g, imagine that a user has a dual monitor setup and always wants audio 
  output from the left side monitor, and keep the right side monitor 
  silent. If it is not reliable which codec pin refers to which physical 
  output, one day suddenly the sound might come out on the right side 
  monitor instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1183125/+subscriptions