On 03/20/2015 01:44 PM, Jens Wiklander wrote:
On Fri, Mar 20, 2015 at 12:00:21PM +0100, Pascal Brand wrote:
Hello Jens,
On 19 March 2015 at 14:48, Jérôme Forissier jerome.forissier@linaro.org wrote:
Hi Jens,
On 03/19/2015 11:23 AM, Jens Wiklander wrote:
[snip]
+/*
- This file describes the API provided by the generic TEE driver to
user
- space
- */
+#define TEE_VERSION 1
About TEE_* names: is it OK to use them, or should we use a different prefix to avoid confusions or even clashes with GP APIs? I'd say: keep them, since we're not tied to GP, and I don't think it can be a major problem.
I would say it can create confusion. In a specific backend driver which implements GP, we may have a mixed of defines coming from the generic driver and from the GP-TEE Internal API. All will look the same.
Agree, perhaps TEE_SUBSSYS_VERSION, all the ioctl related defines TEE_IOCTL_... and finally all structs 'struct tee_ioctl...'?
+1