From: Wang Xingchao <xingchao.wang@intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, anssi.hannula@iki.fi, alanwww1@xbmc.org,
fengguang.wu@intel.com, Wang Xingchao <xingchao.wang@intel.com>
Subject: [PATCH 0/3] HDMI HBR(High Bit Rate) Feature bug fix for Intel's Chips
Date: Thu, 6 Sep 2012 10:02:35 +0800 [thread overview]
Message-ID: <1346896958-21080-1-git-send-email-xingchao.wang@intel.com> (raw)
As i have no A/V receiver handy and could not test HBR playback directly, i
removed the "RFC" type until the patchset was tested and proved working well.
The patchset was tested on Intel chips and get positive feedback.
Quote from "Øyvind Kvålsvoll <oyvind@kvalsvoll.com>":
"TrueHD and DTS-MA work fine from XBMC, 2-ch playback also works fine
from XBMC.
Channels are all mapped to the right speaker, all 7.1."
Quote from alanwww1:
"I tested the patches. They work perfectly. I tested it with both DTS Master
Audio and Dolby Tru HD streams.
Also tested with speaker-test. Channel mapping was right."
From: http://forum.xbmc.org/showthread.php?tid=128298&pid=1184574#pid1184574
Maybe there's still potential bug and i will keep on track that.
The idea of this patch comes from Anssi, Big credit to him at first!
Thanks the guys from XBMC forum which help test the patches.
For people interested to test the patch, please remember to apply another change in
alsa-lib side, you can refer to the patch detail from XBMC forum:
http://forum.xbmc.org/showthread.php?tid=128298&pid=1178776#pid1178776
I will send that patch to alsa-lib mail-list later.
Changelog:
* do not touch channel_allocation priority order, use new api to get
correct channels number
* use spdif->status to check audio type, pcm or non-pcm
* create new non_pcm_mapping[] for non_pcm audio in seperate block
* add non_pcm hdmi_spec_per_cvt to remember previous audio type, used to
determine whether need a channel mapping update during the pcm/non-pcm
stream switch with same channel number.
Wang Xingchao (3):
ALSA: HDMI - Fix channel_allocation array wrong order
ALSA: HDMI - Enable HBR feature on Intel chips
ALSA: HDMI - Setup channel mapping for non_pcm audio
sound/pci/hda/patch_hdmi.c | 56 ++++++++++++++++++++++++++++++++++++++++----
1 file changed, 51 insertions(+), 5 deletions(-)
--
1.7.9.5
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2012-09-06 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 2:02 Wang Xingchao [this message]
2012-09-06 2:02 ` [PATCH 1/3] ALSA: HDMI - Fix channel_allocation array wrong order Wang Xingchao
2012-09-06 2:02 ` [PATCH 2/3] ALSA: HDMI - Enable HBR feature on Intel chips Wang Xingchao
2012-09-06 2:02 ` [PATCH 3/3] ALSA: HDMI - Setup channel mapping for non_pcm audio Wang Xingchao
2012-09-06 6:53 ` [PATCH 0/3] HDMI HBR(High Bit Rate) Feature bug fix for Intel's Chips Takashi Iwai
2012-09-06 16:00 ` Takashi Iwai
2012-09-07 1:32 ` Wang, Xingchao
-- strict thread matches above, loose matches on Subject: below --
2012-09-05 5:58 Wang Xingchao
2012-09-05 6:30 ` Takashi Iwai
2012-09-05 6:34 ` Wang Xingchao
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=1346896958-21080-1-git-send-email-xingchao.wang@intel.com \
--to=xingchao.wang@intel.com \
--cc=alanwww1@xbmc.org \
--cc=alsa-devel@alsa-project.org \
--cc=anssi.hannula@iki.fi \
--cc=fengguang.wu@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).