From: Takashi Iwai <tiwai@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/4] updates for Intel SandyBridge/CougarPoint HDMI codec V2
Date: Mon, 17 May 2010 08:15:28 +0200 [thread overview]
Message-ID: <s5hzkzzt5of.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100514083611.624260274@intel.com>
At Fri, 14 May 2010 16:36:11 +0800,
Wu Fengguang wrote:
>
> Hi Takashi,
>
> The Intel SandyBridge/CougarPoint HDMI codec is very similar to the
> IbexPeak HDMI codec, except that it exports one more Audio Converter.
>
> Now we have 3 Audio Converters, each of them present one HDMI PCM device:
> (and expect a 4th HDMI PCM device in future)
>
> $ aplay -l | grep HDMI
> card 0: PCH [HDA Intel PCH], device 3: INTEL HDMI 0 [INTEL HDMI 0]
> card 0: PCH [HDA Intel PCH], device 7: INTEL HDMI 1 [INTEL HDMI 1]
> card 0: PCH [HDA Intel PCH], device 8: INTEL HDMI 2 [INTEL HDMI 2]
>
> So enable devices minors to support more than 8 PCM playback devices.
Applied all patches now. Thanks.
Takashi
prev parent reply other threads:[~2010-05-17 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 8:36 [PATCH 0/4] updates for Intel SandyBridge/CougarPoint HDMI codec V2 Wu Fengguang
2010-05-14 8:36 ` [PATCH 1/4] intelhdmi - add dependency on SND_DYNAMIC_MINORS Wu Fengguang
2010-05-14 8:36 ` [PATCH 2/4] intelhdmi - user friendly codec name Wu Fengguang
2010-05-14 8:36 ` [PATCH 3/4] intelhdmi - add id for the CougarPoint chipset Wu Fengguang
2010-05-14 8:36 ` [PATCH 4/4] hdmi - dont fail on extra nodes Wu Fengguang
2010-05-17 6:15 ` Takashi Iwai [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=s5hzkzzt5of.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@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;
as well as URLs for NNTP newsgroup(s).