[alsa-devel] [PATCH] ALSA: hda - delay resume haswell hdmi codec in system resume
mengdong.lin at intel.com
Mon May 6 11:48:59 CEST 2013
> -----Original Message-----
> From: alsa-devel-bounces at alsa-project.org
> [mailto:alsa-devel-bounces at alsa-project.org] On Behalf Of David Henningsson
> Sent: Monday, May 06, 2013 3:08 PM
> To: Lin, Mengdong
> Cc: Takashi Iwai; Li, Jocelyn; alsa-devel at alsa-project.org; Girdwood, Liam R;
> Wang, Xingchao
> Subject: Re: [alsa-devel] [PATCH] ALSA: hda - delay resume haswell hdmi codec
> in system resume
> The core of the problem is that the DDI port can sometimes be connected to a
> transcoder that in turn is connected to an audio codec pin which default pin
> config is set to "not connected". In this case, audio will not work correctly. (It
> might sometimes work by accident.)
> The solution is that DDI to transcoder connection cannot change, it must always
> be connected to the audio codec pin which is marked as "jack".
The gfx driver will decide which pipe is used for a DDI port. And the connection can change by hot plug events.
The gfx driver will always try to use the 1st pipe if it's free, because the 1st pipe is not affected by the power down well.
Thus the user can get display while the other parts are turned off for power saving.
I think if everything is properly configured, the pin to DDI port mapping should not change even if the port is connected to a different transcoder.
There may be something wrong or missing in current audio or gfx driver.
> Btw, even if all audio codec pins are marked as "jack", it would be a bad habit to
> change the connection, because people will be confused when we show these
> pins to the user as e g "HDMI 1", "HDMI 2" and "HDMI 3", and which one is
> corresponding to the physical output is varying.
Yes. This would confuse users.
More information about the Alsa-devel