blob: 05a85b2226eb52c7132a6ae68610065ba85ba85d [file] [log] [blame]
Joakim Bech8e5c5b32018-10-25 08:18:32 +02001.. _linux_kernel:
2
3##########################
4Linux kernel TEE framework
5##########################
6
7.. todo::
8
9 Joakim: Jens to fill in information in the following sections. Eventually
10 this should be split up as two files, one under "Build and Run" and one
11 under "Architecture documentation".
12
13 History
14 - Refer to the patch when it was merged.
15 - Mention old and deprecated optee_linux driver.
16
17 Maintainer
18 - Jens and ... ?
19
20 Maillists
21 - Mention the get_maintainer script in kernel.
22 - Tee-dev? (:ref:`contact`).
23
24 Build instructions
25 - How to enable it in kernel
26
27 KConfig flags
28 - What flags to enable to run OP-TEE.
29 - Reference to :ref:`optee_benchmark`.
30
31 Device Tree
32 - What nodes/thing are important for OP-TEE.
33 - Are OP-TEE DT things upstream? If not, why?
34
35 TEE kernel Internal Client API
36 - What is it?
37 - How can I use it?
38 - Is it upstream? If not, why?
39
40 Differences between kernel.org and linaro-swg/linux
41 - Why do we have a separate fork?
42 - Features being developed.
43 - Not meant to go upstream.
44 - Should people send patches to the mailinglist or create PRs at
45 linaro-swg/linux?
46
47 External references
48 - (Links to) Documentation in the official kernel?