Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-03 Thread Volodymyr Babchuk
On 3 November 2016 at 21:35, Jens Wiklander wrote: > On Mon, Oct 31, 2016 at 01:24:14PM -0500, Andrew F. Davis wrote: >> On 10/29/2016 04:46 AM, Jens Wiklander wrote: >> > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: >> >> On 10/28/2016 05:19 AM,

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-03 Thread Volodymyr Babchuk
On 3 November 2016 at 21:35, Jens Wiklander wrote: > On Mon, Oct 31, 2016 at 01:24:14PM -0500, Andrew F. Davis wrote: >> On 10/29/2016 04:46 AM, Jens Wiklander wrote: >> > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: >> >> On 10/28/2016 05:19 AM, Jens Wiklander wrote: >> >>>

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-03 Thread Jens Wiklander
On Mon, Oct 31, 2016 at 01:24:14PM -0500, Andrew F. Davis wrote: > On 10/29/2016 04:46 AM, Jens Wiklander wrote: > > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > >> On 10/28/2016 05:19 AM, Jens Wiklander wrote: > >>> Hi, > >>> > >>> This patch set introduces a generic TEE

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-03 Thread Jens Wiklander
On Mon, Oct 31, 2016 at 01:24:14PM -0500, Andrew F. Davis wrote: > On 10/29/2016 04:46 AM, Jens Wiklander wrote: > > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > >> On 10/28/2016 05:19 AM, Jens Wiklander wrote: > >>> Hi, > >>> > >>> This patch set introduces a generic TEE

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-01 Thread Andrew F. Davis
On 10/28/2016 01:19 PM, Mark Brown wrote: > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > >> Do we see this as a chicken and egg situation, or is there any harm >> beyond the pains of supporting an out-of-tree driver for a while, to >> wait until we have at least one other

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-11-01 Thread Andrew F. Davis
On 10/28/2016 01:19 PM, Mark Brown wrote: > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > >> Do we see this as a chicken and egg situation, or is there any harm >> beyond the pains of supporting an out-of-tree driver for a while, to >> wait until we have at least one other

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-31 Thread Andrew F. Davis
On 10/29/2016 04:46 AM, Jens Wiklander wrote: > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: >> On 10/28/2016 05:19 AM, Jens Wiklander wrote: >>> Hi, >>> >>> This patch set introduces a generic TEE subsystem. The TEE subsystem will >>> contain drivers for various TEE

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-31 Thread Andrew F. Davis
On 10/29/2016 04:46 AM, Jens Wiklander wrote: > On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: >> On 10/28/2016 05:19 AM, Jens Wiklander wrote: >>> Hi, >>> >>> This patch set introduces a generic TEE subsystem. The TEE subsystem will >>> contain drivers for various TEE

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-29 Thread Jens Wiklander
On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > On 10/28/2016 05:19 AM, Jens Wiklander wrote: > > Hi, > > > > This patch set introduces a generic TEE subsystem. The TEE subsystem will > > contain drivers for various TEE implementations. A TEE (Trusted Execution > > Environment)

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-29 Thread Jens Wiklander
On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > On 10/28/2016 05:19 AM, Jens Wiklander wrote: > > Hi, > > > > This patch set introduces a generic TEE subsystem. The TEE subsystem will > > contain drivers for various TEE implementations. A TEE (Trusted Execution > > Environment)

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Mark Brown
On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > Do we see this as a chicken and egg situation, or is there any harm > beyond the pains of supporting an out-of-tree driver for a while, to > wait until we have at least one other TEE to add to this subsystem > before merging? We

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Mark Brown
On Fri, Oct 28, 2016 at 10:43:24AM -0500, Andrew F. Davis wrote: > Do we see this as a chicken and egg situation, or is there any harm > beyond the pains of supporting an out-of-tree driver for a while, to > wait until we have at least one other TEE to add to this subsystem > before merging? We

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Andrew F. Davis
On 10/28/2016 05:19 AM, Jens Wiklander wrote: > Hi, > > This patch set introduces a generic TEE subsystem. The TEE subsystem will > contain drivers for various TEE implementations. A TEE (Trusted Execution > Environment) is a trusted OS running in some secure environment, for > example, TrustZone

Re: [PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Andrew F. Davis
On 10/28/2016 05:19 AM, Jens Wiklander wrote: > Hi, > > This patch set introduces a generic TEE subsystem. The TEE subsystem will > contain drivers for various TEE implementations. A TEE (Trusted Execution > Environment) is a trusted OS running in some secure environment, for > example, TrustZone

[PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Jens Wiklander
Hi, This patch set introduces a generic TEE subsystem. The TEE subsystem will contain drivers for various TEE implementations. A TEE (Trusted Execution Environment) is a trusted OS running in some secure environment, for example, TrustZone on ARM CPUs, or a separate secure co-processor etc.

[PATCH v12 RESEND 0/4] generic TEE subsystem

2016-10-28 Thread Jens Wiklander
Hi, This patch set introduces a generic TEE subsystem. The TEE subsystem will contain drivers for various TEE implementations. A TEE (Trusted Execution Environment) is a trusted OS running in some secure environment, for example, TrustZone on ARM CPUs, or a separate secure co-processor etc.