From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
"Daniel Stone" <daniels@collabora.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Riley Andrews" <riandrews@android.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Arve Hjønnevåg" <arve@android.com>,
pavel@ucw.cz, "Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"John Harrison" <John.C.Harrison@Intel.com>
Subject: Re: [PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface
Date: Thu, 11 Aug 2016 10:43:45 +0100 [thread overview]
Message-ID: <20160811094345.GQ10429@imgtec.com> (raw)
In-Reply-To: <1470691462-19140-6-git-send-email-gustavo@padovan.org>
On Mon, Aug 08, 2016 at 06:24:21PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> This interface is hidden from kernel headers and it is intended for use
> only for testing. So testers would have to add the ioctl information
> internally. This is to prevent misuse of this feature.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
> drivers/staging/android/sw_sync.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/drivers/staging/android/sw_sync.c b/drivers/staging/android/sw_sync.c
> index 43491b6..2ac5608 100644
> --- a/drivers/staging/android/sw_sync.c
> +++ b/drivers/staging/android/sw_sync.c
> @@ -25,6 +25,36 @@
> #define CREATE_TRACE_POINTS
> #include "sync_trace.h"
>
> +/*
> + * SW SYNC validation framework
> + *
> + * A sync object driver that uses a 32bit counter to coordinate
> + * synchronization. Useful when there is no hardware primitive backing
> + * the synchronization.
> + *
> + * To start the framework just open:
> + *
> + * <debugfs>/sync/sw_sync
> + *
> + * That will create a sync timeline, all fences created under this timeline
> + * file descriptor will belong to the this timeline.
> + *
> + * The 'sw_sync' file can be opened many times as to create different
> + * timelines.
> + *
> + * Fences can be created with SW_SYNC_IOC_CREATE_FENCE ioctl with struct
> + * sw_sync_ioctl_create_fence as parameter.
> + *
> + * To increment the timeline counter SW_SYNC_IOC_INC ioctl should be used
> + * with the increment as u32. This will update the last signaled value
> + * from the timeline and signal any fence that has seqno, smaller of equal
> + * it.
This last paragraph could use some love: comma before "SW_SYNC_IOC_INC",
"that has seqno smaller or equal to it."
> + *
> + * struct sw_sync_ioctl_create_fence
> + * @value: the seqno to initiate the fence with
s/initiate/initialise/
With these fixed,
Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com>
> + * @name: the name of the new sync point
> + * @fence: return the fd of the new sync_file with the created fence
> + */
> struct sw_sync_create_fence_data {
> __u32 value;
> char name[32];
> @@ -35,6 +65,7 @@ struct sw_sync_create_fence_data {
>
> #define SW_SYNC_IOC_CREATE_FENCE _IOWR(SW_SYNC_IOC_MAGIC, 0,\
> struct sw_sync_create_fence_data)
> +
> #define SW_SYNC_IOC_INC _IOW(SW_SYNC_IOC_MAGIC, 1, __u32)
>
> static const struct fence_ops timeline_fence_ops;
> --
> 2.5.5
next prev parent reply other threads:[~2016-08-11 9:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 21:24 [PATCH v2 0/6] de-stage SW_SYNC validation frawework Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 1/6] staging/android: remove doc from sw_sync Gustavo Padovan
2016-08-08 23:41 ` Pavel Machek
2016-08-11 15:06 ` Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 2/6] staging/android: do not let userspace trigger WARN_ON Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 3/6] staging/android: move trace/sync.h to sync_trace.h Gustavo Padovan
2016-08-11 9:41 ` Eric Engestrom
2016-08-08 21:24 ` [PATCH v2 4/6] staging/android: prepare sw_sync files for de-staging Gustavo Padovan
2016-08-11 9:42 ` Eric Engestrom
2016-08-08 21:24 ` [PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface Gustavo Padovan
2016-08-11 9:43 ` Eric Engestrom [this message]
2016-08-08 21:24 ` [PATCH v2 6/6] dma-buf/sw_sync: de-stage SW_SYNC Gustavo Padovan
2016-08-11 9:56 ` Eric Engestrom
2016-08-11 9:24 ` [PATCH v2 0/6] de-stage SW_SYNC validation frawework Eric Engestrom
2016-08-11 15:09 ` 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=20160811094345.GQ10429@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=John.C.Harrison@Intel.com \
--cc=arve@android.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=riandrews@android.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox