Re: [PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run

On Sun, 24 May 2020 at 09:22, Jens Wiklander wrote: > > Hi Maxim, > > On Thu, May 21, 2020 at 8:47 AM Maxim Uvarov wrote: > > > > Some drivers (like ftpm) can operate only after tee-supplicant > > runs becase of tee-supplicant provides things like storage > > services. This patch splits probe

Re: [PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run

Hi Maxim, On Thu, May 21, 2020 at 8:47 AM Maxim Uvarov wrote: > > Some drivers (like ftpm) can operate only after tee-supplicant > runs becase of tee-supplicant provides things like storage > services. This patch splits probe of non tee-supplicant dependable > drivers to early stage, and after

Re: [PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run

On Fri, 22 May 2020 at 14:40, Sumit Garg wrote: > > Hi Maxim, > > On Thu, 21 May 2020 at 12:17, Maxim Uvarov wrote: > > > > Some drivers (like ftpm) can operate only after tee-supplicant > > runs becase of tee-supplicant provides things like storage > > services. This patch splits probe of non

Re: [PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run

Hi Maxim, On Thu, 21 May 2020 at 12:17, Maxim Uvarov wrote: > > Some drivers (like ftpm) can operate only after tee-supplicant > runs becase of tee-supplicant provides things like storage > services. This patch splits probe of non tee-supplicant dependable > drivers to early stage, and after

[PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run

Some drivers (like ftpm) can operate only after tee-supplicant runs becase of tee-supplicant provides things like storage services. This patch splits probe of non tee-supplicant dependable drivers to early stage, and after tee-supplicant run probe other drivers. Signed-off-by: Maxim Uvarov