From: Wu Fengguang <fengguang.wu@intel.com>
To: alsa-user@lists.sourceforge.net, intel-gfx@lists.freedesktop.org,
shane-alsa@csy.ca, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: [Intel-gfx] Problems with HDMI audio on Intel DG45FC motherboard
Date: Wed, 21 Oct 2009 09:38:12 +0800 [thread overview]
Message-ID: <20091021013812.GB7279@localhost> (raw)
In-Reply-To: <20091020223758.GA31022@hardeman.nu>
On Wed, Oct 21, 2009 at 06:37:58AM +0800, David Härdeman wrote:
> On Tue, Oct 20, 2009 at 09:26:00AM +0800, Wu Fengguang wrote:
> >On Thu, Oct 15, 2009 at 01:40:53AM +0800, David Härdeman wrote:
> >> ii) Is there any documentation somewhere on how this mapping is supposed
> >> to be performed in user space?
> >
> >I think Shane has provided a good example for you in another email :)
> >Here are more descriptions for the route plugin:
>
> So perhaps I should still file a bug with the ALSA bugtracker asking for
> the default ALSA userspace to include a channel mapping along Shane's
> recommendation?
That would be good. I'm not sure if PulseAudio need a separate fix.
(Lennart CCed).
> >> >Complete silence for how much time?
> >>
> >> For the entire duration of the particular movie/audio track/video
> >> clip/whatever.
> >>
> >
> >I actually have a DG45FC box and have not run into this problem for
> >all the HDMI monitors I have. What's your monitor model?
>
> A Samsung LE-55A956 LCD TV. But I think the problem is not with the
> monitor (TV) but rather with the receiver that is between the DG45FC and
> the TV. The receiver is a Marantz SR8002 with HDMI support.
Got it. If you have a HDMI capable TV or monitor, it would be possible to get
rid of the Marantz and check if the problem sticks :)
> >Did the kernel emit some error messages?
>
> Nope
OK. You can get more debug info if turning on
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_VERBOSE=y
CONFIG_SND_PCM_XRUN_DEBUG=y
> >What if you change display
> >modes with xrandr?
>
> Haven't tried that yet...currently running on 1920x1080@60 which should
> (I guess) be one of the most common modes with modern LCD TV's.
The infoframe would be different for 2-channel pure music and 5.1 channel
movie. The video timing might also affect audio stream, because the HDMI
audio data is transfered in the gaps of video data.
> >HDMI codec/sink seem to take some time to response to the output
> >enable and new infoframe, so there are some delay. I've moved the HDMI
> >output enable command to module load time, this helps. The infoframe
> >is in theory created in run time based on the format of _each_ new
> >audio stream, so infoframe transmission has to be started/stopped
> >for each track..
>
> So my current theory is along the line of HDMI audio infoframe or video
> infoframe problems. Do you have any pointers where in the driver(s)
> the infoframes (both audio and video) are generated so that I can add
> some debugging statements to dump the frames and compare the working
> and non-working scenarios?
I guess the infoframe itself should be identical for the same clip.
Have you tried upgrading to a recent Xorg/intel gfx driver?
Anyway, the kernel driver code is linux/sound/pci/hda/patch_intelhdmi.c
The relevant function is hdmi_setup_audio_infoframe(). Inside which the
hdmi_setup_channel_mapping() is not functioning for G45,
hdmi_setup_channel_allocation() is no-op for 2-channel music.
hdmi_debug_dip_size() and hdmi_clear_dip_buffers() can also be commented out.
And feel free to ask more questions :)
Thanks,
Fengguang
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-10-21 1:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091011214513.GB12771@hardeman.nu>
[not found] ` <20091014015455.GI13364@zhen-devel.sh.intel.com>
[not found] ` <20091014020044.GA10032@localhost>
[not found] ` <20091014174053.GA31149@hardeman.nu>
2009-10-20 1:26 ` [Intel-gfx] Problems with HDMI audio on Intel DG45FC motherboard Wu Fengguang
2009-10-20 22:37 ` David Härdeman
2009-10-21 1:38 ` Wu Fengguang [this message]
2009-10-25 22:31 ` David Härdeman
2009-10-27 8:57 ` Wu Fengguang
2009-11-08 10:41 ` Takashi Iwai
2009-10-20 22:43 ` Shane W
2009-10-26 23:11 ` David Härdeman
2009-10-27 9:08 ` Wu Fengguang
2009-10-27 3:28 ` Wu Fengguang
[not found] ` <2da93e57183a480510f5b67c24ba11d0.squirrel@www.hardeman.nu>
[not found] ` <20091028044621.GA18453@localhost>
[not found] ` <0323437dc2fc33a33ec9285505a36434.squirrel@www.hardeman.nu>
[not found] ` <20091029094602.GA3589@localhost>
[not found] ` <20091029222932.GA1109@hardeman.nu>
2009-11-02 9:11 ` Wu Fengguang
[not found] ` <20091105004655.GA25580@hardeman.nu>
[not found] ` <20091105074731.GB3016@localhost>
[not found] ` <b3e8c2bfd1e1ff82a1e68a4e03950238.squirrel@www.hardeman.nu>
2009-11-05 9:22 ` Wu Fengguang
[not found] ` <5a703067d8395f3f80e4fb6a5227d117.squirrel@www.hardeman.nu>
2009-11-11 7:05 ` Wu Fengguang
2009-11-12 9:49 ` Paul Fertser
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=20091021013812.GB7279@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mznyfn@0pointer.de \
--cc=shane-alsa@csy.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox