Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751943AbcDOBk1 (ORCPT ); Thu, 14 Apr 2016 21:40:27 -0400 Received: from mail-yw0-f171.google.com ([209.85.161.171]:35933 "EHLO mail-yw0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751375AbcDOBk0 (ORCPT ); Thu, 14 Apr 2016 21:40:26 -0400 MIME-Version: 1.0 In-Reply-To: <1460683781-22535-7-git-send-email-gustavo@padovan.org> References: <1460683781-22535-1-git-send-email-gustavo@padovan.org> <1460683781-22535-7-git-send-email-gustavo@padovan.org> Date: Thu, 14 Apr 2016 21:40:25 -0400 Message-ID: Subject: Re: [RFC 6/8] drm/fence: create DRM_MODE_ATOMIC_OUT_FENCE flag From: Rob Clark To: Gustavo Padovan Cc: "dri-devel@lists.freedesktop.org" , Linux Kernel Mailing List , Daniel Stone , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Riley Andrews , Daniel Vetter , Greg Hackmann , John Harrison , Laurent Pinchart , Sean Paul , =?UTF-8?Q?St=C3=A9phane_Marchesin?= , Mauro Carvalho Chehab , Maarten Lankhorst , Gustavo Padovan Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1455 Lines: 43 On Thu, Apr 14, 2016 at 9:29 PM, Gustavo Padovan wrote: > From: Gustavo Padovan > > This flag tells drm_atomic_ioctl that we want to get a per-crtc out-fence > fd back. > > Signed-off-by: Gustavo Padovan > --- > include/uapi/drm/drm_mode.h | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h > index 7a7856e..39905cc 100644 > --- a/include/uapi/drm/drm_mode.h > +++ b/include/uapi/drm/drm_mode.h > @@ -582,13 +582,15 @@ struct drm_mode_destroy_dumb { > #define DRM_MODE_ATOMIC_TEST_ONLY 0x0100 > #define DRM_MODE_ATOMIC_NONBLOCK 0x0200 > #define DRM_MODE_ATOMIC_ALLOW_MODESET 0x0400 > +#define DRM_MODE_ATOMIC_OUT_FENCE 0x0800 > > #define DRM_MODE_ATOMIC_FLAGS (\ > DRM_MODE_PAGE_FLIP_EVENT |\ > DRM_MODE_PAGE_FLIP_ASYNC |\ > DRM_MODE_ATOMIC_TEST_ONLY |\ > DRM_MODE_ATOMIC_NONBLOCK |\ > - DRM_MODE_ATOMIC_ALLOW_MODESET) > + DRM_MODE_ATOMIC_ALLOW_MODESET |\ > + DRM_MODE_ATOMIC_OUT_FENCE) just to be pedantic / bisectable, perhaps this should be squashed in to patch that actually starts using this flag? Otherwise there is an intermediate state in git where the flag is accepted but ignored.. BR, -R > struct drm_mode_atomic { > __u32 flags; > -- > 2.5.5 >