All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: [PATCH 0/4] sdvo hdmi regression fix and related cleanups
Date: Tue, 10 Apr 2012 13:55:45 +0200	[thread overview]
Message-ID: <1334058949-5633-1-git-send-email-daniel.vetter@ffwll.ch> (raw)

Hi all,

The first patch in this series fixes a long-standing hdmi-on-sdvo regression -
we apparently have not set up the pixel doubling (or quadrupling) correctly.
This regression was introduced in 2.6.36. Now if this patch is indeed correct,
hdmi on sdvo (and _only_ hdmi) for any pixelclock below 100 MHz should have been
broken since then. But we seem to have a decent lack of regression reports,
which is why I'm a bit uneasy with this patch.

So review, comments and especially testing (and tested-by gathering) on the
first patch highly welcome. I'd like to include this into -fixes for 3.4, but if
the testing/review on that patch is lacking, I'll postpone it for -next - it's
been broken for way too long anyway :(

The other patches are just clarifications and paranoia-checks for -next.

Yours, Daniel

Daniel Vetter (4):
  drm/i915: handle input/output sdvo timings separately in mode_set
  drm/i915: clarify preferred sdvo input mode code
  drm/i915: don't silently ignore sdvo mode_set failures
  drm/i915: debug messge for lossy sdvo dtd -> drm mode conversion

 drivers/gpu/drm/i915/intel_sdvo.c |   74 +++++++++++++++++++++---------------
 1 files changed, 43 insertions(+), 31 deletions(-)

-- 
1.7.9.1

             reply	other threads:[~2012-04-10 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 11:55 Daniel Vetter [this message]
2012-04-10 11:55 ` [PATCH 1/4] drm/i915: handle input/output sdvo timings separately in mode_set Daniel Vetter
2012-04-10 16:17   ` Jesse Barnes
2012-04-10 16:36     ` [Intel-gfx] " Daniel Vetter
2012-04-10 16:59       ` Jesse Barnes
2012-04-10 17:13         ` [PATCH] " Daniel Vetter
2012-04-10 22:37           ` Daniel Vetter
2012-04-26 16:38             ` Daniel Vetter
2012-04-26 16:56           ` Daniel Vetter
2012-04-10 11:55 ` [PATCH 2/4] drm/i915: clarify preferred sdvo input mode code Daniel Vetter
2012-04-10 12:18   ` Chris Wilson
2012-05-22  7:33     ` Daniel Vetter
2012-04-10 11:55 ` [PATCH 3/4] drm/i915: don't silently ignore sdvo mode_set failures Daniel Vetter
2012-04-10 11:55 ` [PATCH 4/4] drm/i915: debug messge for lossy sdvo dtd -> drm mode conversion Daniel Vetter

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=1334058949-5633-1-git-send-email-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 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.