From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753957AbcKATWE (ORCPT ); Tue, 1 Nov 2016 15:22:04 -0400 Received: from arroyo.ext.ti.com ([198.47.19.12]:54830 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751797AbcKATWC (ORCPT ); Tue, 1 Nov 2016 15:22:02 -0400 Subject: Re: [PATCH v12 RESEND 0/4] generic TEE subsystem To: Mark Brown References: <1477649984-16777-1-git-send-email-jens.wiklander@linaro.org> <1e532aeb-4944-62e4-c8c4-1e23438b92cd@ti.com> <20161028181914.xkse5orwwp42dvj3@sirena.org.uk> CC: Jens Wiklander , , , , Greg Kroah-Hartman , Al Viro , , , , , Jason Gunthorpe , Mark Rutland , Michal Simek , Rob Herring , Will Deacon , Arnd Bergmann , Nishanth Menon From: "Andrew F. Davis" Message-ID: <4eb80778-cfe3-f4c0-d1ee-0d798c8ddd35@ti.com> Date: Tue, 1 Nov 2016 14:20:58 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20161028181914.xkse5orwwp42dvj3@sirena.org.uk> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 TEE to add to this subsystem >> before merging? > > We haven't been overburneded with TEE vendors wanting to get their > driver code into mainline - do we have any reasonable prospect of other > TEE vendors with an interest in mainline turning up in any kind of > reasonable timeframe? > Doesn't look like anyone has near-term plans for upstreaming non-OPTEE TEEs, we don't at least (TI), so I guess I see no reason right now to delay upstreaming of this TEE's driver on the off-chance it is incompatible with a TEE that may or may not try to get upstreamed later. I'll redact my objection for now. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew F. Davis" Subject: Re: [PATCH v12 RESEND 0/4] generic TEE subsystem Date: Tue, 1 Nov 2016 14:20:58 -0500 Message-ID: <4eb80778-cfe3-f4c0-d1ee-0d798c8ddd35@ti.com> References: <1477649984-16777-1-git-send-email-jens.wiklander@linaro.org> <1e532aeb-4944-62e4-c8c4-1e23438b92cd@ti.com> <20161028181914.xkse5orwwp42dvj3@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20161028181914.xkse5orwwp42dvj3-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Brown Cc: Jens Wiklander , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Greg Kroah-Hartman , Al Viro , valentin.manea-hv44wF8Li93QT0dZR+AlfA@public.gmane.org, jean-michel.delorme-qxv4g6HH51o@public.gmane.org, emmanuel.michel-qxv4g6HH51o@public.gmane.org, javier-5MUHepqpBA1BDgjK7y7TUQ@public.gmane.org, Jason Gunthorpe , Mark Rutland , Michal Simek , Rob Herring , Will Deacon , Arnd Bergmann , Nishanth Menon List-Id: devicetree@vger.kernel.org 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 TEE to add to this subsystem >> before merging? > > We haven't been overburneded with TEE vendors wanting to get their > driver code into mainline - do we have any reasonable prospect of other > TEE vendors with an interest in mainline turning up in any kind of > reasonable timeframe? > Doesn't look like anyone has near-term plans for upstreaming non-OPTEE TEEs, we don't at least (TI), so I guess I see no reason right now to delay upstreaming of this TEE's driver on the off-chance it is incompatible with a TEE that may or may not try to get upstreamed later. I'll redact my objection for now. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: afd@ti.com (Andrew F. Davis) Date: Tue, 1 Nov 2016 14:20:58 -0500 Subject: [PATCH v12 RESEND 0/4] generic TEE subsystem In-Reply-To: <20161028181914.xkse5orwwp42dvj3@sirena.org.uk> References: <1477649984-16777-1-git-send-email-jens.wiklander@linaro.org> <1e532aeb-4944-62e4-c8c4-1e23438b92cd@ti.com> <20161028181914.xkse5orwwp42dvj3@sirena.org.uk> Message-ID: <4eb80778-cfe3-f4c0-d1ee-0d798c8ddd35@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 TEE to add to this subsystem >> before merging? > > We haven't been overburneded with TEE vendors wanting to get their > driver code into mainline - do we have any reasonable prospect of other > TEE vendors with an interest in mainline turning up in any kind of > reasonable timeframe? > Doesn't look like anyone has near-term plans for upstreaming non-OPTEE TEEs, we don't at least (TI), so I guess I see no reason right now to delay upstreaming of this TEE's driver on the off-chance it is incompatible with a TEE that may or may not try to get upstreamed later. I'll redact my objection for now.