Re: [RFC PATCH 2/2] tee: add OP-TEE driver

From: "Javier González" <javier@javigon.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Valentin Manea <valentin.manea@huawei.com>,
	devicetree@vger.kernel.org, emmanuel.michel@st.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jean-michel.delorme@st.com, tpmdd-devel@lists.sourceforge.net,
	Jens Wiklander <jens.wiklander@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 2/2] tee: add OP-TEE driver
Date: Sat, 18 Apr 2015 11:36:53 +0200	[thread overview]
Message-ID: <FCFF5E10-0DDC-4ED1-A8B8-D649ADD5E506@javigon.com> (raw)
In-Reply-To: <20150418085747.GC29858@kroah.com>

[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]

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@linuxfoundation.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

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel