From: Gustavo Padovan <gustavo@padovan.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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>,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"John Harrison" <John.C.Harrison@Intel.com>
Subject: [PATCH v2 00/11] sync framework de-staging: part 2 - de-stage
Date: Wed, 27 Jan 2016 11:30:28 -0200 [thread overview]
Message-ID: <1453901439-19467-1-git-send-email-gustavo@padovan.org> (raw)
From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
This patch series de-stage the sync framework and it a follow up on the
clean up series I've sent last week:
http://thread.gmane.org/gmane.comp.video.dri.devel/145509
Now in part 2 we finish the de-stage of the sync framework. It start with the
move of sync_file from staging to drivers/dma-buf, followed by a bunch of clean
ups on sync_timeline and sw_sync. Finally we de-stage the later two plus the
debug routines.
v2: use git format-patch -M
Gustavo Padovan (11):
dma-buf/sync_file: de-stage sync_file
staging/android: store last signaled value on sync timeline
staging/android: remove .fill_driver_data() timeline ops
staging/android: remove .{fence,timeline}_value_str() from
timeline_ops
staging/android: remove struct sync_timeline_ops
staging/android: remove sw_sync_timeline and sw_sync_pt
staging/android: remove sw_sync.[ch] files
staging/android: rename android_fence to timeline_fence
dma-buf/sync_timeline: de-stage sync_timeline
dma-buf/sync_file: bring debug back to sync file
dma-buf/sync_file: bring sync_dump() back
drivers/Kconfig | 2 +
drivers/dma-buf/Kconfig | 21 ++
drivers/dma-buf/Makefile | 2 +
.../{staging/android/uapi => dma-buf}/sw_sync.h | 0
drivers/{staging/android => dma-buf}/sync_debug.c | 40 ++--
drivers/dma-buf/sync_debug.h | 35 +++
.../android/sync.c => dma-buf/sync_file.c} | 245 ++-----------------
drivers/dma-buf/sync_timeline.c | 222 ++++++++++++++++++
drivers/staging/android/Kconfig | 19 --
drivers/staging/android/Makefile | 1 -
drivers/staging/android/sw_sync.c | 103 --------
drivers/staging/android/sw_sync.h | 59 -----
drivers/staging/android/sync.h | 261 ---------------------
include/linux/sync_file.h | 123 ++++++++++
include/linux/sync_timeline.h | 114 +++++++++
.../sync.h => include/trace/events/sync_file.h | 35 +--
include/trace/events/sync_timeline.h | 31 +++
.../android/uapi => include/uapi/linux}/sync.h | 12 +-
18 files changed, 604 insertions(+), 721 deletions(-)
create mode 100644 drivers/dma-buf/Kconfig
rename drivers/{staging/android/uapi => dma-buf}/sw_sync.h (100%)
rename drivers/{staging/android => dma-buf}/sync_debug.c (91%)
create mode 100644 drivers/dma-buf/sync_debug.h
rename drivers/{staging/android/sync.c => dma-buf/sync_file.c} (62%)
create mode 100644 drivers/dma-buf/sync_timeline.c
delete mode 100644 drivers/staging/android/sw_sync.c
delete mode 100644 drivers/staging/android/sw_sync.h
delete mode 100644 drivers/staging/android/sync.h
create mode 100644 include/linux/sync_file.h
create mode 100644 include/linux/sync_timeline.h
rename drivers/staging/android/trace/sync.h => include/trace/events/sync_file.h (58%)
create mode 100644 include/trace/events/sync_timeline.h
rename {drivers/staging/android/uapi => include/uapi/linux}/sync.h (90%)
--
2.5.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-01-27 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 13:30 Gustavo Padovan [this message]
2016-01-27 13:30 ` [PATCH v2 01/11] dma-buf/sync_file: de-stage sync_file Gustavo Padovan
2016-01-27 14:31 ` Maarten Lankhorst
2016-01-27 17:03 ` Gustavo Padovan
2016-01-27 18:17 ` Emil Velikov
2016-01-27 20:25 ` Gustavo Padovan
2016-01-27 21:41 ` Greg Hackmann
2016-01-28 9:23 ` Daniel Vetter
2016-01-29 17:46 ` Greg Hackmann
2016-01-27 13:30 ` [PATCH v2 02/11] staging/android: store last signaled value on sync timeline Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 03/11] staging/android: remove .fill_driver_data() timeline ops Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 04/11] staging/android: remove .{fence, timeline}_value_str() from timeline_ops Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 05/11] staging/android: remove struct sync_timeline_ops Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 06/11] staging/android: remove sw_sync_timeline and sw_sync_pt Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 07/11] staging/android: remove sw_sync.[ch] files Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 08/11] staging/android: rename android_fence to timeline_fence Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 09/11] dma-buf/sync_timeline: de-stage sync_timeline Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 10/11] dma-buf/sync_file: bring debug back to sync file Gustavo Padovan
2016-01-27 13:30 ` [PATCH v2 11/11] dma-buf/sync_file: bring sync_dump() back 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=1453901439-19467-1-git-send-email-gustavo@padovan.org \
--to=gustavo@padovan.org \
--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=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).