On Wed, Jan 25, 2017 at 11:02 AM, Greg Kroah-Hartman
[off-list ref] wrote:

On Wed, Jan 25, 2017 at 10:47:45AM +0100, Jens Wiklander wrote:

quoted

On Tue, Jan 24, 2017 at 01:53:30PM +0100, Jens Wiklander wrote:

quoted

/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