Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: don't clobber the special upscaling lvds timings
Date: Mon, 16 Apr 2012 09:34:44 +0200	[thread overview]
Message-ID: <20120416073423.GA4199@phenom.ffwll.local> (raw)
In-Reply-To: <1334513013_2817@CP5-2952>

On Sun, Apr 15, 2012 at 07:03:18PM +0100, Chris Wilson wrote:
> On Sun, 15 Apr 2012 19:53:19 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > This regression has been introduced in
> > 
> > commit ca9bfa7eed20ea34e862804e62aae10eb159edbb
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date:   Sat Jan 28 14:49:20 2012 +0100
> > 
> >     drm/i915: fixup interlaced vertical timings confusion, part 1
> > 
> > Unfortunately that commit failed to take into account that the lvds
> > code does some special adjustements to the crtc timings for upscaling
> > an centering.
> > 
> > Fix this by explicitly computing crtc timings in the lvds mode fixup
> > function and setting a special flag in mode->private_flags if the crtc
> > timings have been adjusted.
> > 
> > v2: Add a comment to explain the new mode driver private flag,
> > suggested by Eugeni Dodonov.
> > 
> > v3: Kill the confusing and now redundant set_crtcinfo call in
> > intel_fixed_panel_mode, noticed by Chris Wilson.
> > 
> > Reported-and-Tested-by: Hans de Bruin <jmdebruin@xmsnet.nl>
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43071
> > Reviewed-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> The patch fixes a regression and shouldn't have any side-effects as far
> as I can see, so
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> Just wish there were more ponies.

Picked up for -fixes, thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-04-16  7:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 16:17 [PATCH] drm/i915: don't clobber the special upscaling lvds timings Daniel Vetter
2012-04-14 16:43 ` Chris Wilson
2012-04-14 16:54   ` Daniel Vetter
2012-04-14 17:05     ` Chris Wilson
2012-04-15 15:07       ` Eugeni Dodonov
2012-04-15 15:19 ` Eugeni Dodonov
2012-04-15 17:24   ` Daniel Vetter
2012-04-15 17:38     ` Chris Wilson
2012-04-15 17:53       ` Daniel Vetter
2012-04-15 18:03         ` Chris Wilson
2012-04-16  7:34           ` Daniel Vetter [this message]

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=20120416073423.GA4199@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox