From: Fengguang Wu <fengguang.wu@intel.com>
To: Wang Xingchao <xingchao.wang@intel.com>
Cc: michael.fu@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH V2 1/2] intel_audio_dump: fix wrong port definition
Date: Wed, 15 Aug 2012 15:56:37 +0800 [thread overview]
Message-ID: <20120815075637.GA28901@localhost> (raw)
In-Reply-To: <1344329570-17939-2-git-send-email-xingchao.wang@intel.com>
Thanks for catching this!
Acked-by: Fengguang Wu <fengguang.wu@intel.com>
On Tue, Aug 07, 2012 at 04:52:49PM +0800, Wang Xingchao wrote:
> There're three Ports B/C/D used for selection by each transcoder A/B/C.
>
> Signed-off-by: Wang Xingchao <xingchao.wang@intel.com>
> ---
> tools/intel_audio_dump.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/intel_audio_dump.c b/tools/intel_audio_dump.c
> index 077e096..8a0f6ee 100644
> --- a/tools/intel_audio_dump.c
> +++ b/tools/intel_audio_dump.c
> @@ -126,9 +126,9 @@ static const char *video_dip_trans[] = {
> static const char *trans_to_port_sel[] = {
> [0] = "no port",
> [1] = "Digital Port B",
> - [2] = "Digital Port B",
> - [3] = "Digital Port B",
> - [4] = "Digital Port B",
> + [2] = "Digital Port C",
> + [3] = "Digital Port D",
> + [4] = "reserved",
> [5] = "reserved",
> [6] = "reserved",
> [7] = "reserved",
> --
> 1.7.9.5
next prev parent reply other threads:[~2012-08-15 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 8:52 [PATCH 0/2] Haswell intel_audio_dump support Wang Xingchao
2012-08-07 8:52 ` [PATCH V2 1/2] intel_audio_dump: fix wrong port definition Wang Xingchao
2012-08-15 7:56 ` Fengguang Wu [this message]
2012-08-07 8:52 ` [PATCH V2 2/2] intel_audio_dump: add Haswell audio dump support Wang Xingchao
2012-08-15 8:00 ` Fengguang Wu
2012-08-15 8:05 ` Wang, Xingchao
2012-08-15 7:51 ` [PATCH 0/2] Haswell intel_audio_dump support 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=20120815075637.GA28901@localhost \
--to=fengguang.wu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michael.fu@intel.com \
--cc=xingchao.wang@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