From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:35156 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751861AbcBIKF4 (ORCPT ); Tue, 9 Feb 2016 05:05:56 -0500 Received: by mail-wm0-f65.google.com with SMTP id g62so2426319wme.2 for ; Tue, 09 Feb 2016 02:05:55 -0800 (PST) Date: Tue, 9 Feb 2016 11:06:18 +0100 From: Daniel Vetter To: Mario Kleiner Cc: dri-devel@lists.freedesktop.org, linux@bernd-steinhauser.de, stable@vger.kernel.org, michel@daenzer.net, vbabka@suse.cz, ville.syrjala@linux.intel.com, daniel.vetter@ffwll.ch, alexander.deucher@amd.com, christian.koenig@amd.com Subject: Re: [PATCH 4/6] drm: Fix treatment of drm_vblank_offdelay in drm_vblank_on() Message-ID: <20160209100618.GO11240@phenom.ffwll.local> References: <1454894009-15466-1-git-send-email-mario.kleiner.de@gmail.com> <1454894009-15466-5-git-send-email-mario.kleiner.de@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1454894009-15466-5-git-send-email-mario.kleiner.de@gmail.com> Sender: stable-owner@vger.kernel.org List-ID: On Mon, Feb 08, 2016 at 02:13:27AM +0100, Mario Kleiner wrote: > drm_vblank_offdelay can have three different types of values: > > < 0 is to be always treated the same as dev->vblank_disable_immediate > = 0 is to be treated as "never disable vblanks" > > 0 is to be treated as disable immediate if kms driver wants it > that way via dev->vblank_disable_immediate. Otherwise it is > a disable timeout in msecs. > > This got broken in Linux 3.18+ for the implementation of > drm_vblank_on. If the user specified a value of zero which should > always reenable vblank irqs in this function, a kms driver could > override the users choice by setting vblank_disable_immediate > to true. This patch fixes the regression and keeps the user in > control. > > Signed-off-by: Mario Kleiner > Cc: # 3.18+ > Cc: michel@daenzer.net > Cc: vbabka@suse.cz > Cc: ville.syrjala@linux.intel.com > Cc: daniel.vetter@ffwll.ch > Cc: dri-devel@lists.freedesktop.org > Cc: alexander.deucher@amd.com > Cc: christian.koenig@amd.com > --- > drivers/gpu/drm/drm_irq.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c > index 5c27ad3..fb17c45 100644 > --- a/drivers/gpu/drm/drm_irq.c > +++ b/drivers/gpu/drm/drm_irq.c > @@ -1492,8 +1492,8 @@ void drm_vblank_on(struct drm_device *dev, unsigned int pipe) > * re-enable interrupts if there are users left, or the > * user wishes vblank interrupts to be enabled all the time. > */ > - if (atomic_read(&vblank->refcount) != 0 || > - (!dev->vblank_disable_immediate && drm_vblank_offdelay == 0)) > + if (atomic_read(&vblank->refcount) != 0 || drm_vblank_offdelay == 0 || > + (!dev->vblank_disable_immediate && drm_vblank_offdelay > 0)) Hm, shouldn't we change this to only enable the vblank irq if we need it, i.e. offdelay == 0? For delayed disabling there's kinda no need to enable it superflously after a modeset, if userspace didn't yet ask for vblank timestamps. But then is was specifically added by Ville in cd19e52aee922, so I guess someone really wants this. Reviewed-by: Daniel Vetter > WARN_ON(drm_vblank_enable(dev, pipe)); > spin_unlock_irqrestore(&dev->vbl_lock, irqflags); > } > -- > 1.9.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch