From: Gustavo Padovan <gustavo@padovan.org>
To: Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org, marcheu@google.com,
Daniel Stone <daniels@collabora.com>,
seanpaul@google.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
John Harrison <John.C.Harrison@Intel.com>,
m.chehab@samsung.com
Subject: Re: [PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc
Date: Tue, 15 Nov 2016 17:42:35 +0900 [thread overview]
Message-ID: <20161115084235.GA20601@joana> (raw)
In-Reply-To: <20161115082555.GB30410@nuc-i3427.alporthouse.com>
2016-11-15 Chris Wilson <chris@chris-wilson.co.uk>:
> On Tue, Nov 15, 2016 at 10:57:35AM +0900, Gustavo Padovan wrote:
> > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> > index 11780a9..0870de1 100644
> > --- a/include/drm/drm_crtc.h
> > +++ b/include/drm/drm_crtc.h
> > @@ -32,6 +32,8 @@
> > #include <linux/fb.h>
> > #include <linux/hdmi.h>
> > #include <linux/media-bus-format.h>
> > +#include <linux/srcu.h>
> > +#include <linux/dma-fence.h>
> > #include <uapi/drm/drm_mode.h>
> > #include <uapi/drm/drm_fourcc.h>
> > #include <drm/drm_modeset_lock.h>
> > @@ -739,9 +741,52 @@ struct drm_crtc {
> > */
> > struct drm_crtc_crc crc;
> > #endif
> > +
> > + /**
> > + * @fence_context:
> > + *
> > + * timeline context used for fence operations.
> > + */
> > + unsigned int fence_context;
> > +
> > + /**
> > + * @fence_lock:
> > + *
> > + * spinlock to protect the fences in the fence_context.
> > + */
> > +
> > + spinlock_t fence_lock;
> > + /**
> > + * @fence_seqno:
> > + *
> > + * Seqno variable used as monotonic counter for the fences
> > + * created on the CRTC's timeline.
> > + */
> > + unsigned long fence_seqno;
> > +
> > + /**
> > + * @timeline_name:
> > + *
> > + * The name of the CRTC's fence timeline.
> > + */
> > + char timeline_name[32];
> > };
> >
> > /**
> > + * dma_crtc_fence_ops - fence ops for the drm_crtc timeline
> > + *
> > + * It contains the dma_fence_ops that should be called by the dma_fence
> > + * code. CRTC core should use this ops when initializing fences.
> > + */
> > +extern const struct dma_fence_ops drm_crtc_fence_ops;
> > +
> > +static inline struct drm_crtc *fence_to_crtc(struct dma_fence *fence)
> > +{
> > + BUG_ON(fence->ops != &drm_crtc_fence_ops);
> > + return container_of(fence->lock, struct drm_crtc, fence_lock);
> > +}
>
> If you are planning to export this for use by drivers, you are missing
> the EXPORT_SYMBOL(drm_crtc_fence_ops).
Drivers should not be using this, at least for now.
Gustavo
next prev parent reply other threads:[~2016-11-15 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 1:57 [PATCH v11 0/3] drm: add explicit fencing Gustavo Padovan
2016-11-15 1:57 ` [PATCH v11 1/3] drm/fence: add in-fences support Gustavo Padovan
2016-11-15 1:57 ` Gustavo Padovan
2016-11-15 1:57 ` [PATCH v11 2/3] drm/fence: add fence timeline to drm_crtc Gustavo Padovan
2016-11-15 1:57 ` Gustavo Padovan
2016-11-15 8:25 ` Chris Wilson
2016-11-15 8:39 ` Chris Wilson
2016-11-15 8:39 ` Chris Wilson
2016-11-15 8:42 ` Gustavo Padovan [this message]
2016-11-15 8:52 ` Daniel Vetter
2016-11-15 8:55 ` Chris Wilson
2016-11-15 8:55 ` Chris Wilson
2016-11-15 1:57 ` [PATCH v11 3/3] drm/fence: add out-fences support Gustavo Padovan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161115084235.GA20601@joana \
--to=gustavo@padovan.org \
--cc=John.C.Harrison@Intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=marcheu@google.com \
--cc=seanpaul@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.