From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH] drm/i915: rip out unnecessary calls to drm_mode_set_crtcinfo Date: Fri, 4 May 2012 11:33:32 +0200 Message-ID: <20120504093332.GC5443@phenom.ffwll.local> References: <1336055159_130964@CP5-2952> <1336053118-11952-1-git-send-email-daniel.vetter@ffwll.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bk0-f49.google.com (mail-bk0-f49.google.com [209.85.214.49]) by gabe.freedesktop.org (Postfix) with ESMTP id 6E9BC9F011 for ; Fri, 4 May 2012 02:32:27 -0700 (PDT) Received: by bkwj4 with SMTP id j4so2672705bkw.36 for ; Fri, 04 May 2012 02:32:26 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1336053118-11952-1-git-send-email-daniel.vetter@ffwll.ch> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Intel Graphics Development Cc: Daniel Vetter List-Id: intel-gfx@lists.freedesktop.org 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 > 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 > 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 > 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 > Signed-Off-by: Daniel Vetter Queued for -next, thanks for the review. -Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48