mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>, <valentin.manea@huawei.com>,
	<jean-michel.delorme@st.com>, <emmanuel.michel@st.com>,
	<javier@javigon.com>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Rob Herring <robh+dt@kernel.org>,
	Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
	Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v12 RESEND 0/4] generic TEE subsystem
Date: Tue, 1 Nov 2016 14:20:58 -0500	[thread overview]
Message-ID: <4eb80778-cfe3-f4c0-d1ee-0d798c8ddd35@ti.com> (raw)
In-Reply-To: <20161028181914.xkse5orwwp42dvj3@sirena.org.uk>

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.

  reply	other threads:[~2016-11-01 19:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 10:19 Jens Wiklander
2016-10-28 10:19 ` [PATCH v12 RESEND 1/4] dt/bindings: add bindings for optee Jens Wiklander
2016-10-28 10:19 ` [PATCH v12 RESEND 2/4] tee: generic TEE subsystem Jens Wiklander
2016-10-28 10:19 ` [PATCH v12 RESEND 3/4] tee: add OP-TEE driver Jens Wiklander
2016-10-28 10:19 ` [PATCH v12 RESEND 4/4] Documentation: tee subsystem and op-tee driver Jens Wiklander
2016-10-28 15:43 ` [PATCH v12 RESEND 0/4] generic TEE subsystem Andrew F. Davis
2016-10-28 18:19   ` Mark Brown
2016-11-01 19:20     ` Andrew F. Davis [this message]
2016-10-29  9:46   ` Jens Wiklander
2016-10-31 18:24     ` Andrew F. Davis
2016-11-03 19:35       ` Jens Wiklander
2016-11-03 19:52         ` Volodymyr Babchuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4eb80778-cfe3-f4c0-d1ee-0d798c8ddd35@ti.com \
    --to=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=emmanuel.michel@st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier@javigon.com \
    --cc=jean-michel.delorme@st.com \
    --cc=jens.wiklander@linaro.org \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=valentin.manea@huawei.com \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®