| /arm-trusted-firmware-2.8.0/docs/perf/ |
| A D | tsp.rst | 8 called the TSPD. Therefore, if you intend to use the TSP, the BL31 image
13 Then to build the TSP image use:
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | coding-style.rst | 17 The source code must use the **UTF-8** character encoding. Comments and
18 documentation may use non-ASCII characters when required (e.g. Greek letters
31 Exceptions are made when referring directly to something that does not use
69 Use **tabs** for indentation. The use of spaces for indentation is forbidden
121 acceptable to use additional blank lines for clarity, if required.
172 For example, use the following style:
328 /* Single line comments can use this format */
356 All header files that are included by a source file must use the following,
398 including them, use the ``"..."`` variant.
401 is including them, use the ``<...>`` variant.
[all …]
|
| A D | commit-style.rst | 8 keep a more accurate changelog. You may use Markdown in commit messages.
39 The following example commit message demonstrates the use of the
87 While we don't enforce scopes strictly, we do ask that commits use these if they
90 It's highly recommended that you use the tooling installed by the optional steps
119 When creating new scopes, try to keep them short and succinct, and use kebab
121 platforms and some drivers) should use that name (e.g. ``gic600ae``,
122 ``flexspi``, ``stpmic1``), otherwise use a name that uniquely represents the
|
| A D | coding-guidelines.rst | 11 Many of the rules given below (such as indentation size, use of tabs, and
48 the remote master, use:
76 Avoid printf and use logging macros
160 | ``strcpy, wcscpy``, | Banned | use strlcpy instead |
163 | ``strcat, wcscat``, | Banned | use strlcat instead |
166 | ``sprintf, vsprintf`` | Banned | use snprintf, vsnprintf |
175 | ``strtok`` | Banned | use strtok_r or strsep instead |
351 - Where possible, use the built-in *C* data types for variable storage (for
370 systems. If a variable must be exactly 16-bit, use ``int16_t`` or
375 at least 64-bit, use ``long long``.
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | trusted-board-boot-build.rst | 14 is important to use a version that is compatible with TF-A and fixes any
17 version of mbed TLS to use.
35 By default, this will use the Chain of Trust described in the TBBR-client
36 document. To select a different one, use the ``COT`` build option.
57 - ``ARM_ROTPK_LOCATION=devel_rsa``: use the default hash located in
61 - ``ARM_ROTPK_LOCATION=devel_ecdsa``: use the default hash located in
|
| /arm-trusted-firmware-2.8.0/lib/compiler-rt/ |
| A D | LICENSE.TXT | 7 to use it under either license. As a contributor, you agree to allow your code
32 use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
63 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
88 other licenses gives permission to use the names of the LLVM Team or the
|
| /arm-trusted-firmware-2.8.0/docs/resources/diagrams/plantuml/ |
| A D | fconf_bl1_load_config.puml | 43 note over fconf: use statically defined policies in bl1
63 note over fconf: use statically defined policies in bl1
|
| A D | fconf_bl2_populate.puml | 44 note over arm_io_storage: use populated properties
|
| /arm-trusted-firmware-2.8.0/docs/about/ |
| A D | acknowledgements.rst | 10 use for new contributions.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/n1sdp/fdts/ |
| A D | n1sdp_tb_fw_config.dts | 22 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/rde1edge/fdts/ |
| A D | rde1edge_tb_fw_config.dts | 23 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/rdn1edge/fdts/ |
| A D | rdn1edge_tb_fw_config.dts | 22 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/rdn2/fdts/ |
| A D | rdn2_tb_fw_config.dts | 23 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/rdv1/fdts/ |
| A D | rdv1_tb_fw_config.dts | 23 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/rdv1mc/fdts/ |
| A D | rdv1mc_tb_fw_config.dts | 23 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/sgi575/fdts/ |
| A D | sgi575_tb_fw_config.dts | 23 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/include/drivers/brcm/ |
| A D | fru.h | 54 bool use; member
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/juno/fdts/ |
| A D | juno_tb_fw_config.dts | 21 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/morello/fdts/ |
| A D | morello_tb_fw_config.dts | 22 * BL2 in order to locate and re-use the heap.
|
| /arm-trusted-firmware-2.8.0/tools/marvell/doimage/secure/ |
| A D | sec_img_7K.cfg | 7 # use "*" string instead of file name for specifying an empty key
|
| A D | sec_img_8K.cfg | 7 # use "*" string instead of file name for specifying an empty key
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | qti-msm8916.rst | 17 make use of a proprietary binary components (QTISECLIB). It is fully
50 use KVM or another hypervisor. The entry address is fixed in the BL31 binary
55 from Qualcomm) are not directly supported, although it is possible to use an EL2
71 use e.g. `qtestsign`_::
|
| A D | rpi3.rst | 7 The following instructions explain how to use this port of the TF-A with the
42 This means that we can use the default AArch32 kernel provided in the official
171 use mailboxes to trap the secondary cores until they are ready to jump to the
175 Kernels with PSCI support can use the PSCI calls instead for a cleaner boot.
199 build folder (e.g. ``build/rpi3/debug/armstub8.bin``). To know how to use this
268 Please use the code from `here <https://github.com/OP-TEE/optee_os>`__.
275 Linux command line so that the USB driver doesn't use FIQs:
281 it. In order to use TBB, you might want to set ``GENERATE_COT=1`` to let the
314 Then compile TF-A. For a 32-bit kernel, use the following command line:
322 For a 64-bit kernel, use this other command line:
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | context_mgmt_rework.rst | 14 initialization and management routines for use by different components
52 firmware should only initialize the next immediate lower EL in use.
117 use by SPMD and RMMD. The details of this can be worked out during
125 execution and would need to use sysregs of lower EL (eg: PAuth, pmcr) to enable
156 There is also the case that when EL3 would like to make use of some
159 use of Pointer Authentication (PAuth) feature, it needs to program
163 or use of SP_EL0 for C Runtime Stack at EL3.
182 Having this framework in place will allow Root world to make use of lower EL
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/ |
| A D | arm-build-options.rst | 20 By default, Arm platforms use a watchdog to trigger a system reset in case
46 State-ID yet. Hence this flag is used to configure whether to use the
63 ``arm_rotpk_rsa.der``, located in ``plat/arm/board/common/rotpk``. To use
69 use this option, ``arm_rotprivk_ecdsa.pem`` must be specified as
95 configure an Arm® Ethos™-N NPU. To use this service the target platform's
133 then TF-A will detect if an earlier version is in use. Default is 1.
|