From: Wu Fengguang <fengguang.wu@intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
"intel-gfx@lists.freedesktop..."
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Zhao, Yakui" <yakui.zhao@intel.com>,
Ben Skeggs <bskeggs@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Christopher White <c.white@pulseforce.com>,
Jeremy Bush <contractfrombelow@gmail.com>,
"Fu, Michael" <michael.fu@intel.com>,
"Bossart, Pierre-louis" <pierre-louis.bossart@intel.com>
Subject: Re: [PATCH v4] drm/i915: pass ELD to HDMI/DP audio driver
Date: Fri, 2 Sep 2011 16:29:26 +0800 [thread overview]
Message-ID: <20110902082926.GA19820@localhost> (raw)
In-Reply-To: <20110902081428.GA19621@localhost>
Keith: this version completes the IvyBridge support :)
Bossart: hotplug is working fine now, with some minor issues:
- on G45, monitor hot removal is not handled at all in
i915_driver_irq_handler(). I'll leave it as a future TODO.
- on IvyBridge, _repeated_ plug/unplug will trigger
[ 1183.654859] ALSA hda_eld.c:259 HDMI: Unknown ELD version 0
which means the ELD_valid flag will be seen by audio driver,
however it cannot get any valid ELD data. I double checked and
find everything in the graphics driver is working as expected:
ironlake_write_eld() is writing the good ELD data to the same
pipe on hot plug events. So I'll leave it as a possible bug of
the early stage hardware.
Thanks,
Fengguang
next prev parent reply other threads:[~2011-09-02 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 8:14 [PATCH v4] drm/i915: pass ELD to HDMI/DP audio driver Wu Fengguang
2011-09-02 8:29 ` Wu Fengguang [this message]
2011-09-03 21:15 ` [PATCH v5] " Wu Fengguang
2011-09-04 10:57 ` James Cloos
2011-09-05 1:19 ` Wu Fengguang
2011-09-04 11:11 ` [Intel-gfx] " Paul Menzel
2011-09-05 1:06 ` Wu Fengguang
2011-09-04 12:08 ` Chris Wilson
2011-09-05 1:14 ` Wu Fengguang
2011-09-05 11:04 ` Chris Wilson
2011-09-05 12:31 ` Wu Fengguang
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=20110902082926.GA19820@localhost \
--to=fengguang.wu@intel.com \
--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=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=michael.fu@intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=yakui.zhao@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