qcom_invoke_driver.txt 1.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. Introduction:
  2. =============
  3. Invoke driver is a misc driver which helps communication between non secure
  4. and secure world. Invoke driver communicates with secure side using SCM
  5. driver. To use invoke driver, open must be called on invoke device i.e.
  6. /dev/invoke. Invoke driver exposes only one IOCTL invoke which passes
  7. userspace request to TZ.
  8. SW Architecture
  9. ===============
  10. Following is SW stack for Invoke driver.
  11. +++++++++++++++++++++++++++++++++++++++++
  12. + Applications +
  13. +++++++++++++++++++++++++++++++++++++++++
  14. + System Layer +
  15. +++++++++++++++++++++++++++++++++++++++++
  16. + Kernel +
  17. + +++++++++++++++++++ +
  18. + + Invoke driver + +
  19. + +++++++++++++++++++ +
  20. + + SCM Driver + +
  21. +++++++++++++++++++++++++++++++++++++++++
  22. ||
  23. ||
  24. \/
  25. +++++++++++++++++++++++++++++++++++++++++
  26. + Trust Zone +
  27. + +++++++++++ +++++++++++ +
  28. + + TZ App1 + + TZ App2 + +
  29. +++++++++++++++++++++++++++++++++++++++++
  30. Interfaces
  31. ==========
  32. Invoke driver exposes INVOKE_IOCTL_INVOKE_REQ IOCTL for userspace to
  33. communicate with driver. More details of IOCTL are avilable in
  34. corresponding header file.
  35. Driver Parameters
  36. =================
  37. This driver is built and statically linked into the kernel; therefore,
  38. there are no module parameters supported by this driver.
  39. There are no kernel command line parameters supported by this driver.
  40. Power Management
  41. ================
  42. TBD
  43. Dependencies
  44. ============
  45. Invoke driver depends on SCM driver to communicate with TZ.