You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currenttly, the treble architecture of Android P, have a lot of restrictions . for example, libary linker, socket between system and vendor .
Once a system service want to use the op-tee client api, it will face the problem.Maybe we can use hidl service to deal with this . But it still will be some problem about sharememory and struction inforation which need to be passed between process.
I notice op-tee is doing some work about the AOSP . Will you have a plan to design a standard hidl interface for the gp client api?
Thanks
The text was updated successfully, but these errors were encountered:
dracular1983
changed the title
About how can Android system application use optee client API in the feature
About how can Android system application use optee client API in the future
Apr 12, 2018
I'm not sure if treble applies here? Treble defines a standard interface for the hardware/hal (vendor) but the client api lives above the OS framework.
Hi All,
Currenttly, the treble architecture of Android P, have a lot of restrictions . for example, libary linker, socket between system and vendor .
Once a system service want to use the op-tee client api, it will face the problem.Maybe we can use hidl service to deal with this . But it still will be some problem about sharememory and struction inforation which need to be passed between process.
I notice op-tee is doing some work about the AOSP . Will you have a plan to design a standard hidl interface for the gp client api?
Thanks
The text was updated successfully, but these errors were encountered: