From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org,
Wang Zhenyu <zhenyu.z.wang@intel.com>,
"intel-gfx@lists.freedesktop..."
<intel-gfx@lists.freedesktop.org>,
dri-devel@lists.freedesktop.org, Ben Skeggs <bskeggs@redhat.com>,
Christopher White <c.white@pulseforce.com>,
Jeremy Bush <contractfrombelow@gmail.com>,
"Bossart, Pierre-louis" <pierre-louis.bossart@intel.com>
Subject: Re: [PATCH v2] pass ELD to HDMI/DP audio driver
Date: Fri, 29 Jul 2011 13:07:59 -0700 [thread overview]
Message-ID: <20110729130759.37aca083@jbarnes-desktop> (raw)
In-Reply-To: <20110629131013.GA10900@localhost>
On Wed, 29 Jun 2011 21:10:13 +0800
Wu Fengguang <fengguang.wu@intel.com> wrote:
> Update: according to the spec, limit max a/v latencies to 500ms and
> avoid overflowing the ELD field Aud_Synch_Delay[7:0].
>
> Thanks to Pierre for pointing this out!
>
> btw, the drm_edid_to_eld() function reuses some code from Ben Skeggs.
> Ben, please add your Signed-off-by if the patch looks OK to you :)
Looks like this needs to be refreshed against Keith's drm-intel-next
tree (some trivial conflicts).
I tested this on a Sandy Bridge laptop I have but wasn't able to get
audio through my DP->HDMI dongle to my HDMI TV.
Does the HDMI HDA codec need any special parameters to work?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-29 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 6:20 [PATCH] pass ELD to HDMI/DP audio driver Wu Fengguang
2011-06-29 6:36 ` Wu Fengguang
2011-06-29 7:00 ` Takashi Iwai
2011-06-29 13:10 ` [PATCH v2] " Wu Fengguang
2011-06-29 23:11 ` Ben Skeggs
2011-07-29 20:07 ` Jesse Barnes [this message]
2011-08-01 13:51 ` [PATCH v3] " Wu Fengguang
2011-08-04 2:48 ` Keith Packard
2011-08-04 9:40 ` Wu Fengguang
2011-08-04 18:03 ` Keith Packard
2011-08-05 12:49 ` Wu Fengguang
2011-08-05 15:52 ` Stephen Warren
2011-08-06 20:02 ` Keith Packard
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=20110729130759.37aca083@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=alsa-devel@alsa-project.org \
--cc=bskeggs@redhat.com \
--cc=c.white@pulseforce.com \
--cc=contractfrombelow@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengguang.wu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pierre-louis.bossart@intel.com \
--cc=zhenyu.z.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