alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: alsa-devel@alsa-project.org, 881826@bugs.launchpad.net
Subject: Re: [RFC] Fix for conflict of HDMI and SPDIF IEC958 controls
Date: Mon, 15 Oct 2012 15:20:45 +0200	[thread overview]
Message-ID: <s5hipabswgi.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAN8cciakmCAfwh_z8uRRmx=QyJDyWQw6upwDG_tJGu-5zkn6wg@mail.gmail.com>

At Mon, 15 Oct 2012 21:10:44 +0800,
Raymond Yau wrote:
> 
> > > > > > >
> > > > > > > how about those hdmi jack and iec958 on ad1989b?
> > > > > >
> > > > > > On AD codecs, all digital outputs are exposed as a single cloned
> > > > > > device with HDA_PCM_TYPE_SPDIF.
> > > > >
> > > > > how about ad1988b with nvidia codec ?
> > > >
> > > > Nvidia codec provides devices only with HDA_PCM_TYPE_HDMI, of course.
> > > >
> > > > > from user point of view , how can they differenitate hdmi jack is
> > > digital
> > > > > ouput and hdmi output ?
> > > >
> > > > The device 1 is from AD and the device 3 is from Nvidia codec, as you
> > > > can see below.  And this is exactly the case the conflict happens as I
> > > > mentioned in the original mail.
> > >
> > > will your fix change the spdif of  those motherboard with ad1988b which
> > > have iec958 but no hdmi jack ?
> >
> > It won't change anything unless both SPDIF and HDMI *devices* are
> > actually created.
> >
> >
> >
> > > > Which is connected to what output, you can't know exactly unless you
> > > > compare the obtained ELD.  The HD-audio spec isn't good enough to
> > > > identify the actual output.
> > >
> > > it seem that there is no presence detect on this codec
> >
> > ELD has nothing to do with the presence detect bit.
> >
> 
> ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html#_examples
> 
> 6.1.2. Chipset with 8-channel support, single stream
> 
> This configuration is used in MCP77, MCP78, MCP79, MCP7A, and ION.
> 
> In the case where multiple HDMI display connectors are present, the audio
> stream is broadcast to all HDMI connectors at once. A single ALSA device is
> exposed.
> 
> ELD and PD information is not available on these chipsets.
> 
> In these chipsets, the multiple 2-channel converters are aggregated by the
> ALSA driver and exposed as a single 8-channel device. Some chipsets support
> 2, or 8 channels (MCP77). Other chipsets support 2, 6, or 8 channels
> (MCP79).
> 
> id = 0x10de0002, .name = "MCP77/78 HDMI",    .patch = patch_nvhdmi_8ch_7x },
> 
> does it mean that this hdmi codec support 8 channels but no ELD info ?

Right.


Takashi

  reply	other threads:[~2012-10-15 13:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 15:18 [RFC] Fix for conflict of HDMI and SPDIF IEC958 controls Takashi Iwai
2012-10-12 15:24 ` [PATCH RFC] ALSA: hda - Add workaround for conflicting " Takashi Iwai
2012-10-17  8:17   ` Takashi Iwai
2012-10-17 12:43     ` Raymond Yau
2012-10-17 12:44       ` Takashi Iwai
2013-02-08 22:44   ` [PATCH] ALSA: hda - Fix the " Anssi Hannula
2013-02-10 10:38     ` Takashi Iwai
2013-02-10 11:05       ` Anssi Hannula
2013-02-11 10:51         ` Takashi Iwai
2013-02-11 11:20           ` Anssi Hannula
2013-02-11 11:28             ` Takashi Iwai
2013-02-12 15:51               ` Anssi Hannula
2013-02-12 17:40                 ` Takashi Iwai
2012-10-12 15:25 ` [PATCH RFC 1/2] control: Simplify using snd_config_get_bool() Takashi Iwai
2012-10-12 15:25 ` [PATCH RFC 2/2] Add workaround for conflicting IEC958 controls for HD-audio Takashi Iwai
2013-02-03 16:40   ` Anssi Hannula
2013-02-04  9:34     ` Takashi Iwai
2012-10-15  2:31 ` [RFC] Fix for conflict of HDMI and SPDIF IEC958 controls Raymond Yau
2012-10-15  7:46   ` Takashi Iwai
2012-10-15  8:15     ` Raymond Yau
2012-10-15  8:35       ` Takashi Iwai
2012-10-15  8:49         ` Raymond Yau
2012-10-15  8:55           ` Takashi Iwai
     [not found]             ` <CAN8ccib4Z9VpHcdGxP3q5kofikU6zt6risGDAbOBiRKyKVcsxA@mail.gmail.com>
     [not found]               ` <CAN8cciY0TfZ+50EuoYbFdz1AzgNuDKZAaDE-o0v-YD_MpXnO1g@mail.gmail.com>
2012-10-15 13:10                 ` Raymond Yau
2012-10-15 13:20                   ` Takashi Iwai [this message]
2012-10-15 10:09 ` David Henningsson
2012-10-15 10:18   ` Takashi Iwai
2012-10-15 10:58     ` David Henningsson
2012-10-15 10:21 ` Jaroslav Kysela
2012-10-15 10:31   ` Takashi Iwai
2012-10-15 11:11     ` Jaroslav Kysela
2012-10-15 12:06       ` Takashi Iwai

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=s5hipabswgi.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=881826@bugs.launchpad.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.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).