From: Wu Fengguang <wfg@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/4] multi-channel HDMI audio support
Date: Wed, 19 Nov 2008 14:42:16 +0800 [thread overview]
Message-ID: <20081119064216.GA16545@localhost> (raw)
In-Reply-To: <s5hk5b0w76z.wl%tiwai@suse.de>
On Wed, Nov 19, 2008 at 07:39:16AM +0100, Takashi Iwai wrote:
> At Wed, 19 Nov 2008 08:56:14 +0800,
> Wu Fengguang wrote:
> >
> > Hi Takashi,
> >
> > This patchset attempts to support multi-channel HDMI audio.
> >
> > It contains two basic operations:
> >
> > - setup the CA(channel-allocation) byte in the audio infoframe
> > - setup the converter channel to HDMI slot mapping
> >
> > Please read patch 3 for more detailed descriptions:
> >
> > [PATCH 1/4] hda: make standalone hdmi_fill_audio_infoframe()
> > [PATCH 2/4] hda: make global snd_print_channel_allocation()
> > [PATCH 3/4] hda: HDMI channel allocations for audio infoframe
> > [PATCH 4/4] hda: HDMI channel mapping cleanups
> >
> > The current implementation only does minimal works that ensure multi-channel
> > audio playing out. However the wrong speakers may be selected. We could
> > elaborate the framework/policy if it proves to be a problem.
>
> Thanks, applied all patches now.
Thank you, I'll post more cleanups after a while :-)
Regards,
Fengguang
prev parent reply other threads:[~2008-11-19 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 0:56 [PATCH 0/4] multi-channel HDMI audio support Wu Fengguang
2008-11-19 0:56 ` [PATCH 1/4] hda: make standalone hdmi_fill_audio_infoframe() Wu Fengguang
2008-11-19 0:56 ` [PATCH 2/4] hda: make global snd_print_channel_allocation() Wu Fengguang
2008-11-19 0:56 ` [PATCH 3/4] hda: HDMI channel allocations for audio infoframe Wu Fengguang
2008-11-19 0:56 ` [PATCH 4/4] hda: HDMI channel mapping cleanups Wu Fengguang
2008-11-19 6:39 ` [PATCH 0/4] multi-channel HDMI audio support Takashi Iwai
2008-11-19 6:42 ` Wu Fengguang [this message]
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=20081119064216.GA16545@localhost \
--to=wfg@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.