From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Padovan Subject: Re: [PATCH v5 4/4] drm/fence: add out-fences support Date: Thu, 20 Oct 2016 13:55:38 -0200 Message-ID: <20161020155538.GA10205@joana> References: <1476975005-30441-1-git-send-email-gustavo@padovan.org> <1476975005-30441-5-git-send-email-gustavo@padovan.org> <20161020153518.GX4329@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Return-path: Content-Disposition: inline In-Reply-To: <20161020153518.GX4329@intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Cc: Gustavo Padovan , dri-devel@lists.freedesktop.org, marcheu@google.com, Daniel Stone , seanpaul@google.com, Daniel Vetter , linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com, Gustavo Padovan , John Harrison , m.chehab@samsung.com List-Id: dri-devel@lists.freedesktop.org 2016-10-20 Ville Syrjälä : > On Thu, Oct 20, 2016 at 12:50:05PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Support DRM out-fences by creating a sync_file with a fence for each CRTC > > that sets the OUT_FENCE_PTR property. > > I still maintain the out fence should also be per fb (well, per plane > since we can't add it to fbs). Otherwise it's not going to be at all > useful if you do fps>vrefresh and don't include the same set of planes > in every atomic ioctl, eg. if you only ever include ones that are > somehow dirty. How would the kernel signal these dirty planes then? Right now we signal at the vblank. Gustavo