All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: Takashi Iwai <tiwai@suse.de>, Sander Jansen <s.jansen@gmail.com>,
	Christopher White <c.white@pulseforce.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Bossart, Pierre-louis" <pierre-louis.bossart@intel.com>,
	"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
	Jeremy Bush <contractfrombelow@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Intel HDMI ELD fixes
Date: Mon, 28 Nov 2011 16:06:37 +0800	[thread overview]
Message-ID: <20111128080637.GA23173@localhost> (raw)
In-Reply-To: <20111128073337.815008177@intel.com>

> The only missing part is hot plug notification for DP -- most DP monitors in
> the market don't support DP audio well. So I cannot test this for now.

btw, we'd like to buy a Philips 221P3LPYEB that _seems_ to have DP
audio support. I'd appreciate if any one can help confirm.

Thanks,
Fengguang

  parent reply	other threads:[~2011-11-28  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  7:33 [PATCH 0/4] Intel HDMI ELD fixes Wu Fengguang
2011-11-28  7:33 ` Wu Fengguang
2011-11-28  7:33 ` [PATCH 1/4] drm/i915: fix ELD writing for SandyBridge Wu Fengguang
2011-11-28  7:33   ` Wu Fengguang
2011-11-29 11:53   ` [PATCH 1/4 v2] " Wu Fengguang
2011-11-28  7:33 ` [PATCH 2/4] drm/i915: rename audio ELD registers Wu Fengguang
2011-11-28  7:33   ` Wu Fengguang
2011-11-29 11:54   ` [PATCH 2/4 v2] " Wu Fengguang
2011-11-28  7:33 ` [PATCH 3/4] drm/i915: dont trigger hotplug events on unchanged ELD Wu Fengguang
2011-11-28  7:33   ` Wu Fengguang
2011-11-28  7:33 ` [PATCH 4/4] drm/i915: HDMI hot remove notification to audio driver Wu Fengguang
2011-11-28  7:33   ` Wu Fengguang
2011-11-28  8:06 ` Wu Fengguang [this message]
2011-12-09 13:12   ` Philips 221P3LPYEB has working DP audio 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=20111128080637.GA23173@localhost \
    --to=fengguang.wu@intel.com \
    --cc=c.white@pulseforce.com \
    --cc=contractfrombelow@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@intel.com \
    --cc=s.jansen@gmail.com \
    --cc=tiwai@suse.de \
    --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 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.