From: Wu Fengguang <fengguang.wu@intel.com>
To: Nick Bowler <nbowler@elliptictech.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Keith Packard <keithp@keithp.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2-rc1
Date: Thu, 10 Nov 2011 19:57:12 +0800 [thread overview]
Message-ID: <20111110115712.GA6492@localhost> (raw)
In-Reply-To: <s5hty6dlp5o.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Nick,
On Wed, Nov 09, 2011 at 03:40:19PM +0800, Takashi Iwai wrote:
> At Tue, 8 Nov 2011 12:23:30 -0800,
> Linus Torvalds wrote:
> >
> > Hmm, I don't know what caused this to trigger, but I'm adding both the
> > i915 people and the HDA people to the cc, and they can fight to the
> > death about this in the HDMI Thunderdome.
>
> It must be the new addition of ELD-passing code.
>
> Fengguang, can the drm or i915 driver check whether ELD is changed or
> not? Writing ELD at each time even when unchanged confuses the audio
> side, as if the monitor is hotplugged.
The attached patch is tested OK to prevent extra hot plug events.
However it has one side effect: when HDMI monitor is hot removed,
the ELD keeps remain valid. I need to find a way to test for the
presence of the monitor and handle that case as well. When all done,
I'll submit the patches together for review.
Thanks,
Fengguang
[-- Attachment #2: no-extra-eld-passing --]
[-- Type: text/plain, Size: 2661 bytes --]
Subject: drm/i915: don't trigger hotplug events on unchanged ELD
Date: Thu Nov 10 17:48:49 CST 2011
The ELD may or may not change when switching the video mode.
If unchanged, don't trigger hot plug events to HDMI audio driver.
This avoids disturbing the user with repeated printks.
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
drivers/gpu/drm/i915/intel_display.c | 51 ++++++++++++++++++++++---
1 file changed, 46 insertions(+), 5 deletions(-)
--- linux.orig/drivers/gpu/drm/i915/intel_display.c 2011-11-10 17:23:04.000000000 +0800
+++ linux/drivers/gpu/drm/i915/intel_display.c 2011-11-10 17:59:25.000000000 +0800
@@ -5811,6 +5811,35 @@ static int intel_crtc_mode_set(struct dr
return ret;
}
+static bool intel_eld_uptodate(struct drm_connector *connector,
+ int reg_eldv, uint32_t bits_eldv,
+ int reg_elda, uint32_t bits_elda,
+ int reg_edid)
+{
+ struct drm_i915_private *dev_priv = connector->dev->dev_private;
+ uint8_t *eld = connector->eld;
+ uint32_t i;
+
+ i = I915_READ(reg_eldv);
+ i &= bits_eldv;
+
+ if (!eld[0])
+ return !i;
+
+ if (!i)
+ return false;
+
+ i = I915_READ(reg_elda);
+ i &= ~bits_elda;
+ I915_WRITE(reg_elda, i);
+
+ for (i = 0; i < eld[2]; i++)
+ if (I915_READ(reg_edid) != *((uint32_t *)eld + i))
+ return false;
+
+ return true;
+}
+
static void g4x_write_eld(struct drm_connector *connector,
struct drm_crtc *crtc)
{
@@ -5827,6 +5856,12 @@ static void g4x_write_eld(struct drm_con
else
eldv = G4X_ELDV_DEVCTG;
+ if (intel_eld_uptodate(connector,
+ G4X_AUD_CNTL_ST, eldv,
+ G4X_AUD_CNTL_ST, G4X_ELD_ADDR,
+ G4X_HDMIW_HDMIEDID))
+ return;
+
i = I915_READ(G4X_AUD_CNTL_ST);
i &= ~(eldv | G4X_ELD_ADDR);
len = (i >> 9) & 0x1f; /* ELD buffer size */
@@ -5886,6 +5921,17 @@ static void ironlake_write_eld(struct dr
eldv = GEN5_ELD_VALIDB << ((i - 1) * 4);
}
+ if (intel_pipe_has_type(crtc, INTEL_OUTPUT_DISPLAYPORT)) {
+ DRM_DEBUG_DRIVER("ELD: DisplayPort detected\n");
+ eld[5] |= (1 << 2); /* Conn_Type, 0x1 = DisplayPort */
+ }
+
+ if (intel_eld_uptodate(connector,
+ aud_cntrl_st2, eldv,
+ aud_cntl_st, GEN5_ELD_ADDRESS,
+ hdmiw_hdmiedid))
+ return;
+
i = I915_READ(aud_cntrl_st2);
i &= ~eldv;
I915_WRITE(aud_cntrl_st2, i);
@@ -5893,11 +5939,6 @@ static void ironlake_write_eld(struct dr
if (!eld[0])
return;
- if (intel_pipe_has_type(crtc, INTEL_OUTPUT_DISPLAYPORT)) {
- DRM_DEBUG_DRIVER("ELD: DisplayPort detected\n");
- eld[5] |= (1 << 2); /* Conn_Type, 0x1 = DisplayPort */
- }
-
i = I915_READ(aud_cntl_st);
i &= ~GEN5_ELD_ADDRESS;
I915_WRITE(aud_cntl_st, i);
next prev parent reply other threads:[~2011-11-10 11:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 2:10 Linux 3.2-rc1 Linus Torvalds
2011-11-08 3:12 ` Al Viro
2011-11-08 4:26 ` Linus Torvalds
2011-11-08 10:52 ` Geert Uytterhoeven
2011-11-08 6:50 ` Nicholas A. Bellinger
2011-11-08 13:43 ` Udo Steinberg
2011-11-08 14:47 ` Ming Lei
2011-11-08 22:10 ` Rafael J. Wysocki
2011-11-08 14:53 ` Alessandro Suardi
2011-11-08 20:13 ` Linus Torvalds
2011-11-08 20:15 ` Matthew Garrett
2011-11-08 20:44 ` Linus Torvalds
2011-11-08 14:55 ` Nick Bowler
2011-11-08 20:23 ` Linus Torvalds
2011-11-09 7:40 ` Takashi Iwai
2011-11-09 12:03 ` Wu Fengguang
2011-11-10 11:57 ` Wu Fengguang [this message]
2011-11-08 19:06 ` Thomas Bächler
2011-11-08 23:00 ` Steven Rostedt
2011-11-08 23:53 ` Linus Torvalds
2011-11-09 8:09 ` Borislav Petkov
2011-11-09 13:11 ` Valdis.Kletnieks
2011-11-09 14:20 ` Paul Rolland
2011-11-09 23:23 ` Linus Torvalds
2011-11-09 17:18 ` Randy Dunlap
2011-11-09 17:28 ` Josh Boyer
2011-11-22 1:41 ` Boaz Harrosh
2011-11-22 16:10 ` Josh Boyer
2011-11-22 18:05 ` Alan Cox
2011-11-22 18:29 ` Boaz Harrosh
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=20111110115712.GA6492@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
/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