[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FCFF5E10-0DDC-4ED1-A8B8-D649ADD5E506@javigon.com>
Date: Sat, 18 Apr 2015 11:36:53 +0200
From: Javier González <javier@...igon.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jens Wiklander <jens.wiklander@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>,
Herbert Xu <herbert@...dor.apana.org.au>,
tpmdd-devel@...ts.sourceforge.net,
Valentin Manea <valentin.manea@...wei.com>,
jean-michel.delorme@...com, emmanuel.michel@...com
Subject: Re: [RFC PATCH 2/2] tee: add OP-TEE driver
Hi,
We have discussed and implemented an in-kernel interface for the driver.
However, we need to agree on that interface with the kernel submodules that
can be interested in using it (e.g., IMA, keyring). We though it was easier
to have a framework in place before taking this space. This makes sense
since a TEE driver will be, as for today, mostly used by user space.
applications.
Best,
Javier
> On 18 Apr 2015, at 10:57, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
>
> On Fri, Apr 17, 2015 at 09:50:57AM +0200, Jens Wiklander wrote:
>> Adds mostly stubbed OP-TEE driver which also can be compiled as a
>> loadable module.
>
> Please provide a "real" driver, so that we can see how this is all going
> to work. Otherwise it's not really that useful to create some framework
> that nothing in-kernel is going to use.
>
> thanks,
>
> greg k-h
Download attachment "signature.asc" of type "application/pgp-signature" (843 bytes)
Powered by blists - more mailing lists