faq: add all content

Signed-off-by: Joakim Bech <joakim.bech@linaro.org>

architecture/porting_guidelines.rst

@@ -375,6 +375,8 @@ memory using TZASC (see plat_arm_security_setup_ in TF-A). The takeaway here is
 that you must make sure that you have configured whatever memory firewall your
 device has such that it has a secure and a non-secure memory area.
 
+.. _core_pub_priv_keypair:
+
 Trusted Application private/public keypair
 ******************************************
 By default all Trusted Applications (TA's) are signed with the pre-generated

building/trusted_applications.rst

@@ -106,6 +106,8 @@ A typical Makefile for a TA looks something like this
     # Source the TA-devkit make file
     include $(TA_DEV_KIT_DIR)/mk/ta_dev_kit.mk
 
+.. _build_trusted_applications_submk:
+
 sub.mk directives
 =================
 The make file expects that current directory contains a file ``sub.mk`` that is

debug/benchmark.rst

@@ -30,8 +30,8 @@ Benchmark framework consists of such components:
        which is responsible for allocating timestamp circular buffers,
        registering these buffers in the Benchmark PTA and consuming all
        timestamp data generated by all OP-TEE layers. Finally, it puts timestamp
-       data into appropriate file with ``.ts`` extension. Additional details can
-       be found here here optee_benchmark_.
+       data into appropriate file with ``.ts`` extension. Additional build
+       details can be found at :ref:`optee_benchmark`.
 
     2. **Benchmark Pseudo Trusted Application (PTA)**: which owns all per-cpu
        circular non-secure buffers from a shared memory. Benchmark PTA must be