Re: [Tee-dev] [PATCHv3 2/3] optee: use uuid for sysfs driver entry
From: Sumit Garg
Date: Tue May 26 2020 - 06:37:49 EST
On Mon, 25 May 2020 at 21:24, Jerome Forissier <jerome@xxxxxxxxxxxxx> wrote:
> On 5/25/20 3:36 PM, Maxim Uvarov wrote:
> > On Mon, 25 May 2020 at 15:10, Jerome Forissier <jerome@xxxxxxxxxxxxx> wrote:
> >> On 5/25/20 1:52 PM, Maxim Uvarov wrote:
> >>> Optee device names for sysfs needed to be unique
> >> s/Optee/OP-TEE/
> >> s/needed/need/
> >>> and it's better if they will mean something. UUID for name
> >>> looks like good solution:
> >>> /sys/bus/tee/devices/optee-clnt-<uuid>
> >> How about mentioning it is the UUID of the Trusted Application on the
> >> TEE side?
> > Jerome, do you think optee-ta-<uuid> is more suitable here?
> Yes, a bit better I think. More "self explanatory"... kind of :)
> Is it possible to have several devices bound to the same TA? I think
> nothing forbids this although we may not have any use case for now...
A single TA is represented via a single device represented via UUID on
the TEE bus. And I can't think of a scenario where the user may not
want to split the TA so as to support a particular driver in Linux.
> Tee-dev mailing list