From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752178AbdAYLDk (ORCPT ); Wed, 25 Jan 2017 06:03:40 -0500 Received: from mail-ot0-f196.google.com ([74.125.82.196]:35390 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751976AbdAYLDi (ORCPT ); Wed, 25 Jan 2017 06:03:38 -0500 MIME-Version: 1.0 In-Reply-To: <20170125100252.GA8889@kroah.com> References: <1484744296-30003-1-git-send-email-jens.wiklander@linaro.org> <8183743.bSJXZpMh95@wuerfel> <20170123090852.GB1910@jax> <5564439.UZohRc66aK@wuerfel> <20170124125330.GA30998@jax> <20170125094744.GA7121@jax> <20170125100252.GA8889@kroah.com> From: Arnd Bergmann Date: Wed, 25 Jan 2017 12:03:37 +0100 X-Google-Sender-Auth: eY1MKEuYyy80YilOI4c3aEWKJoo Message-ID: Subject: Re: [PATCH v14 3/5] tee: add OP-TEE driver To: Greg Kroah-Hartman Cc: Jens Wiklander , Olof Johansson , Andrew Morton , Wei Xu , Linux Kernel Mailing List , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Al Viro , valentin.manea@huawei.com, jean-michel.delorme@st.com, emmanuel.michel@st.com, javier@javigon.com, Jason Gunthorpe , Mark Rutland , Michal Simek , Rob Herring , Will Deacon , Nishanth Menon , "Andrew F . Davis" , Mark Brown , scott.branden@broadcom.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 25, 2017 at 11:02 AM, Greg Kroah-Hartman wrote: > On Wed, Jan 25, 2017 at 10:47:45AM +0100, Jens Wiklander wrote: >> On Tue, Jan 24, 2017 at 01:53:30PM +0100, Jens Wiklander wrote: >> > >> > /sys/class/tee/ sounds good, I'll use that. It's more or less what we >> > also have today. >> >> I'm sorry, it seems a struct device has to be used in order to put stuff >> under /sys/class/tee/. Or am I missing something? > > Nope, that is correct. But that's a different device: this device represents the "class" of device for the user space interface, nothing wrong with that. However, we don't need both the class device and a platform device that is made up by the optee driver for a firmware feature to represent the same entity that we have the class device for. Arnd