From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Padovan Subject: Re: [PATCH v2] drm/exynos: calculate vrefresh instead of use a fixed value Date: Wed, 20 May 2015 17:50:55 -0300 Message-ID: <20150520205055.GB4438@joana> References: <1432147477-12650-1-git-send-email-gustavo@padovan.org> <555CDC6F.9070000@math.uni-bielefeld.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <555CDC6F.9070000@math.uni-bielefeld.de> Sender: linux-samsung-soc-owner@vger.kernel.org To: Tobias Jakobi Cc: linux-samsung-soc@vger.kernel.org, dri-devel@lists.freedesktop.org, inki.dae@samsung.com, jy0922.shim@samsung.com, daniel@fooishbar.org, Gustavo Padovan List-Id: dri-devel@lists.freedesktop.org 2015-05-20 Tobias Jakobi : > Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > When mode's vrefresh is zero we should ask DRM core to calculate vrefresh > > for us so we can get the correct value instead of relying on fixed value > > defined in a macro. But if vrefresh is still zero we should fail the > > update. > Even with this we still need to consider crtc->state->adjusted_mode in > fimd_commit(), otherwise vrefresh computed by drm_mode_vrefresh() is > never actually used. You are right, I think we should pass crtc->state->adjusted_mode to fimd_calc_clkdiv(). I'll send a v3 with this change. Gustavo