lkml.org 
[lkml]   [2015]   [Apr]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC PATCH 2/2] tee: add OP-TEE driver
From
Date
> On 18 Apr 2015, at 21:01, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Saturday 18 April 2015 20:49:03 Greg Kroah-Hartman wrote:
>> On Sat, Apr 18, 2015 at 11:36:53AM +0200, Javier González wrote:
>>> Hi,
>>
>> A: No.
>> Q: Should I include quotations after my reply?
>>
>> http://daringfireball.net/2007/07/on_top
>>
>>> 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.
>>
>> No, please provide a "real" solution, just providing a framework that no
>> one uses means that I get to delete it from the kernel tree the next
>> release, and I doubt you want that
>>
>> Please do all of the work here, as odds are, what you need in the end
>> will be different from what you have proposed here.
>
> I guess an alternative would be to remove all the unused infrastructure
> code and only provide a user space interface for the features that
> op_tee requires, but no optional user interfaces or in-kernel interfaces.
>
> Arnd

Only providing user space support would defeat one of the main purposes
of the driver. We could better organize the patches and divide them into user
space support and in-kernel support if that is what you mean. In the end
the interfaces are orthogonal, even though the functionality should be very
similar.


Javier.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2015-04-19 13:41    [W:0.090 / U:2.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site