On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote: > Just to show it's easy. > > Android syncpoints can be mapped to a timeline. This removes the need > to maintain a separate api for synchronization. I've left the android > trace events in place, but the core fence events should already be > sufficient for debugging. > > v2: > - Call fence_remove_callback in sync_fence_free if not all fences have fired. > v3: > - Merge Colin Cross' bugfixes, and the android fence merge optimization. > v4: > - Merge with the upstream fixes. > v5: > - Fix small style issues pointed out by Thomas Hellstrom. > > Signed-off-by: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxx> > Acked-by: John Stultz <john.stultz@xxxxxxxxxx> > --- > drivers/staging/android/Kconfig | 1 > drivers/staging/android/Makefile | 2 > drivers/staging/android/sw_sync.c | 6 > drivers/staging/android/sync.c | 913 +++++++++++----------------------- > drivers/staging/android/sync.h | 79 ++- > drivers/staging/android/sync_debug.c | 247 +++++++++ > drivers/staging/android/trace/sync.h | 12 > 7 files changed, 609 insertions(+), 651 deletions(-) > create mode 100644 drivers/staging/android/sync_debug.c With these changes, can we pull the android sync logic out of drivers/staging/ now? thanks, greg k-h _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
