[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+M3ks6fddVwvwiUSBkMccV7utVVuB=iBqGonURimavM=sSWUw@mail.gmail.com>
Date: Tue, 12 May 2015 10:46:26 +0200
From: Benjamin Gaignard <benjamin.gaignard@...aro.org>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: Daniel Vetter <daniel@...ll.ch>,
Thierry Reding <treding@...dia.com>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Hans Verkuil <hverkuil@...all.nl>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Rob Clark <robdclark@...il.com>,
Dave Airlie <airlied@...hat.com>,
Sumit Semwal <sumit.semwal@...aro.org>,
Tom Gall <tom.gall@...aro.org>
Subject: Re: [RFC] How implement Secure Data Path ?
I think now I have an answer to my question.
I will back come in a couple of weeks with a generic dmabuf allocator.
The feature set of this should be:
- allow to have per device specificone allocator
- ioctl for buffer allocation and exporting dmabuf file descriptor on /dev/foo
- generic API to be able to call buffer securing module which is
platform specific.
- ioctl and kernel API to set/get dmabuf secure status
Sumit had already done a draft of this kind of dmabuf allocator with
his cenalloc [1]
I think I will start from that.
Benjamin
[1] http://git.linaro.org/people/sumit.semwal/linux-3.x.git on
cenalloc_wip branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists