From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 1/2] drm/i915: use mode values consistently when converting to sdvo dtd Date: Tue, 24 Apr 2012 20:24:20 +0100 Message-ID: <1335295491_40619@CP5-2952> References: <1335284878-22201-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 fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id B863EA0B18 for ; Tue, 24 Apr 2012 12:24:58 -0700 (PDT) In-Reply-To: <1335284878-22201-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 Tue, 24 Apr 2012 18:27:57 +0200, Daniel Vetter wrote: > The drm_mode->dtd conversion used the crtc timings, whereas the > dtd->drm_mod did not set these. Use the standard mode information, not > the crtc timings, in both cases to make these two functions proper > inverses of each another. > > Note that this also kills the risk that we handle interlaced timings > inconsistently because the drm core uses half-frames for crtc timings, > whereas we need full frames. But interlaced support is pretty decently > broken anyway for sdvo encoders, so no big deal. So as I understand it, if we had interlacing or dblscan enabled on the incoming mode we would have been feeding the display timing into the magic black box of the SDVO encoder rather the mode line. Reviewed-by: Chris Wilson -Chris -- Chris Wilson, Intel Open Source Technology Centre