On Wed, Mar 9, 2016 at 10:40 AM, Benjamin Gaignard
wrote:
> dmabuf have just accept one ioctl for cache management but I think
> that some exporter may need also need custom iotcl.
>
> For example I'm working since a while on a way to secure buffer (SMAF)
> [1] which is a central allocator + 2 ioc
dmabuf have just accept one ioctl for cache management but I think
that some exporter may need also need custom iotcl.
For example I'm working since a while on a way to secure buffer (SMAF)
[1] which is a central allocator + 2 ioctl for set/get secure status
of the buffer.
This not depend on one d
Am 09.03.2016 um 10:03 schrieb Daniel Vetter:
> On Wed, Mar 9, 2016 at 9:54 AM, Benjamin Gaignard
> wrote:
>> In addition of the already existing operations allow exporter
>> to use it own custom ioctls.
>>
>> Signed-off-by: Benjamin Gaignard
> First reaction: No way ever! More seriously, please
On Wed, Mar 9, 2016 at 9:54 AM, Benjamin Gaignard
wrote:
> In addition of the already existing operations allow exporter
> to use it own custom ioctls.
>
> Signed-off-by: Benjamin Gaignard
First reaction: No way ever! More seriously, please start by
explaining why you need this.
-Daniel
> ---
>
In addition of the already existing operations allow exporter
to use it own custom ioctls.
Signed-off-by: Benjamin Gaignard
---
drivers/dma-buf/dma-buf.c | 3 +++
include/linux/dma-buf.h | 5 +
2 files changed, 8 insertions(+)
diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-b
