linux/drivers/staging/android/uapi, branch v4.15

staging: android: uapi: drop definitions of removed ION_IOC_{FREE,SHARE} ioctls

2017-06-03T08:38:26Z

This problem was found by strace ioctl list generator. Fixes: 15c6098cfec5 ("staging: android: ion: Remove ion_handle and ion_client") Signed-off-by: Gleb Fotengauer-Malinovskiy Acked-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove ION_FLAG_CACHED_NEEDS_SYNC

2017-05-18T13:59:38Z

The flag ION_FLAG_CACHED_NEEDS_SYNC isn't used anymore. Remove it. Signed-off-by: Archit Taneja Reviewed-by: Sumit Semwal Acked-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove ion_handle and ion_client

2017-04-18T18:43:14Z

ion_handle was introduced as an abstraction to represent a reference to a buffer via an ion_client. As frameworks outside of Ion evolved, the dmabuf emerged as the preferred standard for use in the kernel. This has made the ion_handle an unnecessary abstraction and prone to race conditions. ion_client is also now only used internally. We have enough mechanisms for race conditions and leaks already so just drop ion_handle and ion_client. This also includes ripping out most of the debugfs infrastructure since much of that was tied to clients and handles. The debugfs infrastructure was prone to give confusing data (orphaned allocations) so it can be replaced with something better if people actually want it. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Break the ABI in the name of forward progress

2017-04-18T18:43:14Z

Several of the Ion ioctls were designed in such a way that they necessitate compat ioctls. We're breaking a bunch of other ABIs and cleaning stuff up anyway so let's follow the ioctl guidelines and clean things up while everyone is busy converting things over anyway. As part of this, also remove the useless alignment field from the allocation structure. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove old platform support

2017-04-08T10:36:11Z

Device specific platform support has been haphazard for Ion. There have been several independent attempts and there are still objections to what bindings exist right now. Just remove everything for a fresh start. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove duplicate ION_IOC_MAP

2017-04-08T10:36:11Z

ION_IOC_MAP is the same as ION_IOC_SHARE. We really don't need two identical interfaces. Remove it. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove import interface

2017-04-08T10:36:11Z

With the expansion of dma-buf and the move for Ion to be come just an allocator, the import mechanism is mostly useless. There isn't a kernel component to Ion anymore and handles are private to Ion. Remove this interface. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove custom ioctl interface

2017-04-08T10:36:11Z

Ion is now moving towards a unified interfact. This makes the custom ioctl interface unneeded. Remove it. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion: Remove crufty cache support

2017-04-08T10:36:11Z

Now that we call dma_map in the dma_buf API callbacks there is no need to use the existing cache APIs. Remove the sync ioctl and the existing bad dma_sync calls. Explicit caching can be handled with the dma_buf sync API. Signed-off-by: Laura Abbott Signed-off-by: Greg Kroah-Hartman

staging: android: ion_test: remove extra line per checkpatch.pl

2016-10-16T08:24:50Z

Cleanup extra line found by checkpatch.pl Signed-off-by: Wayne Porter Signed-off-by: Greg Kroah-Hartman