Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754689AbcJTUMO convert rfc822-to-8bit (ORCPT ); Thu, 20 Oct 2016 16:12:14 -0400 Received: from mail-vk0-f68.google.com ([209.85.213.68]:36376 "EHLO mail-vk0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbcJTUMN (ORCPT ); Thu, 20 Oct 2016 16:12:13 -0400 Date: Thu, 20 Oct 2016 18:12:06 -0200 From: Gustavo Padovan To: Brian Starkey Cc: 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 Subject: Re: [PATCH v5 3/4] drm/fence: add fence timeline to drm_crtc Message-ID: <20161020201206.GB2734@joana> Mail-Followup-To: Gustavo Padovan , Brian Starkey , 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 References: <1476975005-30441-1-git-send-email-gustavo@padovan.org> <1476975005-30441-4-git-send-email-gustavo@padovan.org> <20161020172054.GA7165@e106950-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20161020172054.GA7165@e106950-lin.cambridge.arm.com> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3511 Lines: 107 2016-10-20 Brian Starkey : > Hi Gustavo, > > On Thu, Oct 20, 2016 at 12:50:04PM -0200, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Create one timeline context for each CRTC to be able to handle out-fences > > and signal them. It adds a few members to struct drm_crtc: fence_context, > > where we store the context we get from fence_context_alloc(), the > > fence seqno and the fence lock, that we pass in fence_init() to be > > used by the fence. > > > > v2: Comment by Daniel Stone: > > - add BUG_ON() to fence_to_crtc() macro > > > > v3: Comment by Ville Syrj?l? > > - Use more meaningful name as crtc timeline name > > > > Signed-off-by: Gustavo Padovan > > --- > > drivers/gpu/drm/drm_crtc.c | 31 +++++++++++++++++++++++++++++++ > > include/drm/drm_crtc.h | 19 +++++++++++++++++++ > > 2 files changed, 50 insertions(+) > > > > diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c > > index fcb6453..b99090f 100644 > > --- a/drivers/gpu/drm/drm_crtc.c > > +++ b/drivers/gpu/drm/drm_crtc.c > > @@ -165,6 +165,32 @@ static void drm_crtc_crc_fini(struct drm_crtc *crtc) > > #endif > > } > > > > +static const char *drm_crtc_fence_get_driver_name(struct fence *fence) > > +{ > > + struct drm_crtc *crtc = fence_to_crtc(fence); > > + > > + return crtc->dev->driver->name; > > +} > > + > > +static const char *drm_crtc_fence_get_timeline_name(struct fence *fence) > > +{ > > + struct drm_crtc *crtc = fence_to_crtc(fence); > > + > > + return crtc->timeline_name; > > +} > > + > > +static bool drm_crtc_fence_enable_signaling(struct fence *fence) > > +{ > > + return true; > > +} > > + > > +const struct fence_ops drm_crtc_fence_ops = { > > + .get_driver_name = drm_crtc_fence_get_driver_name, > > + .get_timeline_name = drm_crtc_fence_get_timeline_name, > > + .enable_signaling = drm_crtc_fence_enable_signaling, > > + .wait = fence_default_wait, > > +}; > > + > > /** > > * drm_crtc_init_with_planes - Initialise a new CRTC object with > > * specified primary and cursor planes. > > @@ -222,6 +248,11 @@ int drm_crtc_init_with_planes(struct drm_device *dev, struct drm_crtc *crtc, > > return -ENOMEM; > > } > > > > + crtc->fence_context = fence_context_alloc(1); > > + spin_lock_init(&crtc->fence_lock); > > + snprintf(crtc->timeline_name, sizeof(crtc->timeline_name), > > + "drm_crtc-%d", crtc->base.id); > > I wondered about "[CRTC:id:name]" to be consistent with the DRM debug > prints. Yeah, sounds good to me. > > > + > > crtc->base.properties = &crtc->properties; > > > > list_add_tail(&crtc->head, &config->crtc_list); > > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h > > index 279132e..657a33a 100644 > > --- a/include/drm/drm_crtc.h > > +++ b/include/drm/drm_crtc.h > > @@ -32,6 +32,8 @@ > > #include > > #include > > #include > > +#include > > +#include > > #include > > #include > > #include > > @@ -618,6 +620,9 @@ struct drm_crtc_funcs { > > * @gamma_store: gamma ramp values > > * @helper_private: mid-layer private data > > * @properties: property tracking for this CRTC > > + * @fence_context: context for fence signalling > > + * @fence_lock: fence lock for the fence context > > + * @fence_seqno: seqno variable to create fences > > @timeline_name ? Sure. Gustavo