Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <wfg@linux.intel.com>
To: Wang Zhenyu <zhenyu.z.wang@intel.com>
Cc: alsa-devel@alsa-project.org, linux-gfx@linux.intel.com,
	xorg@lists.freedesktop.org
Subject: [PATCH 0/3] enable HDMI audio output for HDMI monitors V2
Date: Fri, 07 Nov 2008 14:23:38 +0800	[thread overview]
Message-ID: <20081107062338.158523355@linux.intel.com> (raw)

Hello,

We can now enjoy music on HDMI monitors that are attached to Intel G35/G45
chipsets with the following X.org intel driver patches

      [PATCH 1/3] introduce i830_hdmi_priv.has_hdmi_sink
      [PATCH 2/3] enable Intel G45 integrated HDMI audio output
      [PATCH 3/3] enable Intel G35 SDVO HDMI audio output

_and_ the corresponding ALSA patch posted at
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-November/012158.html

The patches are tested OK on Intel DG45ID board, HP 2230s notebook and
ASUS P5E-VM board.

Since the HDMI audio requires both audio and video driver support to function
well, I'd like to provide an overview here.

1) driver components:
	A) ALSA: audio driver (the above link)
	B) Xorg: audio output enabling (this patchset)
	C) Xorg: EDID/ELD information (patches to be submitted by Ma Ling)

2) summary of the feature sets:
	- basic 2-channel audio:
		(A) is required, (B) is mostly required, (C) is not needed
	- 2+ multichannel audio:
		not tested yet; in theory we need (C) to get HDMI monitor's
		speaker allocation configuration; there are also bandwidth
		constraints that should be coordinated between audio/video
		drivers in the future.
	- non-LPCM audio:
		not tested yet; need more work in ALSA code.

3) summary of the work flow:
	- basic audio output: (A) and (B)
		- ALSA HDMI driver: enable pin out and unmute
		- ALSA HDMI driver: fill audio infoframe and enable its transmission
		- Xorg intel driver: enable audio output
	- ELD info for advanced audio capabilities: (A) and (C)
		- Xorg xserver: get/parse/store EDID extensions
		- Xorg xserver: transform EDID into ELD
		- Xorg intel driver: feed ELD to hardware
		- Xorg intel driver: set ELD-Valid flag to inform audio driver of new ELD
		- ALSA HDMI driver: response to unsolicited response triggered by ELDV
		- ALSA HDMI driver: get ELD from hardware
		- ALSA HDMI driver: parse and show ELD info
		- ALSA HDMI driver: update hardware capabilities/constraints
				    according to ELD (TBD)

That describes my understandings of HDMI audio, comments and discussions are
warmly welcome.

Thank you,
Fengguang
--

             reply	other threads:[~2008-11-07  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  6:23 Wu Fengguang [this message]
2008-11-07  6:23 ` [PATCH 1/3] introduce i830_hdmi_priv.has_hdmi_sink Wu Fengguang
     [not found]   ` <20081112072747.GD14627@zhen-devel.sh.intel.com>
2008-11-12  8:16     ` Wu Fengguang
2008-11-07  6:23 ` [PATCH 2/3] enable Intel G45 integrated HDMI audio output Wu Fengguang
2008-11-07  6:23 ` [PATCH 3/3] enable Intel G35 SDVO " Wu Fengguang
2008-11-10 18:18 ` [PATCH 0/3] enable HDMI audio output for HDMI monitors V2 Adam Jackson
2008-11-13  2:05 ` Wang, Zhenyu Z

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081107062338.158523355@linux.intel.com \
    --to=wfg@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-gfx@linux.intel.com \
    --cc=xorg@lists.freedesktop.org \
    --cc=zhenyu.z.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox