All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: rip out unnecessary calls to drm_mode_set_crtcinfo
Date: Fri, 4 May 2012 11:33:32 +0200	[thread overview]
Message-ID: <20120504093332.GC5443@phenom.ffwll.local> (raw)
In-Reply-To: <1336053118-11952-1-git-send-email-daniel.vetter@ffwll.ch>

On Thu, May 03, 2012 at 03:51:58PM +0200, Daniel Vetter wrote:
> Our handling of the crtc timing computation has been nicely
> cargo-culted with calls to drm_mode_set_crtcinfo sprinkled all over
> the place. But with
> 
> commit f9bef081c3c3f77bec54454872e98d3ec635756f
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Sun Apr 15 19:53:19 2012 +0200
> 
>     drm/i915: don't clobber the special upscaling lvds timings
> 
> and
> 
> 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
> 
> we now only set the crtc timing fields in the encoder->mode_fixup
> (lvds only) and in crtc->mode_fixup (for everyone else). And since
> 
> commit 75c13993db592343bda1fd62f2555fea037d56bd
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Sat Jan 28 23:48:46 2012 +0100
> 
>     drm/i915: fixup overlay checks for interlaced modes
> 
> the only places we actually need the crtc timings is in the mode_set
> function.
> 
> I guess the idea of the drm core is that every time it creates a drm
> mode, it also sets the timings. But afaics it never uses them, safe
> for the precise vblank timestamp code (but that can only run on active
> modes, i.e.  after our mode_fixup functions have been called). The
> problem is that drm core always sets CRTC_INTERLACE_HALVE_V, so the
> timings are pretty much bogus for us anyway (at least with interlaced
> support).
> 
> So I guess it's the drivers job that every active modes needs to have
> crtc timings that suits it, and with these patches we should have
> that. drm core doesn't seem to care about modes that just get passed
> around. Hence we can now safely rip out all the remaining calls to
> set_crtcinfo left in the driver and clean up this confusion.
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Queued for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-05-04  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 13:41 [PATCH] drm/i915: rip out unnecessary calls to drm_mode_set_crtcinfo Daniel Vetter
2012-04-24 15:11 ` Chris Wilson
2012-04-24 15:37   ` Daniel Vetter
2012-05-03 14:26     ` Chris Wilson
2012-05-03 13:51       ` Daniel Vetter
2012-05-04  9:33         ` 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=20120504093332.GC5443@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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 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.