Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About how can Android system application use optee client API in the future #120

Closed
dracular1983 opened this issue Apr 12, 2018 · 2 comments

Comments

@dracular1983
Copy link

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

@dracular1983 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
@vchong
Copy link

vchong commented Apr 12, 2018

Hi,

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.

You'd just use JNI to call the api from the apks. See linaro-swg/optee_android_manifest#31 for some discussions about it.

@vchong
Copy link

vchong commented Apr 13, 2018

Continue discussion on linaro-swg/optee_android_manifest#31. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants