From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Lin, Mengdong" <mengdong.lin@intel.com>,
David Henningsson <david.henningsson@canonical.com>,
"Yang, Libin" <libin.yang@intel.com>,
Takashi Iwai <tiwai@suse.de>,
"anssi.hannula@iki.fi" <anssi.hannula@iki.fi>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: hda - using POS_FIX_LPIB on Broadwell HDMI Audio
Date: Fri, 09 May 2014 09:58:18 -0500 [thread overview]
Message-ID: <536CED0A.9060902@linux.intel.com> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F82B40F3CB@SHSMSX101.ccr.corp.intel.com>
On 5/9/14, 5:08 AM, Lin, Mengdong wrote:
> Hi,
>
> We found the Broadwell HDMI audio regression is introduced by this patch:
>
> commit dcb32ecd9a533f47ab652c5c5680bc50a7a822cd
> Author: Anssi Hannula <anssi.hannula@iki.fi>
> Date: Tue Apr 8 12:36:42 2014 +0300
> ALSA: hda - Do not assign streams in reverse order
>
> We'll further check the root cause.
> Since this patch seems only affect the stream ID. Actually Intel GPU tool only find the stream ID is changed by this patch.
>
> In addition, Haswell HDMI audio is not affected and works well. It seems there is HW behavior difference between HSW and BDW.
It's unlikely that the wallclock is the issue here. LPIB and wallclock
only make sense for the short link to the GPU, where the data is
reshuffled. It'd look into how the audio data is inserted in the HDMI
frame, the fact that the behavior is linked to a channel order or stream
ID points to GPU-level configuration, not a counter issue at the HDAudio
controller level.
-Pierre
next prev parent reply other threads:[~2014-05-09 14:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 18:03 [PATCH] ALSA: hda - using POS_FIX_LPIB on Broadwell HDMI Audio libin.yang
2014-05-08 5:09 ` Takashi Iwai
2014-05-08 5:48 ` Yang, Libin
2014-05-08 5:51 ` Takashi Iwai
2014-05-08 6:13 ` Yang, Libin
2014-05-08 6:19 ` Takashi Iwai
2014-05-08 6:28 ` Yang, Libin
2014-05-08 6:39 ` Takashi Iwai
2014-05-08 7:58 ` Yang, Libin
2014-05-08 16:06 ` David Henningsson
2014-05-09 10:08 ` Lin, Mengdong
2014-05-09 10:20 ` Takashi Iwai
2014-05-12 8:22 ` Lin, Mengdong
2014-05-12 8:31 ` Takashi Iwai
2014-05-12 9:46 ` Lin, Mengdong
2014-05-12 9:51 ` Takashi Iwai
2014-05-13 4:37 ` Lin, Mengdong
2014-05-13 7:19 ` Takashi Iwai
2014-05-13 9:00 ` Lin, Mengdong
2014-05-09 14:58 ` Pierre-Louis Bossart [this message]
2014-05-08 9:37 ` Lin, Mengdong
2014-05-08 9:42 ` 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=536CED0A.9060902@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=anssi.hannula@iki.fi \
--cc=david.henningsson@canonical.com \
--cc=libin.yang@intel.com \
--cc=mengdong.lin@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 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.