[lkml]   [2018]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH 0/2] allow optee to be exposed on ACPI systems
Similar to how OP-TEE is exposed as a pseudo device under /firmware/optee
on DT systems, permit OP-TEE presence to be exposed via a device object
in the ACPI namespace. This makes it possible to model the OP-TEE interface
as a platform device gets instantiated automatically both on DT and ACPI
systems, and implement the driver as a platform driver that is able to
use the generic device properties API to access the 'method' attribute
as well as potential future extensions to the binding that introduce
new attributes.

What remains to be discussed is how to expose OP-TEE pseudo devices,
e.g., Sumit's RNG implementation on SynQuacer which we would like to
bind a Linux driver to.

Cc: Jens Wiklander <>
Cc: Sumit Garg <>
Cc: Graeme Gregory <>
Cc: Jerome Forissier <>

Ard Biesheuvel (2):
optee: model OP-TEE as a platform device/driver
optee: add ACPI support

drivers/tee/optee/core.c | 94 +++++++++-----------
1 file changed, 41 insertions(+), 53 deletions(-)


 \ /
  Last update: 2018-12-27 20:02    [W:0.052 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site