Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1 | Trusted Firmware-A Porting Guide |
| 2 | ================================ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 3 | |
| 4 | |
| 5 | .. section-numbering:: |
| 6 | :suffix: . |
| 7 | |
| 8 | .. contents:: |
| 9 | |
| 10 | -------------- |
| 11 | |
| 12 | Introduction |
| 13 | ------------ |
| 14 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 15 | Porting Trusted Firmware-A (TF-A) to a new platform involves making some |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 16 | mandatory and optional modifications for both the cold and warm boot paths. |
| 17 | Modifications consist of: |
| 18 | |
| 19 | - Implementing a platform-specific function or variable, |
| 20 | - Setting up the execution context in a certain way, or |
| 21 | - Defining certain constants (for example #defines). |
| 22 | |
| 23 | The platform-specific functions and variables are declared in |
| 24 | `include/plat/common/platform.h`_. The firmware provides a default implementation |
| 25 | of variables and functions to fulfill the optional requirements. These |
| 26 | implementations are all weakly defined; they are provided to ease the porting |
| 27 | effort. Each platform port can override them with its own implementation if the |
| 28 | default implementation is inadequate. |
| 29 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 30 | Some modifications are common to all Boot Loader (BL) stages. Section 2 |
| 31 | discusses these in detail. The subsequent sections discuss the remaining |
| 32 | modifications for each BL stage in detail. |
| 33 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 34 | This document should be read in conjunction with the TF-A `User Guide`_. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 35 | |
Soby Mathew | 6e93eef | 2018-09-26 11:17:23 +0100 | [diff] [blame] | 36 | Please refer to the `Platform compatibility policy`_ for the policy regarding |
| 37 | compatibility and deprecation of these porting interfaces. |
| 38 | |
Antonio Nino Diaz | 8f457da | 2019-02-13 14:07:38 +0000 | [diff] [blame] | 39 | Only Arm development platforms (such as FVP and Juno) may use the |
| 40 | functions/definitions in ``include/plat/arm/common/`` and the corresponding |
| 41 | source files in ``plat/arm/common/``. This is done so that there are no |
| 42 | dependencies between platforms maintained by different people/companies. If you |
| 43 | want to use any of the functionality present in ``plat/arm`` files, please |
| 44 | create a pull request that moves the code to ``plat/common`` so that it can be |
| 45 | discussed. |
| 46 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 47 | Common modifications |
| 48 | -------------------- |
| 49 | |
| 50 | This section covers the modifications that should be made by the platform for |
| 51 | each BL stage to correctly port the firmware stack. They are categorized as |
| 52 | either mandatory or optional. |
| 53 | |
| 54 | Common mandatory modifications |
| 55 | ------------------------------ |
| 56 | |
| 57 | A platform port must enable the Memory Management Unit (MMU) as well as the |
| 58 | instruction and data caches for each BL stage. Setting up the translation |
| 59 | tables is the responsibility of the platform port because memory maps differ |
| 60 | across platforms. A memory translation library (see ``lib/xlat_tables/``) is |
Sandrine Bailleux | de3d704 | 2017-07-20 16:11:01 +0100 | [diff] [blame] | 61 | provided to help in this setup. |
| 62 | |
| 63 | Note that although this library supports non-identity mappings, this is intended |
| 64 | only for re-mapping peripheral physical addresses and allows platforms with high |
| 65 | I/O addresses to reduce their virtual address space. All other addresses |
| 66 | corresponding to code and data must currently use an identity mapping. |
| 67 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 68 | Also, the only translation granule size supported in TF-A is 4KB, as various |
| 69 | parts of the code assume that is the case. It is not possible to switch to |
| 70 | 16 KB or 64 KB granule sizes at the moment. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 71 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 72 | In Arm standard platforms, each BL stage configures the MMU in the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 73 | platform-specific architecture setup function, ``blX_plat_arch_setup()``, and uses |
| 74 | an identity mapping for all addresses. |
| 75 | |
| 76 | If the build option ``USE_COHERENT_MEM`` is enabled, each platform can allocate a |
| 77 | block of identity mapped secure memory with Device-nGnRE attributes aligned to |
| 78 | page boundary (4K) for each BL stage. All sections which allocate coherent |
| 79 | memory are grouped under ``coherent_ram``. For ex: Bakery locks are placed in a |
| 80 | section identified by name ``bakery_lock`` inside ``coherent_ram`` so that its |
| 81 | possible for the firmware to place variables in it using the following C code |
| 82 | directive: |
| 83 | |
| 84 | :: |
| 85 | |
| 86 | __section("bakery_lock") |
| 87 | |
| 88 | Or alternatively the following assembler code directive: |
| 89 | |
| 90 | :: |
| 91 | |
| 92 | .section bakery_lock |
| 93 | |
| 94 | The ``coherent_ram`` section is a sum of all sections like ``bakery_lock`` which are |
| 95 | used to allocate any data structures that are accessed both when a CPU is |
| 96 | executing with its MMU and caches enabled, and when it's running with its MMU |
| 97 | and caches disabled. Examples are given below. |
| 98 | |
| 99 | The following variables, functions and constants must be defined by the platform |
| 100 | for the firmware to work correctly. |
| 101 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 102 | File : platform_def.h [mandatory] |
| 103 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 104 | |
| 105 | Each platform must ensure that a header file of this name is in the system |
Antonio Nino Diaz | 5e44781 | 2019-02-01 12:22:22 +0000 | [diff] [blame] | 106 | include path with the following constants defined. This will require updating |
| 107 | the list of ``PLAT_INCLUDES`` in the ``platform.mk`` file. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 108 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 109 | Platform ports may optionally use the file `include/plat/common/common_def.h`_, |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 110 | which provides typical values for some of the constants below. These values are |
| 111 | likely to be suitable for all platform ports. |
| 112 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 113 | - **#define : PLATFORM_LINKER_FORMAT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 114 | |
| 115 | Defines the linker format used by the platform, for example |
| 116 | ``elf64-littleaarch64``. |
| 117 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 118 | - **#define : PLATFORM_LINKER_ARCH** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 119 | |
| 120 | Defines the processor architecture for the linker by the platform, for |
| 121 | example ``aarch64``. |
| 122 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 123 | - **#define : PLATFORM_STACK_SIZE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 124 | |
| 125 | Defines the normal stack memory available to each CPU. This constant is used |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 126 | by `plat/common/aarch64/platform_mp_stack.S`_ and |
| 127 | `plat/common/aarch64/platform_up_stack.S`_. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 128 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 129 | - **define : CACHE_WRITEBACK_GRANULE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 130 | |
| 131 | Defines the size in bits of the largest cache line across all the cache |
| 132 | levels in the platform. |
| 133 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 134 | - **#define : FIRMWARE_WELCOME_STR** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 135 | |
| 136 | Defines the character string printed by BL1 upon entry into the ``bl1_main()`` |
| 137 | function. |
| 138 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 139 | - **#define : PLATFORM_CORE_COUNT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 140 | |
| 141 | Defines the total number of CPUs implemented by the platform across all |
| 142 | clusters in the system. |
| 143 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 144 | - **#define : PLAT_NUM_PWR_DOMAINS** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 145 | |
| 146 | Defines the total number of nodes in the power domain topology |
| 147 | tree at all the power domain levels used by the platform. |
| 148 | This macro is used by the PSCI implementation to allocate |
| 149 | data structures to represent power domain topology. |
| 150 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 151 | - **#define : PLAT_MAX_PWR_LVL** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 152 | |
| 153 | Defines the maximum power domain level that the power management operations |
| 154 | should apply to. More often, but not always, the power domain level |
| 155 | corresponds to affinity level. This macro allows the PSCI implementation |
| 156 | to know the highest power domain level that it should consider for power |
| 157 | management operations in the system that the platform implements. For |
| 158 | example, the Base AEM FVP implements two clusters with a configurable |
| 159 | number of CPUs and it reports the maximum power domain level as 1. |
| 160 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 161 | - **#define : PLAT_MAX_OFF_STATE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 162 | |
| 163 | Defines the local power state corresponding to the deepest power down |
| 164 | possible at every power domain level in the platform. The local power |
| 165 | states for each level may be sparsely allocated between 0 and this value |
| 166 | with 0 being reserved for the RUN state. The PSCI implementation uses this |
| 167 | value to initialize the local power states of the power domain nodes and |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 168 | to specify the requested power state for a PSCI_CPU_OFF call. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 169 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 170 | - **#define : PLAT_MAX_RET_STATE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 171 | |
| 172 | Defines the local power state corresponding to the deepest retention state |
| 173 | possible at every power domain level in the platform. This macro should be |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 174 | a value less than PLAT_MAX_OFF_STATE and greater than 0. It is used by the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 175 | PSCI implementation to distinguish between retention and power down local |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 176 | power states within PSCI_CPU_SUSPEND call. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 177 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 178 | - **#define : PLAT_MAX_PWR_LVL_STATES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 179 | |
| 180 | Defines the maximum number of local power states per power domain level |
| 181 | that the platform supports. The default value of this macro is 2 since |
| 182 | most platforms just support a maximum of two local power states at each |
| 183 | power domain level (power-down and retention). If the platform needs to |
| 184 | account for more local power states, then it must redefine this macro. |
| 185 | |
| 186 | Currently, this macro is used by the Generic PSCI implementation to size |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 187 | the array used for PSCI_STAT_COUNT/RESIDENCY accounting. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 188 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 189 | - **#define : BL1_RO_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 190 | |
| 191 | Defines the base address in secure ROM where BL1 originally lives. Must be |
| 192 | aligned on a page-size boundary. |
| 193 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 194 | - **#define : BL1_RO_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 195 | |
| 196 | Defines the maximum address in secure ROM that BL1's actual content (i.e. |
| 197 | excluding any data section allocated at runtime) can occupy. |
| 198 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 199 | - **#define : BL1_RW_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 200 | |
| 201 | Defines the base address in secure RAM where BL1's read-write data will live |
| 202 | at runtime. Must be aligned on a page-size boundary. |
| 203 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 204 | - **#define : BL1_RW_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 205 | |
| 206 | Defines the maximum address in secure RAM that BL1's read-write data can |
| 207 | occupy at runtime. |
| 208 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 209 | - **#define : BL2_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 210 | |
| 211 | Defines the base address in secure RAM where BL1 loads the BL2 binary image. |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 212 | Must be aligned on a page-size boundary. This constant is not applicable |
| 213 | when BL2_IN_XIP_MEM is set to '1'. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 214 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 215 | - **#define : BL2_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 216 | |
| 217 | Defines the maximum address in secure RAM that the BL2 image can occupy. |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 218 | This constant is not applicable when BL2_IN_XIP_MEM is set to '1'. |
| 219 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 220 | - **#define : BL2_RO_BASE** |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 221 | |
| 222 | Defines the base address in secure XIP memory where BL2 RO section originally |
| 223 | lives. Must be aligned on a page-size boundary. This constant is only needed |
| 224 | when BL2_IN_XIP_MEM is set to '1'. |
| 225 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 226 | - **#define : BL2_RO_LIMIT** |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 227 | |
| 228 | Defines the maximum address in secure XIP memory that BL2's actual content |
| 229 | (i.e. excluding any data section allocated at runtime) can occupy. This |
| 230 | constant is only needed when BL2_IN_XIP_MEM is set to '1'. |
| 231 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 232 | - **#define : BL2_RW_BASE** |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 233 | |
| 234 | Defines the base address in secure RAM where BL2's read-write data will live |
| 235 | at runtime. Must be aligned on a page-size boundary. This constant is only |
| 236 | needed when BL2_IN_XIP_MEM is set to '1'. |
| 237 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 238 | - **#define : BL2_RW_LIMIT** |
Jiafei Pan | 7d173fc | 2018-03-21 07:20:09 +0000 | [diff] [blame] | 239 | |
| 240 | Defines the maximum address in secure RAM that BL2's read-write data can |
| 241 | occupy at runtime. This constant is only needed when BL2_IN_XIP_MEM is set |
| 242 | to '1'. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 243 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 244 | - **#define : BL31_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 245 | |
| 246 | Defines the base address in secure RAM where BL2 loads the BL31 binary |
| 247 | image. Must be aligned on a page-size boundary. |
| 248 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 249 | - **#define : BL31_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 250 | |
| 251 | Defines the maximum address in secure RAM that the BL31 image can occupy. |
| 252 | |
| 253 | For every image, the platform must define individual identifiers that will be |
| 254 | used by BL1 or BL2 to load the corresponding image into memory from non-volatile |
| 255 | storage. For the sake of performance, integer numbers will be used as |
| 256 | identifiers. The platform will use those identifiers to return the relevant |
| 257 | information about the image to be loaded (file handler, load address, |
| 258 | authentication information, etc.). The following image identifiers are |
| 259 | mandatory: |
| 260 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 261 | - **#define : BL2_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 262 | |
| 263 | BL2 image identifier, used by BL1 to load BL2. |
| 264 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 265 | - **#define : BL31_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 266 | |
| 267 | BL31 image identifier, used by BL2 to load BL31. |
| 268 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 269 | - **#define : BL33_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 270 | |
| 271 | BL33 image identifier, used by BL2 to load BL33. |
| 272 | |
| 273 | If Trusted Board Boot is enabled, the following certificate identifiers must |
| 274 | also be defined: |
| 275 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 276 | - **#define : TRUSTED_BOOT_FW_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 277 | |
| 278 | BL2 content certificate identifier, used by BL1 to load the BL2 content |
| 279 | certificate. |
| 280 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 281 | - **#define : TRUSTED_KEY_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 282 | |
| 283 | Trusted key certificate identifier, used by BL2 to load the trusted key |
| 284 | certificate. |
| 285 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 286 | - **#define : SOC_FW_KEY_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 287 | |
| 288 | BL31 key certificate identifier, used by BL2 to load the BL31 key |
| 289 | certificate. |
| 290 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 291 | - **#define : SOC_FW_CONTENT_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 292 | |
| 293 | BL31 content certificate identifier, used by BL2 to load the BL31 content |
| 294 | certificate. |
| 295 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 296 | - **#define : NON_TRUSTED_FW_KEY_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 297 | |
| 298 | BL33 key certificate identifier, used by BL2 to load the BL33 key |
| 299 | certificate. |
| 300 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 301 | - **#define : NON_TRUSTED_FW_CONTENT_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 302 | |
| 303 | BL33 content certificate identifier, used by BL2 to load the BL33 content |
| 304 | certificate. |
| 305 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 306 | - **#define : FWU_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 307 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 308 | Firmware Update (FWU) certificate identifier, used by NS_BL1U to load the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 309 | FWU content certificate. |
| 310 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 311 | - **#define : PLAT_CRYPTOCELL_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 312 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 313 | This defines the base address of Arm® TrustZone® CryptoCell and must be |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 314 | defined if CryptoCell crypto driver is used for Trusted Board Boot. For |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 315 | capable Arm platforms, this driver is used if ``ARM_CRYPTOCELL_INTEG`` is |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 316 | set. |
| 317 | |
| 318 | If the AP Firmware Updater Configuration image, BL2U is used, the following |
| 319 | must also be defined: |
| 320 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 321 | - **#define : BL2U_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 322 | |
| 323 | Defines the base address in secure memory where BL1 copies the BL2U binary |
| 324 | image. Must be aligned on a page-size boundary. |
| 325 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 326 | - **#define : BL2U_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 327 | |
| 328 | Defines the maximum address in secure memory that the BL2U image can occupy. |
| 329 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 330 | - **#define : BL2U_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 331 | |
| 332 | BL2U image identifier, used by BL1 to fetch an image descriptor |
| 333 | corresponding to BL2U. |
| 334 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 335 | If the SCP Firmware Update Configuration Image, SCP_BL2U is used, the following |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 336 | must also be defined: |
| 337 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 338 | - **#define : SCP_BL2U_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 339 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 340 | SCP_BL2U image identifier, used by BL1 to fetch an image descriptor |
| 341 | corresponding to SCP_BL2U. |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 342 | NOTE: TF-A does not provide source code for this image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 343 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 344 | If the Non-Secure Firmware Updater ROM, NS_BL1U is used, the following must |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 345 | also be defined: |
| 346 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 347 | - **#define : NS_BL1U_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 348 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 349 | Defines the base address in non-secure ROM where NS_BL1U executes. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 350 | Must be aligned on a page-size boundary. |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 351 | NOTE: TF-A does not provide source code for this image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 352 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 353 | - **#define : NS_BL1U_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 354 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 355 | NS_BL1U image identifier, used by BL1 to fetch an image descriptor |
| 356 | corresponding to NS_BL1U. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 357 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 358 | If the Non-Secure Firmware Updater, NS_BL2U is used, the following must also |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 359 | be defined: |
| 360 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 361 | - **#define : NS_BL2U_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 362 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 363 | Defines the base address in non-secure memory where NS_BL2U executes. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 364 | Must be aligned on a page-size boundary. |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 365 | NOTE: TF-A does not provide source code for this image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 366 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 367 | - **#define : NS_BL2U_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 368 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 369 | NS_BL2U image identifier, used by BL1 to fetch an image descriptor |
| 370 | corresponding to NS_BL2U. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 371 | |
| 372 | For the the Firmware update capability of TRUSTED BOARD BOOT, the following |
| 373 | macros may also be defined: |
| 374 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 375 | - **#define : PLAT_FWU_MAX_SIMULTANEOUS_IMAGES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 376 | |
| 377 | Total number of images that can be loaded simultaneously. If the platform |
| 378 | doesn't specify any value, it defaults to 10. |
| 379 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 380 | If a SCP_BL2 image is supported by the platform, the following constants must |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 381 | also be defined: |
| 382 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 383 | - **#define : SCP_BL2_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 384 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 385 | SCP_BL2 image identifier, used by BL2 to load SCP_BL2 into secure memory |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 386 | from platform storage before being transferred to the SCP. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 387 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 388 | - **#define : SCP_FW_KEY_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 389 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 390 | SCP_BL2 key certificate identifier, used by BL2 to load the SCP_BL2 key |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 391 | certificate (mandatory when Trusted Board Boot is enabled). |
| 392 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 393 | - **#define : SCP_FW_CONTENT_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 394 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 395 | SCP_BL2 content certificate identifier, used by BL2 to load the SCP_BL2 |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 396 | content certificate (mandatory when Trusted Board Boot is enabled). |
| 397 | |
| 398 | If a BL32 image is supported by the platform, the following constants must |
| 399 | also be defined: |
| 400 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 401 | - **#define : BL32_IMAGE_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 402 | |
| 403 | BL32 image identifier, used by BL2 to load BL32. |
| 404 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 405 | - **#define : TRUSTED_OS_FW_KEY_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 406 | |
| 407 | BL32 key certificate identifier, used by BL2 to load the BL32 key |
| 408 | certificate (mandatory when Trusted Board Boot is enabled). |
| 409 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 410 | - **#define : TRUSTED_OS_FW_CONTENT_CERT_ID** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 411 | |
| 412 | BL32 content certificate identifier, used by BL2 to load the BL32 content |
| 413 | certificate (mandatory when Trusted Board Boot is enabled). |
| 414 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 415 | - **#define : BL32_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 416 | |
| 417 | Defines the base address in secure memory where BL2 loads the BL32 binary |
| 418 | image. Must be aligned on a page-size boundary. |
| 419 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 420 | - **#define : BL32_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 421 | |
| 422 | Defines the maximum address that the BL32 image can occupy. |
| 423 | |
| 424 | If the Test Secure-EL1 Payload (TSP) instantiation of BL32 is supported by the |
| 425 | platform, the following constants must also be defined: |
| 426 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 427 | - **#define : TSP_SEC_MEM_BASE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 428 | |
| 429 | Defines the base address of the secure memory used by the TSP image on the |
| 430 | platform. This must be at the same address or below ``BL32_BASE``. |
| 431 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 432 | - **#define : TSP_SEC_MEM_SIZE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 433 | |
| 434 | Defines the size of the secure memory used by the BL32 image on the |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 435 | platform. ``TSP_SEC_MEM_BASE`` and ``TSP_SEC_MEM_SIZE`` must fully |
| 436 | accommodate the memory required by the BL32 image, defined by ``BL32_BASE`` |
| 437 | and ``BL32_LIMIT``. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 438 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 439 | - **#define : TSP_IRQ_SEC_PHY_TIMER** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 440 | |
| 441 | Defines the ID of the secure physical generic timer interrupt used by the |
| 442 | TSP's interrupt handling code. |
| 443 | |
| 444 | If the platform port uses the translation table library code, the following |
| 445 | constants must also be defined: |
| 446 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 447 | - **#define : PLAT_XLAT_TABLES_DYNAMIC** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 448 | |
| 449 | Optional flag that can be set per-image to enable the dynamic allocation of |
| 450 | regions even when the MMU is enabled. If not defined, only static |
| 451 | functionality will be available, if defined and set to 1 it will also |
| 452 | include the dynamic functionality. |
| 453 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 454 | - **#define : MAX_XLAT_TABLES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 455 | |
| 456 | Defines the maximum number of translation tables that are allocated by the |
| 457 | translation table library code. To minimize the amount of runtime memory |
| 458 | used, choose the smallest value needed to map the required virtual addresses |
| 459 | for each BL stage. If ``PLAT_XLAT_TABLES_DYNAMIC`` flag is enabled for a BL |
| 460 | image, ``MAX_XLAT_TABLES`` must be defined to accommodate the dynamic regions |
| 461 | as well. |
| 462 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 463 | - **#define : MAX_MMAP_REGIONS** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 464 | |
| 465 | Defines the maximum number of regions that are allocated by the translation |
| 466 | table library code. A region consists of physical base address, virtual base |
| 467 | address, size and attributes (Device/Memory, RO/RW, Secure/Non-Secure), as |
| 468 | defined in the ``mmap_region_t`` structure. The platform defines the regions |
| 469 | that should be mapped. Then, the translation table library will create the |
| 470 | corresponding tables and descriptors at runtime. To minimize the amount of |
| 471 | runtime memory used, choose the smallest value needed to register the |
| 472 | required regions for each BL stage. If ``PLAT_XLAT_TABLES_DYNAMIC`` flag is |
| 473 | enabled for a BL image, ``MAX_MMAP_REGIONS`` must be defined to accommodate |
| 474 | the dynamic regions as well. |
| 475 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 476 | - **#define : PLAT_VIRT_ADDR_SPACE_SIZE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 477 | |
| 478 | Defines the total size of the virtual address space in bytes. For example, |
David Cunado | 5724481 | 2018-02-16 21:12:58 +0000 | [diff] [blame] | 479 | for a 32 bit virtual address space, this value should be ``(1ULL << 32)``. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 480 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 481 | - **#define : PLAT_PHY_ADDR_SPACE_SIZE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 482 | |
| 483 | Defines the total size of the physical address space in bytes. For example, |
David Cunado | 5724481 | 2018-02-16 21:12:58 +0000 | [diff] [blame] | 484 | for a 32 bit physical address space, this value should be ``(1ULL << 32)``. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 485 | |
| 486 | If the platform port uses the IO storage framework, the following constants |
| 487 | must also be defined: |
| 488 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 489 | - **#define : MAX_IO_DEVICES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 490 | |
| 491 | Defines the maximum number of registered IO devices. Attempting to register |
| 492 | more devices than this value using ``io_register_device()`` will fail with |
| 493 | -ENOMEM. |
| 494 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 495 | - **#define : MAX_IO_HANDLES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 496 | |
| 497 | Defines the maximum number of open IO handles. Attempting to open more IO |
| 498 | entities than this value using ``io_open()`` will fail with -ENOMEM. |
| 499 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 500 | - **#define : MAX_IO_BLOCK_DEVICES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 501 | |
| 502 | Defines the maximum number of registered IO block devices. Attempting to |
| 503 | register more devices this value using ``io_dev_open()`` will fail |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 504 | with -ENOMEM. MAX_IO_BLOCK_DEVICES should be less than MAX_IO_DEVICES. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 505 | With this macro, multiple block devices could be supported at the same |
| 506 | time. |
| 507 | |
| 508 | If the platform needs to allocate data within the per-cpu data framework in |
| 509 | BL31, it should define the following macro. Currently this is only required if |
| 510 | the platform decides not to use the coherent memory section by undefining the |
| 511 | ``USE_COHERENT_MEM`` build flag. In this case, the framework allocates the |
| 512 | required memory within the the per-cpu data to minimize wastage. |
| 513 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 514 | - **#define : PLAT_PCPU_DATA_SIZE** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 515 | |
| 516 | Defines the memory (in bytes) to be reserved within the per-cpu data |
| 517 | structure for use by the platform layer. |
| 518 | |
| 519 | The following constants are optional. They should be defined when the platform |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 520 | memory layout implies some image overlaying like in Arm standard platforms. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 521 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 522 | - **#define : BL31_PROGBITS_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 523 | |
| 524 | Defines the maximum address in secure RAM that the BL31's progbits sections |
| 525 | can occupy. |
| 526 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 527 | - **#define : TSP_PROGBITS_LIMIT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 528 | |
| 529 | Defines the maximum address that the TSP's progbits sections can occupy. |
| 530 | |
| 531 | If the platform port uses the PL061 GPIO driver, the following constant may |
| 532 | optionally be defined: |
| 533 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 534 | - **PLAT_PL061_MAX_GPIOS** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 535 | Maximum number of GPIOs required by the platform. This allows control how |
| 536 | much memory is allocated for PL061 GPIO controllers. The default value is |
| 537 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 538 | #. $(eval $(call add_define,PLAT_PL061_MAX_GPIOS)) |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 539 | |
| 540 | If the platform port uses the partition driver, the following constant may |
| 541 | optionally be defined: |
| 542 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 543 | - **PLAT_PARTITION_MAX_ENTRIES** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 544 | Maximum number of partition entries required by the platform. This allows |
| 545 | control how much memory is allocated for partition entries. The default |
| 546 | value is 128. |
| 547 | `For example, define the build flag in platform.mk`_: |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 548 | PLAT_PARTITION_MAX_ENTRIES := 12 |
| 549 | $(eval $(call add_define,PLAT_PARTITION_MAX_ENTRIES)) |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 550 | |
| 551 | The following constant is optional. It should be defined to override the default |
| 552 | behaviour of the ``assert()`` function (for example, to save memory). |
| 553 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 554 | - **PLAT_LOG_LEVEL_ASSERT** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 555 | If ``PLAT_LOG_LEVEL_ASSERT`` is higher or equal than ``LOG_LEVEL_VERBOSE``, |
| 556 | ``assert()`` prints the name of the file, the line number and the asserted |
| 557 | expression. Else if it is higher than ``LOG_LEVEL_INFO``, it prints the file |
| 558 | name and the line number. Else if it is lower than ``LOG_LEVEL_INFO``, it |
| 559 | doesn't print anything to the console. If ``PLAT_LOG_LEVEL_ASSERT`` isn't |
| 560 | defined, it defaults to ``LOG_LEVEL``. |
| 561 | |
Dimitris Papastamos | 59902b7 | 2017-12-13 10:54:37 +0000 | [diff] [blame] | 562 | If the platform port uses the Activity Monitor Unit, the following constants |
| 563 | may be defined: |
| 564 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 565 | - **PLAT_AMU_GROUP1_COUNTERS_MASK** |
Dimitris Papastamos | 59902b7 | 2017-12-13 10:54:37 +0000 | [diff] [blame] | 566 | This mask reflects the set of group counters that should be enabled. The |
| 567 | maximum number of group 1 counters supported by AMUv1 is 16 so the mask |
| 568 | can be at most 0xffff. If the platform does not define this mask, no group 1 |
| 569 | counters are enabled. If the platform defines this mask, the following |
| 570 | constant needs to also be defined. |
| 571 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 572 | - **PLAT_AMU_GROUP1_NR_COUNTERS** |
Dimitris Papastamos | 59902b7 | 2017-12-13 10:54:37 +0000 | [diff] [blame] | 573 | This value is used to allocate an array to save and restore the counters |
| 574 | specified by ``PLAT_AMU_GROUP1_COUNTERS_MASK`` on CPU suspend. |
| 575 | This value should be equal to the highest bit position set in the |
| 576 | mask, plus 1. The maximum number of group 1 counters in AMUv1 is 16. |
| 577 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 578 | File : plat_macros.S [mandatory] |
| 579 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 580 | |
| 581 | Each platform must ensure a file of this name is in the system include path with |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 582 | the following macro defined. In the Arm development platforms, this file is |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 583 | found in ``plat/arm/board/<plat_name>/include/plat_macros.S``. |
| 584 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 585 | - **Macro : plat_crash_print_regs** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 586 | |
| 587 | This macro allows the crash reporting routine to print relevant platform |
| 588 | registers in case of an unhandled exception in BL31. This aids in debugging |
| 589 | and this macro can be defined to be empty in case register reporting is not |
| 590 | desired. |
| 591 | |
| 592 | For instance, GIC or interconnect registers may be helpful for |
| 593 | troubleshooting. |
| 594 | |
| 595 | Handling Reset |
| 596 | -------------- |
| 597 | |
| 598 | BL1 by default implements the reset vector where execution starts from a cold |
| 599 | or warm boot. BL31 can be optionally set as a reset vector using the |
| 600 | ``RESET_TO_BL31`` make variable. |
| 601 | |
| 602 | For each CPU, the reset vector code is responsible for the following tasks: |
| 603 | |
| 604 | #. Distinguishing between a cold boot and a warm boot. |
| 605 | |
| 606 | #. In the case of a cold boot and the CPU being a secondary CPU, ensuring that |
| 607 | the CPU is placed in a platform-specific state until the primary CPU |
| 608 | performs the necessary steps to remove it from this state. |
| 609 | |
| 610 | #. In the case of a warm boot, ensuring that the CPU jumps to a platform- |
| 611 | specific address in the BL31 image in the same processor mode as it was |
| 612 | when released from reset. |
| 613 | |
| 614 | The following functions need to be implemented by the platform port to enable |
| 615 | reset vector code to perform the above tasks. |
| 616 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 617 | Function : plat_get_my_entrypoint() [mandatory when PROGRAMMABLE_RESET_ADDRESS == 0] |
| 618 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 619 | |
| 620 | :: |
| 621 | |
| 622 | Argument : void |
| 623 | Return : uintptr_t |
| 624 | |
| 625 | This function is called with the MMU and caches disabled |
| 626 | (``SCTLR_EL3.M`` = 0 and ``SCTLR_EL3.C`` = 0). The function is responsible for |
| 627 | distinguishing between a warm and cold reset for the current CPU using |
| 628 | platform-specific means. If it's a warm reset, then it returns the warm |
| 629 | reset entrypoint point provided to ``plat_setup_psci_ops()`` during |
| 630 | BL31 initialization. If it's a cold reset then this function must return zero. |
| 631 | |
| 632 | This function does not follow the Procedure Call Standard used by the |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 633 | Application Binary Interface for the Arm 64-bit architecture. The caller should |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 634 | not assume that callee saved registers are preserved across a call to this |
| 635 | function. |
| 636 | |
| 637 | This function fulfills requirement 1 and 3 listed above. |
| 638 | |
| 639 | Note that for platforms that support programming the reset address, it is |
| 640 | expected that a CPU will start executing code directly at the right address, |
| 641 | both on a cold and warm reset. In this case, there is no need to identify the |
| 642 | type of reset nor to query the warm reset entrypoint. Therefore, implementing |
| 643 | this function is not required on such platforms. |
| 644 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 645 | Function : plat_secondary_cold_boot_setup() [mandatory when COLD_BOOT_SINGLE_CPU == 0] |
| 646 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 647 | |
| 648 | :: |
| 649 | |
| 650 | Argument : void |
| 651 | |
| 652 | This function is called with the MMU and data caches disabled. It is responsible |
| 653 | for placing the executing secondary CPU in a platform-specific state until the |
| 654 | primary CPU performs the necessary actions to bring it out of that state and |
| 655 | allow entry into the OS. This function must not return. |
| 656 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 657 | In the Arm FVP port, when using the normal boot flow, each secondary CPU powers |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 658 | itself off. The primary CPU is responsible for powering up the secondary CPUs |
| 659 | when normal world software requires them. When booting an EL3 payload instead, |
| 660 | they stay powered on and are put in a holding pen until their mailbox gets |
| 661 | populated. |
| 662 | |
| 663 | This function fulfills requirement 2 above. |
| 664 | |
| 665 | Note that for platforms that can't release secondary CPUs out of reset, only the |
| 666 | primary CPU will execute the cold boot code. Therefore, implementing this |
| 667 | function is not required on such platforms. |
| 668 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 669 | Function : plat_is_my_cpu_primary() [mandatory when COLD_BOOT_SINGLE_CPU == 0] |
| 670 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 671 | |
| 672 | :: |
| 673 | |
| 674 | Argument : void |
| 675 | Return : unsigned int |
| 676 | |
| 677 | This function identifies whether the current CPU is the primary CPU or a |
| 678 | secondary CPU. A return value of zero indicates that the CPU is not the |
| 679 | primary CPU, while a non-zero return value indicates that the CPU is the |
| 680 | primary CPU. |
| 681 | |
| 682 | Note that for platforms that can't release secondary CPUs out of reset, only the |
| 683 | primary CPU will execute the cold boot code. Therefore, there is no need to |
| 684 | distinguish between primary and secondary CPUs and implementing this function is |
| 685 | not required. |
| 686 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 687 | Function : platform_mem_init() [mandatory] |
| 688 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 689 | |
| 690 | :: |
| 691 | |
| 692 | Argument : void |
| 693 | Return : void |
| 694 | |
| 695 | This function is called before any access to data is made by the firmware, in |
| 696 | order to carry out any essential memory initialization. |
| 697 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 698 | Function: plat_get_rotpk_info() |
| 699 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 700 | |
| 701 | :: |
| 702 | |
| 703 | Argument : void *, void **, unsigned int *, unsigned int * |
| 704 | Return : int |
| 705 | |
| 706 | This function is mandatory when Trusted Board Boot is enabled. It returns a |
| 707 | pointer to the ROTPK stored in the platform (or a hash of it) and its length. |
| 708 | The ROTPK must be encoded in DER format according to the following ASN.1 |
| 709 | structure: |
| 710 | |
| 711 | :: |
| 712 | |
| 713 | AlgorithmIdentifier ::= SEQUENCE { |
| 714 | algorithm OBJECT IDENTIFIER, |
| 715 | parameters ANY DEFINED BY algorithm OPTIONAL |
| 716 | } |
| 717 | |
| 718 | SubjectPublicKeyInfo ::= SEQUENCE { |
| 719 | algorithm AlgorithmIdentifier, |
| 720 | subjectPublicKey BIT STRING |
| 721 | } |
| 722 | |
| 723 | In case the function returns a hash of the key: |
| 724 | |
| 725 | :: |
| 726 | |
| 727 | DigestInfo ::= SEQUENCE { |
| 728 | digestAlgorithm AlgorithmIdentifier, |
| 729 | digest OCTET STRING |
| 730 | } |
| 731 | |
| 732 | The function returns 0 on success. Any other value is treated as error by the |
| 733 | Trusted Board Boot. The function also reports extra information related |
| 734 | to the ROTPK in the flags parameter: |
| 735 | |
| 736 | :: |
| 737 | |
| 738 | ROTPK_IS_HASH : Indicates that the ROTPK returned by the platform is a |
| 739 | hash. |
| 740 | ROTPK_NOT_DEPLOYED : This allows the platform to skip certificate ROTPK |
| 741 | verification while the platform ROTPK is not deployed. |
| 742 | When this flag is set, the function does not need to |
| 743 | return a platform ROTPK, and the authentication |
| 744 | framework uses the ROTPK in the certificate without |
| 745 | verifying it against the platform value. This flag |
| 746 | must not be used in a deployed production environment. |
| 747 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 748 | Function: plat_get_nv_ctr() |
| 749 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 750 | |
| 751 | :: |
| 752 | |
| 753 | Argument : void *, unsigned int * |
| 754 | Return : int |
| 755 | |
| 756 | This function is mandatory when Trusted Board Boot is enabled. It returns the |
| 757 | non-volatile counter value stored in the platform in the second argument. The |
| 758 | cookie in the first argument may be used to select the counter in case the |
| 759 | platform provides more than one (for example, on platforms that use the default |
| 760 | TBBR CoT, the cookie will correspond to the OID values defined in |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 761 | TRUSTED_FW_NVCOUNTER_OID or NON_TRUSTED_FW_NVCOUNTER_OID). |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 762 | |
| 763 | The function returns 0 on success. Any other value means the counter value could |
| 764 | not be retrieved from the platform. |
| 765 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 766 | Function: plat_set_nv_ctr() |
| 767 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 768 | |
| 769 | :: |
| 770 | |
| 771 | Argument : void *, unsigned int |
| 772 | Return : int |
| 773 | |
| 774 | This function is mandatory when Trusted Board Boot is enabled. It sets a new |
| 775 | counter value in the platform. The cookie in the first argument may be used to |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 776 | select the counter (as explained in plat_get_nv_ctr()). The second argument is |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 777 | the updated counter value to be written to the NV counter. |
| 778 | |
| 779 | The function returns 0 on success. Any other value means the counter value could |
| 780 | not be updated. |
| 781 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 782 | Function: plat_set_nv_ctr2() |
| 783 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 784 | |
| 785 | :: |
| 786 | |
| 787 | Argument : void *, const auth_img_desc_t *, unsigned int |
| 788 | Return : int |
| 789 | |
| 790 | This function is optional when Trusted Board Boot is enabled. If this |
| 791 | interface is defined, then ``plat_set_nv_ctr()`` need not be defined. The |
| 792 | first argument passed is a cookie and is typically used to |
| 793 | differentiate between a Non Trusted NV Counter and a Trusted NV |
| 794 | Counter. The second argument is a pointer to an authentication image |
| 795 | descriptor and may be used to decide if the counter is allowed to be |
| 796 | updated or not. The third argument is the updated counter value to |
| 797 | be written to the NV counter. |
| 798 | |
| 799 | The function returns 0 on success. Any other value means the counter value |
| 800 | either could not be updated or the authentication image descriptor indicates |
| 801 | that it is not allowed to be updated. |
| 802 | |
| 803 | Common mandatory function modifications |
| 804 | --------------------------------------- |
| 805 | |
| 806 | The following functions are mandatory functions which need to be implemented |
| 807 | by the platform port. |
| 808 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 809 | Function : plat_my_core_pos() |
| 810 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 811 | |
| 812 | :: |
| 813 | |
| 814 | Argument : void |
| 815 | Return : unsigned int |
| 816 | |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 817 | This function returns the index of the calling CPU which is used as a |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 818 | CPU-specific linear index into blocks of memory (for example while allocating |
| 819 | per-CPU stacks). This function will be invoked very early in the |
| 820 | initialization sequence which mandates that this function should be |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 821 | implemented in assembly and should not rely on the availability of a C |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 822 | runtime environment. This function can clobber x0 - x8 and must preserve |
| 823 | x9 - x29. |
| 824 | |
| 825 | This function plays a crucial role in the power domain topology framework in |
| 826 | PSCI and details of this can be found in `Power Domain Topology Design`_. |
| 827 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 828 | Function : plat_core_pos_by_mpidr() |
| 829 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 830 | |
| 831 | :: |
| 832 | |
| 833 | Argument : u_register_t |
| 834 | Return : int |
| 835 | |
| 836 | This function validates the ``MPIDR`` of a CPU and converts it to an index, |
| 837 | which can be used as a CPU-specific linear index into blocks of memory. In |
| 838 | case the ``MPIDR`` is invalid, this function returns -1. This function will only |
| 839 | be invoked by BL31 after the power domain topology is initialized and can |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 840 | utilize the C runtime environment. For further details about how TF-A |
| 841 | represents the power domain topology and how this relates to the linear CPU |
| 842 | index, please refer `Power Domain Topology Design`_. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 843 | |
| 844 | Common optional modifications |
| 845 | ----------------------------- |
| 846 | |
| 847 | The following are helper functions implemented by the firmware that perform |
| 848 | common platform-specific tasks. A platform may choose to override these |
| 849 | definitions. |
| 850 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 851 | Function : plat_set_my_stack() |
| 852 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 853 | |
| 854 | :: |
| 855 | |
| 856 | Argument : void |
| 857 | Return : void |
| 858 | |
| 859 | This function sets the current stack pointer to the normal memory stack that |
| 860 | has been allocated for the current CPU. For BL images that only require a |
| 861 | stack for the primary CPU, the UP version of the function is used. The size |
| 862 | of the stack allocated to each CPU is specified by the platform defined |
| 863 | constant ``PLATFORM_STACK_SIZE``. |
| 864 | |
| 865 | Common implementations of this function for the UP and MP BL images are |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 866 | provided in `plat/common/aarch64/platform_up_stack.S`_ and |
| 867 | `plat/common/aarch64/platform_mp_stack.S`_ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 868 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 869 | Function : plat_get_my_stack() |
| 870 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 871 | |
| 872 | :: |
| 873 | |
| 874 | Argument : void |
| 875 | Return : uintptr_t |
| 876 | |
| 877 | This function returns the base address of the normal memory stack that |
| 878 | has been allocated for the current CPU. For BL images that only require a |
| 879 | stack for the primary CPU, the UP version of the function is used. The size |
| 880 | of the stack allocated to each CPU is specified by the platform defined |
| 881 | constant ``PLATFORM_STACK_SIZE``. |
| 882 | |
| 883 | Common implementations of this function for the UP and MP BL images are |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 884 | provided in `plat/common/aarch64/platform_up_stack.S`_ and |
| 885 | `plat/common/aarch64/platform_mp_stack.S`_ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 886 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 887 | Function : plat_report_exception() |
| 888 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 889 | |
| 890 | :: |
| 891 | |
| 892 | Argument : unsigned int |
| 893 | Return : void |
| 894 | |
| 895 | A platform may need to report various information about its status when an |
| 896 | exception is taken, for example the current exception level, the CPU security |
| 897 | state (secure/non-secure), the exception type, and so on. This function is |
| 898 | called in the following circumstances: |
| 899 | |
| 900 | - In BL1, whenever an exception is taken. |
| 901 | - In BL2, whenever an exception is taken. |
| 902 | |
| 903 | The default implementation doesn't do anything, to avoid making assumptions |
| 904 | about the way the platform displays its status information. |
| 905 | |
| 906 | For AArch64, this function receives the exception type as its argument. |
| 907 | Possible values for exceptions types are listed in the |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 908 | `include/common/bl_common.h`_ header file. Note that these constants are not |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 909 | related to any architectural exception code; they are just a TF-A convention. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 910 | |
| 911 | For AArch32, this function receives the exception mode as its argument. |
| 912 | Possible values for exception modes are listed in the |
| 913 | `include/lib/aarch32/arch.h`_ header file. |
| 914 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 915 | Function : plat_reset_handler() |
| 916 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 917 | |
| 918 | :: |
| 919 | |
| 920 | Argument : void |
| 921 | Return : void |
| 922 | |
| 923 | A platform may need to do additional initialization after reset. This function |
| 924 | allows the platform to do the platform specific intializations. Platform |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 925 | specific errata workarounds could also be implemented here. The API should |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 926 | preserve the values of callee saved registers x19 to x29. |
| 927 | |
| 928 | The default implementation doesn't do anything. If a platform needs to override |
| 929 | the default implementation, refer to the `Firmware Design`_ for general |
| 930 | guidelines. |
| 931 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 932 | Function : plat_disable_acp() |
| 933 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 934 | |
| 935 | :: |
| 936 | |
| 937 | Argument : void |
| 938 | Return : void |
| 939 | |
John Tsichritzis | 4901c53 | 2018-07-23 09:18:04 +0100 | [diff] [blame] | 940 | This API allows a platform to disable the Accelerator Coherency Port (if |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 941 | present) during a cluster power down sequence. The default weak implementation |
John Tsichritzis | 4901c53 | 2018-07-23 09:18:04 +0100 | [diff] [blame] | 942 | doesn't do anything. Since this API is called during the power down sequence, |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 943 | it has restrictions for stack usage and it can use the registers x0 - x17 as |
| 944 | scratch registers. It should preserve the value in x18 register as it is used |
| 945 | by the caller to store the return address. |
| 946 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 947 | Function : plat_error_handler() |
| 948 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 949 | |
| 950 | :: |
| 951 | |
| 952 | Argument : int |
| 953 | Return : void |
| 954 | |
| 955 | This API is called when the generic code encounters an error situation from |
| 956 | which it cannot continue. It allows the platform to perform error reporting or |
| 957 | recovery actions (for example, reset the system). This function must not return. |
| 958 | |
| 959 | The parameter indicates the type of error using standard codes from ``errno.h``. |
| 960 | Possible errors reported by the generic code are: |
| 961 | |
| 962 | - ``-EAUTH``: a certificate or image could not be authenticated (when Trusted |
| 963 | Board Boot is enabled) |
| 964 | - ``-ENOENT``: the requested image or certificate could not be found or an IO |
| 965 | error was detected |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 966 | - ``-ENOMEM``: resources exhausted. TF-A does not use dynamic memory, so this |
| 967 | error is usually an indication of an incorrect array size |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 968 | |
| 969 | The default implementation simply spins. |
| 970 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 971 | Function : plat_panic_handler() |
| 972 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 973 | |
| 974 | :: |
| 975 | |
| 976 | Argument : void |
| 977 | Return : void |
| 978 | |
| 979 | This API is called when the generic code encounters an unexpected error |
| 980 | situation from which it cannot recover. This function must not return, |
| 981 | and must be implemented in assembly because it may be called before the C |
| 982 | environment is initialized. |
| 983 | |
| 984 | Note: The address from where it was called is stored in x30 (Link Register). |
| 985 | The default implementation simply spins. |
| 986 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 987 | Function : plat_get_bl_image_load_info() |
| 988 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 989 | |
| 990 | :: |
| 991 | |
| 992 | Argument : void |
| 993 | Return : bl_load_info_t * |
| 994 | |
| 995 | This function returns pointer to the list of images that the platform has |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 996 | populated to load. This function is invoked in BL2 to load the |
| 997 | BL3xx images. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 998 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 999 | Function : plat_get_next_bl_params() |
| 1000 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1001 | |
| 1002 | :: |
| 1003 | |
| 1004 | Argument : void |
| 1005 | Return : bl_params_t * |
| 1006 | |
| 1007 | This function returns a pointer to the shared memory that the platform has |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1008 | kept aside to pass TF-A related information that next BL image needs. This |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1009 | function is invoked in BL2 to pass this information to the next BL |
| 1010 | image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1011 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1012 | Function : plat_get_stack_protector_canary() |
| 1013 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1014 | |
| 1015 | :: |
| 1016 | |
| 1017 | Argument : void |
| 1018 | Return : u_register_t |
| 1019 | |
| 1020 | This function returns a random value that is used to initialize the canary used |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1021 | when the stack protector is enabled with ENABLE_STACK_PROTECTOR. A predictable |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1022 | value will weaken the protection as the attacker could easily write the right |
| 1023 | value as part of the attack most of the time. Therefore, it should return a |
| 1024 | true random number. |
| 1025 | |
| 1026 | Note: For the protection to be effective, the global data need to be placed at |
| 1027 | a lower address than the stack bases. Failure to do so would allow an attacker |
| 1028 | to overwrite the canary as part of the stack buffer overflow attack. |
| 1029 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1030 | Function : plat_flush_next_bl_params() |
| 1031 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1032 | |
| 1033 | :: |
| 1034 | |
| 1035 | Argument : void |
| 1036 | Return : void |
| 1037 | |
| 1038 | This function flushes to main memory all the image params that are passed to |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1039 | next image. This function is invoked in BL2 to flush this information |
| 1040 | to the next BL image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1041 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1042 | Function : plat_log_get_prefix() |
| 1043 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Soby Mathew | 7f56e9a | 2017-09-04 11:49:29 +0100 | [diff] [blame] | 1044 | |
| 1045 | :: |
| 1046 | |
| 1047 | Argument : unsigned int |
| 1048 | Return : const char * |
| 1049 | |
| 1050 | This function defines the prefix string corresponding to the `log_level` to be |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1051 | prepended to all the log output from TF-A. The `log_level` (argument) will |
| 1052 | correspond to one of the standard log levels defined in debug.h. The platform |
| 1053 | can override the common implementation to define a different prefix string for |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1054 | the log output. The implementation should be robust to future changes that |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1055 | increase the number of log levels. |
Soby Mathew | 7f56e9a | 2017-09-04 11:49:29 +0100 | [diff] [blame] | 1056 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1057 | Function : plat_get_mbedtls_heap() |
| 1058 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1059 | |
| 1060 | :: |
| 1061 | |
| 1062 | Arguments : void **heap_addr, size_t *heap_size |
John Tsichritzis | ba597da | 2018-07-30 13:41:52 +0100 | [diff] [blame] | 1063 | Return : int |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1064 | |
| 1065 | This function is invoked during Mbed TLS library initialisation to get |
| 1066 | a heap, by means of a starting address and a size. This heap will then be used |
John Tsichritzis | ba597da | 2018-07-30 13:41:52 +0100 | [diff] [blame] | 1067 | internally by the Mbed TLS library. The heap is requested from the current BL |
| 1068 | stage, i.e. the current BL image inside which Mbed TLS is used. |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1069 | |
John Tsichritzis | ba597da | 2018-07-30 13:41:52 +0100 | [diff] [blame] | 1070 | In the default implementation a heap is statically allocated inside every image |
| 1071 | (i.e. every BL stage) that utilises Mbed TLS. So, in this case, the function |
| 1072 | simply returns the address and size of this "pre-allocated" heap. However, by |
| 1073 | overriding the default implementation, platforms have the potential to optimise |
| 1074 | memory usage. For example, on some Arm platforms, the Mbed TLS heap is shared |
| 1075 | between BL1 and BL2 stages and, thus, the necessary space is not reserved |
| 1076 | twice. |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1077 | |
John Tsichritzis | ba597da | 2018-07-30 13:41:52 +0100 | [diff] [blame] | 1078 | On success the function should return 0 and a negative error code otherwise. |
John Tsichritzis | 6d01a46 | 2018-06-07 16:31:34 +0100 | [diff] [blame] | 1079 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1080 | Modifications specific to a Boot Loader stage |
| 1081 | --------------------------------------------- |
| 1082 | |
| 1083 | Boot Loader Stage 1 (BL1) |
| 1084 | ------------------------- |
| 1085 | |
| 1086 | BL1 implements the reset vector where execution starts from after a cold or |
| 1087 | warm boot. For each CPU, BL1 is responsible for the following tasks: |
| 1088 | |
| 1089 | #. Handling the reset as described in section 2.2 |
| 1090 | |
| 1091 | #. In the case of a cold boot and the CPU being the primary CPU, ensuring that |
| 1092 | only this CPU executes the remaining BL1 code, including loading and passing |
| 1093 | control to the BL2 stage. |
| 1094 | |
| 1095 | #. Identifying and starting the Firmware Update process (if required). |
| 1096 | |
| 1097 | #. Loading the BL2 image from non-volatile storage into secure memory at the |
| 1098 | address specified by the platform defined constant ``BL2_BASE``. |
| 1099 | |
| 1100 | #. Populating a ``meminfo`` structure with the following information in memory, |
| 1101 | accessible by BL2 immediately upon entry. |
| 1102 | |
| 1103 | :: |
| 1104 | |
| 1105 | meminfo.total_base = Base address of secure RAM visible to BL2 |
| 1106 | meminfo.total_size = Size of secure RAM visible to BL2 |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1107 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1108 | By default, BL1 places this ``meminfo`` structure at the end of secure |
| 1109 | memory visible to BL2. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1110 | |
Soby Mathew | b2a68f8 | 2018-02-16 14:52:52 +0000 | [diff] [blame] | 1111 | It is possible for the platform to decide where it wants to place the |
| 1112 | ``meminfo`` structure for BL2 or restrict the amount of memory visible to |
| 1113 | BL2 by overriding the weak default implementation of |
| 1114 | ``bl1_plat_handle_post_image_load`` API. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1115 | |
| 1116 | The following functions need to be implemented by the platform port to enable |
| 1117 | BL1 to perform the above tasks. |
| 1118 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1119 | Function : bl1_early_platform_setup() [mandatory] |
| 1120 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1121 | |
| 1122 | :: |
| 1123 | |
| 1124 | Argument : void |
| 1125 | Return : void |
| 1126 | |
| 1127 | This function executes with the MMU and data caches disabled. It is only called |
| 1128 | by the primary CPU. |
| 1129 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1130 | On Arm standard platforms, this function: |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1131 | |
| 1132 | - Enables a secure instance of SP805 to act as the Trusted Watchdog. |
| 1133 | |
| 1134 | - Initializes a UART (PL011 console), which enables access to the ``printf`` |
| 1135 | family of functions in BL1. |
| 1136 | |
| 1137 | - Enables issuing of snoop and DVM (Distributed Virtual Memory) requests to |
| 1138 | the CCI slave interface corresponding to the cluster that includes the |
| 1139 | primary CPU. |
| 1140 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1141 | Function : bl1_plat_arch_setup() [mandatory] |
| 1142 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1143 | |
| 1144 | :: |
| 1145 | |
| 1146 | Argument : void |
| 1147 | Return : void |
| 1148 | |
| 1149 | This function performs any platform-specific and architectural setup that the |
| 1150 | platform requires. Platform-specific setup might include configuration of |
| 1151 | memory controllers and the interconnect. |
| 1152 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1153 | In Arm standard platforms, this function enables the MMU. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1154 | |
| 1155 | This function helps fulfill requirement 2 above. |
| 1156 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1157 | Function : bl1_platform_setup() [mandatory] |
| 1158 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1159 | |
| 1160 | :: |
| 1161 | |
| 1162 | Argument : void |
| 1163 | Return : void |
| 1164 | |
| 1165 | This function executes with the MMU and data caches enabled. It is responsible |
| 1166 | for performing any remaining platform-specific setup that can occur after the |
| 1167 | MMU and data cache have been enabled. |
| 1168 | |
Roberto Vargas | 2a350df | 2017-12-12 10:39:44 +0000 | [diff] [blame] | 1169 | if support for multiple boot sources is required, it initializes the boot |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1170 | sequence used by plat_try_next_boot_source(). |
Roberto Vargas | 2a350df | 2017-12-12 10:39:44 +0000 | [diff] [blame] | 1171 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1172 | In Arm standard platforms, this function initializes the storage abstraction |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1173 | layer used to load the next bootloader image. |
| 1174 | |
| 1175 | This function helps fulfill requirement 4 above. |
| 1176 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1177 | Function : bl1_plat_sec_mem_layout() [mandatory] |
| 1178 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1179 | |
| 1180 | :: |
| 1181 | |
| 1182 | Argument : void |
| 1183 | Return : meminfo * |
| 1184 | |
| 1185 | This function should only be called on the cold boot path. It executes with the |
| 1186 | MMU and data caches enabled. The pointer returned by this function must point to |
| 1187 | a ``meminfo`` structure containing the extents and availability of secure RAM for |
| 1188 | the BL1 stage. |
| 1189 | |
| 1190 | :: |
| 1191 | |
| 1192 | meminfo.total_base = Base address of secure RAM visible to BL1 |
| 1193 | meminfo.total_size = Size of secure RAM visible to BL1 |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1194 | |
| 1195 | This information is used by BL1 to load the BL2 image in secure RAM. BL1 also |
| 1196 | populates a similar structure to tell BL2 the extents of memory available for |
| 1197 | its own use. |
| 1198 | |
| 1199 | This function helps fulfill requirements 4 and 5 above. |
| 1200 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1201 | Function : bl1_plat_prepare_exit() [optional] |
| 1202 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1203 | |
| 1204 | :: |
| 1205 | |
| 1206 | Argument : entry_point_info_t * |
| 1207 | Return : void |
| 1208 | |
| 1209 | This function is called prior to exiting BL1 in response to the |
| 1210 | ``BL1_SMC_RUN_IMAGE`` SMC request raised by BL2. It should be used to perform |
| 1211 | platform specific clean up or bookkeeping operations before transferring |
| 1212 | control to the next image. It receives the address of the ``entry_point_info_t`` |
| 1213 | structure passed from BL2. This function runs with MMU disabled. |
| 1214 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1215 | Function : bl1_plat_set_ep_info() [optional] |
| 1216 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1217 | |
| 1218 | :: |
| 1219 | |
| 1220 | Argument : unsigned int image_id, entry_point_info_t *ep_info |
| 1221 | Return : void |
| 1222 | |
| 1223 | This function allows platforms to override ``ep_info`` for the given ``image_id``. |
| 1224 | |
| 1225 | The default implementation just returns. |
| 1226 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1227 | Function : bl1_plat_get_next_image_id() [optional] |
| 1228 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1229 | |
| 1230 | :: |
| 1231 | |
| 1232 | Argument : void |
| 1233 | Return : unsigned int |
| 1234 | |
| 1235 | This and the following function must be overridden to enable the FWU feature. |
| 1236 | |
| 1237 | BL1 calls this function after platform setup to identify the next image to be |
| 1238 | loaded and executed. If the platform returns ``BL2_IMAGE_ID`` then BL1 proceeds |
| 1239 | with the normal boot sequence, which loads and executes BL2. If the platform |
| 1240 | returns a different image id, BL1 assumes that Firmware Update is required. |
| 1241 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1242 | The default implementation always returns ``BL2_IMAGE_ID``. The Arm development |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1243 | platforms override this function to detect if firmware update is required, and |
| 1244 | if so, return the first image in the firmware update process. |
| 1245 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1246 | Function : bl1_plat_get_image_desc() [optional] |
| 1247 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1248 | |
| 1249 | :: |
| 1250 | |
| 1251 | Argument : unsigned int image_id |
| 1252 | Return : image_desc_t * |
| 1253 | |
| 1254 | BL1 calls this function to get the image descriptor information ``image_desc_t`` |
| 1255 | for the provided ``image_id`` from the platform. |
| 1256 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1257 | The default implementation always returns a common BL2 image descriptor. Arm |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1258 | standard platforms return an image descriptor corresponding to BL2 or one of |
| 1259 | the firmware update images defined in the Trusted Board Boot Requirements |
| 1260 | specification. |
| 1261 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1262 | Function : bl1_plat_handle_pre_image_load() [optional] |
| 1263 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1264 | |
| 1265 | :: |
| 1266 | |
Soby Mathew | 566034f | 2018-02-08 17:45:12 +0000 | [diff] [blame] | 1267 | Argument : unsigned int image_id |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1268 | Return : int |
| 1269 | |
| 1270 | This function can be used by the platforms to update/use image information |
Soby Mathew | 566034f | 2018-02-08 17:45:12 +0000 | [diff] [blame] | 1271 | corresponding to ``image_id``. This function is invoked in BL1, both in cold |
| 1272 | boot and FWU code path, before loading the image. |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1273 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1274 | Function : bl1_plat_handle_post_image_load() [optional] |
| 1275 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1276 | |
| 1277 | :: |
| 1278 | |
Soby Mathew | 566034f | 2018-02-08 17:45:12 +0000 | [diff] [blame] | 1279 | Argument : unsigned int image_id |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1280 | Return : int |
| 1281 | |
| 1282 | This function can be used by the platforms to update/use image information |
Soby Mathew | 566034f | 2018-02-08 17:45:12 +0000 | [diff] [blame] | 1283 | corresponding to ``image_id``. This function is invoked in BL1, both in cold |
| 1284 | boot and FWU code path, after loading and authenticating the image. |
Masahiro Yamada | 11f001c | 2018-02-01 16:46:18 +0900 | [diff] [blame] | 1285 | |
Soby Mathew | b2a68f8 | 2018-02-16 14:52:52 +0000 | [diff] [blame] | 1286 | The default weak implementation of this function calculates the amount of |
| 1287 | Trusted SRAM that can be used by BL2 and allocates a ``meminfo_t`` |
| 1288 | structure at the beginning of this free memory and populates it. The address |
| 1289 | of ``meminfo_t`` structure is updated in ``arg1`` of the entrypoint |
| 1290 | information to BL2. |
| 1291 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1292 | Function : bl1_plat_fwu_done() [optional] |
| 1293 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1294 | |
| 1295 | :: |
| 1296 | |
| 1297 | Argument : unsigned int image_id, uintptr_t image_src, |
| 1298 | unsigned int image_size |
| 1299 | Return : void |
| 1300 | |
| 1301 | BL1 calls this function when the FWU process is complete. It must not return. |
| 1302 | The platform may override this function to take platform specific action, for |
| 1303 | example to initiate the normal boot flow. |
| 1304 | |
| 1305 | The default implementation spins forever. |
| 1306 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1307 | Function : bl1_plat_mem_check() [mandatory] |
| 1308 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1309 | |
| 1310 | :: |
| 1311 | |
| 1312 | Argument : uintptr_t mem_base, unsigned int mem_size, |
| 1313 | unsigned int flags |
| 1314 | Return : int |
| 1315 | |
| 1316 | BL1 calls this function while handling FWU related SMCs, more specifically when |
| 1317 | copying or authenticating an image. Its responsibility is to ensure that the |
| 1318 | region of memory identified by ``mem_base`` and ``mem_size`` is mapped in BL1, and |
| 1319 | that this memory corresponds to either a secure or non-secure memory region as |
| 1320 | indicated by the security state of the ``flags`` argument. |
| 1321 | |
| 1322 | This function can safely assume that the value resulting from the addition of |
| 1323 | ``mem_base`` and ``mem_size`` fits into a ``uintptr_t`` type variable and does not |
| 1324 | overflow. |
| 1325 | |
| 1326 | This function must return 0 on success, a non-null error code otherwise. |
| 1327 | |
| 1328 | The default implementation of this function asserts therefore platforms must |
| 1329 | override it when using the FWU feature. |
| 1330 | |
| 1331 | Boot Loader Stage 2 (BL2) |
| 1332 | ------------------------- |
| 1333 | |
| 1334 | The BL2 stage is executed only by the primary CPU, which is determined in BL1 |
| 1335 | using the ``platform_is_primary_cpu()`` function. BL1 passed control to BL2 at |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1336 | ``BL2_BASE``. BL2 executes in Secure EL1 and and invokes |
| 1337 | ``plat_get_bl_image_load_info()`` to retrieve the list of images to load from |
| 1338 | non-volatile storage to secure/non-secure RAM. After all the images are loaded |
| 1339 | then BL2 invokes ``plat_get_next_bl_params()`` to get the list of executable |
| 1340 | images to be passed to the next BL image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1341 | |
| 1342 | The following functions must be implemented by the platform port to enable BL2 |
| 1343 | to perform the above tasks. |
| 1344 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1345 | Function : bl2_early_platform_setup2() [mandatory] |
| 1346 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1347 | |
| 1348 | :: |
| 1349 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1350 | Argument : u_register_t, u_register_t, u_register_t, u_register_t |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1351 | Return : void |
| 1352 | |
| 1353 | This function executes with the MMU and data caches disabled. It is only called |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1354 | by the primary CPU. The 4 arguments are passed by BL1 to BL2 and these arguments |
| 1355 | are platform specific. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1356 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1357 | On Arm standard platforms, the arguments received are : |
| 1358 | |
| 1359 | arg0 - Points to load address of HW_CONFIG if present |
| 1360 | |
| 1361 | arg1 - ``meminfo`` structure populated by BL1. The platform copies |
| 1362 | the contents of ``meminfo`` as it may be subsequently overwritten by BL2. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1363 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1364 | On Arm standard platforms, this function also: |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1365 | |
| 1366 | - Initializes a UART (PL011 console), which enables access to the ``printf`` |
| 1367 | family of functions in BL2. |
| 1368 | |
| 1369 | - Initializes the storage abstraction layer used to load further bootloader |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1370 | images. It is necessary to do this early on platforms with a SCP_BL2 image, |
| 1371 | since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1372 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1373 | Function : bl2_plat_arch_setup() [mandatory] |
| 1374 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1375 | |
| 1376 | :: |
| 1377 | |
| 1378 | Argument : void |
| 1379 | Return : void |
| 1380 | |
| 1381 | This function executes with the MMU and data caches disabled. It is only called |
| 1382 | by the primary CPU. |
| 1383 | |
| 1384 | The purpose of this function is to perform any architectural initialization |
| 1385 | that varies across platforms. |
| 1386 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1387 | On Arm standard platforms, this function enables the MMU. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1388 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1389 | Function : bl2_platform_setup() [mandatory] |
| 1390 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1391 | |
| 1392 | :: |
| 1393 | |
| 1394 | Argument : void |
| 1395 | Return : void |
| 1396 | |
| 1397 | This function may execute with the MMU and data caches enabled if the platform |
| 1398 | port does the necessary initialization in ``bl2_plat_arch_setup()``. It is only |
| 1399 | called by the primary CPU. |
| 1400 | |
| 1401 | The purpose of this function is to perform any platform initialization |
| 1402 | specific to BL2. |
| 1403 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1404 | In Arm standard platforms, this function performs security setup, including |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1405 | configuration of the TrustZone controller to allow non-secure masters access |
| 1406 | to most of DRAM. Part of DRAM is reserved for secure world use. |
| 1407 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1408 | Function : bl2_plat_handle_pre_image_load() [optional] |
| 1409 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1410 | |
| 1411 | :: |
| 1412 | |
| 1413 | Argument : unsigned int |
| 1414 | Return : int |
| 1415 | |
| 1416 | This function can be used by the platforms to update/use image information |
Masahiro Yamada | ba68ef5 | 2018-02-01 16:45:51 +0900 | [diff] [blame] | 1417 | for given ``image_id``. This function is currently invoked in BL2 before |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1418 | loading each image. |
Masahiro Yamada | ba68ef5 | 2018-02-01 16:45:51 +0900 | [diff] [blame] | 1419 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1420 | Function : bl2_plat_handle_post_image_load() [optional] |
| 1421 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Masahiro Yamada | ba68ef5 | 2018-02-01 16:45:51 +0900 | [diff] [blame] | 1422 | |
| 1423 | :: |
| 1424 | |
| 1425 | Argument : unsigned int |
| 1426 | Return : int |
| 1427 | |
| 1428 | This function can be used by the platforms to update/use image information |
| 1429 | for given ``image_id``. This function is currently invoked in BL2 after |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1430 | loading each image. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1431 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1432 | Function : bl2_plat_preload_setup [optional] |
| 1433 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1434 | |
| 1435 | :: |
John Tsichritzis | 677ad32 | 2018-06-06 09:38:10 +0100 | [diff] [blame] | 1436 | |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1437 | Argument : void |
| 1438 | Return : void |
| 1439 | |
| 1440 | This optional function performs any BL2 platform initialization |
| 1441 | required before image loading, that is not done later in |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1442 | bl2_platform_setup(). Specifically, if support for multiple |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1443 | boot sources is required, it initializes the boot sequence used by |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1444 | plat_try_next_boot_source(). |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1445 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1446 | Function : plat_try_next_boot_source() [optional] |
| 1447 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1448 | |
| 1449 | :: |
John Tsichritzis | 677ad32 | 2018-06-06 09:38:10 +0100 | [diff] [blame] | 1450 | |
Roberto Vargas | 01f62b6 | 2017-09-26 12:53:01 +0100 | [diff] [blame] | 1451 | Argument : void |
| 1452 | Return : int |
| 1453 | |
| 1454 | This optional function passes to the next boot source in the redundancy |
| 1455 | sequence. |
| 1456 | |
| 1457 | This function moves the current boot redundancy source to the next |
| 1458 | element in the boot sequence. If there are no more boot sources then it |
| 1459 | must return 0, otherwise it must return 1. The default implementation |
| 1460 | of this always returns 0. |
| 1461 | |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1462 | Boot Loader Stage 2 (BL2) at EL3 |
| 1463 | -------------------------------- |
| 1464 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1465 | When the platform has a non-TF-A Boot ROM it is desirable to jump |
| 1466 | directly to BL2 instead of TF-A BL1. In this case BL2 is expected to |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1467 | execute at EL3 instead of executing at EL1. Refer to the `Firmware |
| 1468 | Design`_ for more information. |
| 1469 | |
| 1470 | All mandatory functions of BL2 must be implemented, except the functions |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1471 | bl2_early_platform_setup and bl2_el3_plat_arch_setup, because |
| 1472 | their work is done now by bl2_el3_early_platform_setup and |
| 1473 | bl2_el3_plat_arch_setup. These functions should generally implement |
| 1474 | the bl1_plat_xxx() and bl2_plat_xxx() functionality combined. |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1475 | |
| 1476 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1477 | Function : bl2_el3_early_platform_setup() [mandatory] |
| 1478 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1479 | |
| 1480 | :: |
John Tsichritzis | 677ad32 | 2018-06-06 09:38:10 +0100 | [diff] [blame] | 1481 | |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1482 | Argument : u_register_t, u_register_t, u_register_t, u_register_t |
| 1483 | Return : void |
| 1484 | |
| 1485 | This function executes with the MMU and data caches disabled. It is only called |
| 1486 | by the primary CPU. This function receives four parameters which can be used |
| 1487 | by the platform to pass any needed information from the Boot ROM to BL2. |
| 1488 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1489 | On Arm standard platforms, this function does the following: |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1490 | |
| 1491 | - Initializes a UART (PL011 console), which enables access to the ``printf`` |
| 1492 | family of functions in BL2. |
| 1493 | |
| 1494 | - Initializes the storage abstraction layer used to load further bootloader |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1495 | images. It is necessary to do this early on platforms with a SCP_BL2 image, |
| 1496 | since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded. |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1497 | |
| 1498 | - Initializes the private variables that define the memory layout used. |
| 1499 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1500 | Function : bl2_el3_plat_arch_setup() [mandatory] |
| 1501 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1502 | |
| 1503 | :: |
John Tsichritzis | 677ad32 | 2018-06-06 09:38:10 +0100 | [diff] [blame] | 1504 | |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1505 | Argument : void |
| 1506 | Return : void |
| 1507 | |
| 1508 | This function executes with the MMU and data caches disabled. It is only called |
| 1509 | by the primary CPU. |
| 1510 | |
| 1511 | The purpose of this function is to perform any architectural initialization |
| 1512 | that varies across platforms. |
| 1513 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1514 | On Arm standard platforms, this function enables the MMU. |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1515 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1516 | Function : bl2_el3_plat_prepare_exit() [optional] |
| 1517 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1518 | |
| 1519 | :: |
John Tsichritzis | 677ad32 | 2018-06-06 09:38:10 +0100 | [diff] [blame] | 1520 | |
Roberto Vargas | 4cd1769 | 2017-11-20 13:36:10 +0000 | [diff] [blame] | 1521 | Argument : void |
| 1522 | Return : void |
| 1523 | |
| 1524 | This function is called prior to exiting BL2 and run the next image. |
| 1525 | It should be used to perform platform specific clean up or bookkeeping |
| 1526 | operations before transferring control to the next image. This function |
| 1527 | runs with MMU disabled. |
| 1528 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1529 | FWU Boot Loader Stage 2 (BL2U) |
| 1530 | ------------------------------ |
| 1531 | |
| 1532 | The AP Firmware Updater Configuration, BL2U, is an optional part of the FWU |
| 1533 | process and is executed only by the primary CPU. BL1 passes control to BL2U at |
| 1534 | ``BL2U_BASE``. BL2U executes in Secure-EL1 and is responsible for: |
| 1535 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1536 | #. (Optional) Transferring the optional SCP_BL2U binary image from AP secure |
| 1537 | memory to SCP RAM. BL2U uses the SCP_BL2U ``image_info`` passed by BL1. |
| 1538 | ``SCP_BL2U_BASE`` defines the address in AP secure memory where SCP_BL2U |
| 1539 | should be copied from. Subsequent handling of the SCP_BL2U image is |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1540 | implemented by the platform specific ``bl2u_plat_handle_scp_bl2u()`` function. |
| 1541 | If ``SCP_BL2U_BASE`` is not defined then this step is not performed. |
| 1542 | |
| 1543 | #. Any platform specific setup required to perform the FWU process. For |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1544 | example, Arm standard platforms initialize the TZC controller so that the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1545 | normal world can access DDR memory. |
| 1546 | |
| 1547 | The following functions must be implemented by the platform port to enable |
| 1548 | BL2U to perform the tasks mentioned above. |
| 1549 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1550 | Function : bl2u_early_platform_setup() [mandatory] |
| 1551 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1552 | |
| 1553 | :: |
| 1554 | |
| 1555 | Argument : meminfo *mem_info, void *plat_info |
| 1556 | Return : void |
| 1557 | |
| 1558 | This function executes with the MMU and data caches disabled. It is only |
| 1559 | called by the primary CPU. The arguments to this function is the address |
| 1560 | of the ``meminfo`` structure and platform specific info provided by BL1. |
| 1561 | |
| 1562 | The platform may copy the contents of the ``mem_info`` and ``plat_info`` into |
| 1563 | private storage as the original memory may be subsequently overwritten by BL2U. |
| 1564 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1565 | On Arm CSS platforms ``plat_info`` is interpreted as an ``image_info_t`` structure, |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1566 | to extract SCP_BL2U image information, which is then copied into a private |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1567 | variable. |
| 1568 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1569 | Function : bl2u_plat_arch_setup() [mandatory] |
| 1570 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1571 | |
| 1572 | :: |
| 1573 | |
| 1574 | Argument : void |
| 1575 | Return : void |
| 1576 | |
| 1577 | This function executes with the MMU and data caches disabled. It is only |
| 1578 | called by the primary CPU. |
| 1579 | |
| 1580 | The purpose of this function is to perform any architectural initialization |
| 1581 | that varies across platforms, for example enabling the MMU (since the memory |
| 1582 | map differs across platforms). |
| 1583 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1584 | Function : bl2u_platform_setup() [mandatory] |
| 1585 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1586 | |
| 1587 | :: |
| 1588 | |
| 1589 | Argument : void |
| 1590 | Return : void |
| 1591 | |
| 1592 | This function may execute with the MMU and data caches enabled if the platform |
| 1593 | port does the necessary initialization in ``bl2u_plat_arch_setup()``. It is only |
| 1594 | called by the primary CPU. |
| 1595 | |
| 1596 | The purpose of this function is to perform any platform initialization |
| 1597 | specific to BL2U. |
| 1598 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1599 | In Arm standard platforms, this function performs security setup, including |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1600 | configuration of the TrustZone controller to allow non-secure masters access |
| 1601 | to most of DRAM. Part of DRAM is reserved for secure world use. |
| 1602 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1603 | Function : bl2u_plat_handle_scp_bl2u() [optional] |
| 1604 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1605 | |
| 1606 | :: |
| 1607 | |
| 1608 | Argument : void |
| 1609 | Return : int |
| 1610 | |
| 1611 | This function is used to perform any platform-specific actions required to |
| 1612 | handle the SCP firmware. Typically it transfers the image into SCP memory using |
| 1613 | a platform-specific protocol and waits until SCP executes it and signals to the |
| 1614 | Application Processor (AP) for BL2U execution to continue. |
| 1615 | |
| 1616 | This function returns 0 on success, a negative error code otherwise. |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1617 | This function is included if SCP_BL2U_BASE is defined. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1618 | |
| 1619 | Boot Loader Stage 3-1 (BL31) |
| 1620 | ---------------------------- |
| 1621 | |
| 1622 | During cold boot, the BL31 stage is executed only by the primary CPU. This is |
| 1623 | determined in BL1 using the ``platform_is_primary_cpu()`` function. BL1 passes |
| 1624 | control to BL31 at ``BL31_BASE``. During warm boot, BL31 is executed by all |
| 1625 | CPUs. BL31 executes at EL3 and is responsible for: |
| 1626 | |
| 1627 | #. Re-initializing all architectural and platform state. Although BL1 performs |
| 1628 | some of this initialization, BL31 remains resident in EL3 and must ensure |
| 1629 | that EL3 architectural and platform state is completely initialized. It |
| 1630 | should make no assumptions about the system state when it receives control. |
| 1631 | |
| 1632 | #. Passing control to a normal world BL image, pre-loaded at a platform- |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1633 | specific address by BL2. On ARM platforms, BL31 uses the ``bl_params`` list |
| 1634 | populated by BL2 in memory to do this. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1635 | |
| 1636 | #. Providing runtime firmware services. Currently, BL31 only implements a |
| 1637 | subset of the Power State Coordination Interface (PSCI) API as a runtime |
| 1638 | service. See Section 3.3 below for details of porting the PSCI |
| 1639 | implementation. |
| 1640 | |
| 1641 | #. Optionally passing control to the BL32 image, pre-loaded at a platform- |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 1642 | specific address by BL2. BL31 exports a set of APIs that allow runtime |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1643 | services to specify the security state in which the next image should be |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1644 | executed and run the corresponding image. On ARM platforms, BL31 uses the |
| 1645 | ``bl_params`` list populated by BL2 in memory to do this. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1646 | |
| 1647 | If BL31 is a reset vector, It also needs to handle the reset as specified in |
| 1648 | section 2.2 before the tasks described above. |
| 1649 | |
| 1650 | The following functions must be implemented by the platform port to enable BL31 |
| 1651 | to perform the above tasks. |
| 1652 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1653 | Function : bl31_early_platform_setup2() [mandatory] |
| 1654 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1655 | |
| 1656 | :: |
| 1657 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1658 | Argument : u_register_t, u_register_t, u_register_t, u_register_t |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1659 | Return : void |
| 1660 | |
| 1661 | This function executes with the MMU and data caches disabled. It is only called |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1662 | by the primary CPU. BL2 can pass 4 arguments to BL31 and these arguments are |
| 1663 | platform specific. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1664 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1665 | In Arm standard platforms, the arguments received are : |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1666 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1667 | arg0 - The pointer to the head of `bl_params_t` list |
| 1668 | which is list of executable images following BL31, |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1669 | |
Soby Mathew | 509af92 | 2018-09-27 16:46:41 +0100 | [diff] [blame] | 1670 | arg1 - Points to load address of SOC_FW_CONFIG if present |
| 1671 | |
| 1672 | arg2 - Points to load address of HW_CONFIG if present |
| 1673 | |
| 1674 | arg3 - A special value to verify platform parameters from BL2 to BL31. Not |
| 1675 | used in release builds. |
| 1676 | |
| 1677 | The function runs through the `bl_param_t` list and extracts the entry point |
| 1678 | information for BL32 and BL33. It also performs the following: |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1679 | |
| 1680 | - Initialize a UART (PL011 console), which enables access to the ``printf`` |
| 1681 | family of functions in BL31. |
| 1682 | |
| 1683 | - Enable issuing of snoop and DVM (Distributed Virtual Memory) requests to the |
| 1684 | CCI slave interface corresponding to the cluster that includes the primary |
| 1685 | CPU. |
| 1686 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1687 | Function : bl31_plat_arch_setup() [mandatory] |
| 1688 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1689 | |
| 1690 | :: |
| 1691 | |
| 1692 | Argument : void |
| 1693 | Return : void |
| 1694 | |
| 1695 | This function executes with the MMU and data caches disabled. It is only called |
| 1696 | by the primary CPU. |
| 1697 | |
| 1698 | The purpose of this function is to perform any architectural initialization |
| 1699 | that varies across platforms. |
| 1700 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1701 | On Arm standard platforms, this function enables the MMU. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1702 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1703 | Function : bl31_platform_setup() [mandatory] |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1704 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1705 | |
| 1706 | :: |
| 1707 | |
| 1708 | Argument : void |
| 1709 | Return : void |
| 1710 | |
| 1711 | This function may execute with the MMU and data caches enabled if the platform |
| 1712 | port does the necessary initialization in ``bl31_plat_arch_setup()``. It is only |
| 1713 | called by the primary CPU. |
| 1714 | |
| 1715 | The purpose of this function is to complete platform initialization so that both |
| 1716 | BL31 runtime services and normal world software can function correctly. |
| 1717 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1718 | On Arm standard platforms, this function does the following: |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1719 | |
| 1720 | - Initialize the generic interrupt controller. |
| 1721 | |
| 1722 | Depending on the GIC driver selected by the platform, the appropriate GICv2 |
| 1723 | or GICv3 initialization will be done, which mainly consists of: |
| 1724 | |
| 1725 | - Enable secure interrupts in the GIC CPU interface. |
| 1726 | - Disable the legacy interrupt bypass mechanism. |
| 1727 | - Configure the priority mask register to allow interrupts of all priorities |
| 1728 | to be signaled to the CPU interface. |
| 1729 | - Mark SGIs 8-15 and the other secure interrupts on the platform as secure. |
| 1730 | - Target all secure SPIs to CPU0. |
| 1731 | - Enable these secure interrupts in the GIC distributor. |
| 1732 | - Configure all other interrupts as non-secure. |
| 1733 | - Enable signaling of secure interrupts in the GIC distributor. |
| 1734 | |
| 1735 | - Enable system-level implementation of the generic timer counter through the |
| 1736 | memory mapped interface. |
| 1737 | |
| 1738 | - Grant access to the system counter timer module |
| 1739 | |
| 1740 | - Initialize the power controller device. |
| 1741 | |
| 1742 | In particular, initialise the locks that prevent concurrent accesses to the |
| 1743 | power controller device. |
| 1744 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1745 | Function : bl31_plat_runtime_setup() [optional] |
| 1746 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1747 | |
| 1748 | :: |
| 1749 | |
| 1750 | Argument : void |
| 1751 | Return : void |
| 1752 | |
| 1753 | The purpose of this function is allow the platform to perform any BL31 runtime |
| 1754 | setup just prior to BL31 exit during cold boot. The default weak |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 1755 | implementation of this function will invoke ``console_switch_state()`` to switch |
| 1756 | console output to consoles marked for use in the ``runtime`` state. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1757 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1758 | Function : bl31_plat_get_next_image_ep_info() [mandatory] |
| 1759 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1760 | |
| 1761 | :: |
| 1762 | |
Sandrine Bailleux | 1ec1ebf | 2018-05-14 14:25:47 +0200 | [diff] [blame] | 1763 | Argument : uint32_t |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1764 | Return : entry_point_info * |
| 1765 | |
| 1766 | This function may execute with the MMU and data caches enabled if the platform |
| 1767 | port does the necessary initializations in ``bl31_plat_arch_setup()``. |
| 1768 | |
| 1769 | This function is called by ``bl31_main()`` to retrieve information provided by |
| 1770 | BL2 for the next image in the security state specified by the argument. BL31 |
| 1771 | uses this information to pass control to that image in the specified security |
| 1772 | state. This function must return a pointer to the ``entry_point_info`` structure |
| 1773 | (that was copied during ``bl31_early_platform_setup()``) if the image exists. It |
| 1774 | should return NULL otherwise. |
| 1775 | |
Jeenu Viswambharan | 64ee263 | 2018-04-27 15:17:03 +0100 | [diff] [blame] | 1776 | Function : bl31_plat_enable_mmu [optional] |
| 1777 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1778 | |
| 1779 | :: |
| 1780 | |
| 1781 | Argument : uint32_t |
| 1782 | Return : void |
| 1783 | |
| 1784 | This function enables the MMU. The boot code calls this function with MMU and |
| 1785 | caches disabled. This function should program necessary registers to enable |
| 1786 | translation, and upon return, the MMU on the calling PE must be enabled. |
| 1787 | |
| 1788 | The function must honor flags passed in the first argument. These flags are |
| 1789 | defined by the translation library, and can be found in the file |
| 1790 | ``include/lib/xlat_tables/xlat_mmu_helpers.h``. |
| 1791 | |
| 1792 | On DynamIQ systems, this function must not use stack while enabling MMU, which |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 1793 | is how the function in xlat table library version 2 is implemented. |
Jeenu Viswambharan | 64ee263 | 2018-04-27 15:17:03 +0100 | [diff] [blame] | 1794 | |
Antonio Nino Diaz | b86048c | 2019-02-19 11:53:51 +0000 | [diff] [blame] | 1795 | Function : plat_init_apiakey [optional] |
| 1796 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1797 | |
| 1798 | :: |
| 1799 | |
| 1800 | Argument : void |
| 1801 | Return : uint64_t * |
| 1802 | |
| 1803 | This function populates the ``plat_apiakey`` array that contains the values used |
| 1804 | to set the ``APIAKey{Hi,Lo}_EL1`` registers. It returns a pointer to this array. |
| 1805 | |
| 1806 | The value should be obtained from a reliable source of randomness. |
| 1807 | |
| 1808 | This function is only needed if ARMv8.3 pointer authentication is used in the |
| 1809 | Trusted Firmware by building with ``ENABLE_PAUTH=1``. |
| 1810 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1811 | Function : plat_get_syscnt_freq2() [mandatory] |
| 1812 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1813 | |
| 1814 | :: |
| 1815 | |
| 1816 | Argument : void |
| 1817 | Return : unsigned int |
| 1818 | |
| 1819 | This function is used by the architecture setup code to retrieve the counter |
| 1820 | frequency for the CPU's generic timer. This value will be programmed into the |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1821 | ``CNTFRQ_EL0`` register. In Arm standard platforms, it returns the base frequency |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1822 | of the system counter, which is retrieved from the first entry in the frequency |
| 1823 | modes table. |
| 1824 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1825 | #define : PLAT_PERCPU_BAKERY_LOCK_SIZE [optional] |
| 1826 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1827 | |
| 1828 | When ``USE_COHERENT_MEM = 0``, this constant defines the total memory (in |
| 1829 | bytes) aligned to the cache line boundary that should be allocated per-cpu to |
| 1830 | accommodate all the bakery locks. |
| 1831 | |
| 1832 | If this constant is not defined when ``USE_COHERENT_MEM = 0``, the linker |
| 1833 | calculates the size of the ``bakery_lock`` input section, aligns it to the |
| 1834 | nearest ``CACHE_WRITEBACK_GRANULE``, multiplies it with ``PLATFORM_CORE_COUNT`` |
| 1835 | and stores the result in a linker symbol. This constant prevents a platform |
| 1836 | from relying on the linker and provide a more efficient mechanism for |
| 1837 | accessing per-cpu bakery lock information. |
| 1838 | |
| 1839 | If this constant is defined and its value is not equal to the value |
| 1840 | calculated by the linker then a link time assertion is raised. A compile time |
| 1841 | assertion is raised if the value of the constant is not aligned to the cache |
| 1842 | line boundary. |
| 1843 | |
Jeenu Viswambharan | b7cb133 | 2017-10-16 08:43:14 +0100 | [diff] [blame] | 1844 | SDEI porting requirements |
| 1845 | ~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 1846 | |
| 1847 | The SDEI dispatcher requires the platform to provide the following macros |
| 1848 | and functions, of which some are optional, and some others mandatory. |
| 1849 | |
| 1850 | Macros |
| 1851 | ...... |
| 1852 | |
| 1853 | Macro: PLAT_SDEI_NORMAL_PRI [mandatory] |
| 1854 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 1855 | |
| 1856 | This macro must be defined to the EL3 exception priority level associated with |
| 1857 | Normal SDEI events on the platform. This must have a higher value (therefore of |
| 1858 | lower priority) than ``PLAT_SDEI_CRITICAL_PRI``. |
| 1859 | |
| 1860 | Macro: PLAT_SDEI_CRITICAL_PRI [mandatory] |
| 1861 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 1862 | |
| 1863 | This macro must be defined to the EL3 exception priority level associated with |
| 1864 | Critical SDEI events on the platform. This must have a lower value (therefore of |
| 1865 | higher priority) than ``PLAT_SDEI_NORMAL_PRI``. |
| 1866 | |
Jeenu Viswambharan | f2928f5 | 2018-01-16 09:29:30 +0000 | [diff] [blame] | 1867 | **Note**: SDEI exception priorities must be the lowest among Secure priorities. |
| 1868 | Among the SDEI exceptions, Critical SDEI priority must be higher than Normal |
| 1869 | SDEI priority. |
Jeenu Viswambharan | b7cb133 | 2017-10-16 08:43:14 +0100 | [diff] [blame] | 1870 | |
| 1871 | Functions |
| 1872 | ......... |
| 1873 | |
| 1874 | Function: int plat_sdei_validate_entry_point(uintptr_t ep) [optional] |
| 1875 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 1876 | |
| 1877 | :: |
| 1878 | |
| 1879 | Argument: uintptr_t |
| 1880 | Return: int |
| 1881 | |
| 1882 | This function validates the address of client entry points provided for both |
| 1883 | event registration and *Complete and Resume* SDEI calls. The function takes one |
| 1884 | argument, which is the address of the handler the SDEI client requested to |
| 1885 | register. The function must return ``0`` for successful validation, or ``-1`` |
| 1886 | upon failure. |
| 1887 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1888 | The default implementation always returns ``0``. On Arm platforms, this function |
Jeenu Viswambharan | b7cb133 | 2017-10-16 08:43:14 +0100 | [diff] [blame] | 1889 | is implemented to translate the entry point to physical address, and further to |
| 1890 | ensure that the address is located in Non-secure DRAM. |
| 1891 | |
| 1892 | Function: void plat_sdei_handle_masked_trigger(uint64_t mpidr, unsigned int intr) [optional] |
| 1893 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 1894 | |
| 1895 | :: |
| 1896 | |
| 1897 | Argument: uint64_t |
| 1898 | Argument: unsigned int |
| 1899 | Return: void |
| 1900 | |
| 1901 | SDEI specification requires that a PE comes out of reset with the events masked. |
| 1902 | The client therefore is expected to call ``PE_UNMASK`` to unmask SDEI events on |
| 1903 | the PE. No SDEI events can be dispatched until such time. |
| 1904 | |
| 1905 | Should a PE receive an interrupt that was bound to an SDEI event while the |
| 1906 | events are masked on the PE, the dispatcher implementation invokes the function |
| 1907 | ``plat_sdei_handle_masked_trigger``. The MPIDR of the PE that received the |
| 1908 | interrupt and the interrupt ID are passed as parameters. |
| 1909 | |
| 1910 | The default implementation only prints out a warning message. |
| 1911 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1912 | Power State Coordination Interface (in BL31) |
| 1913 | -------------------------------------------- |
| 1914 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 1915 | The TF-A implementation of the PSCI API is based around the concept of a |
| 1916 | *power domain*. A *power domain* is a CPU or a logical group of CPUs which |
| 1917 | share some state on which power management operations can be performed as |
| 1918 | specified by `PSCI`_. Each CPU in the system is assigned a cpu index which is |
| 1919 | a unique number between ``0`` and ``PLATFORM_CORE_COUNT - 1``. The |
| 1920 | *power domains* are arranged in a hierarchical tree structure and each |
| 1921 | *power domain* can be identified in a system by the cpu index of any CPU that |
| 1922 | is part of that domain and a *power domain level*. A processing element (for |
| 1923 | example, a CPU) is at level 0. If the *power domain* node above a CPU is a |
| 1924 | logical grouping of CPUs that share some state, then level 1 is that group of |
| 1925 | CPUs (for example, a cluster), and level 2 is a group of clusters (for |
| 1926 | example, the system). More details on the power domain topology and its |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1927 | organization can be found in `Power Domain Topology Design`_. |
| 1928 | |
| 1929 | BL31's platform initialization code exports a pointer to the platform-specific |
| 1930 | power management operations required for the PSCI implementation to function |
| 1931 | correctly. This information is populated in the ``plat_psci_ops`` structure. The |
| 1932 | PSCI implementation calls members of the ``plat_psci_ops`` structure for performing |
| 1933 | power management operations on the power domains. For example, the target |
| 1934 | CPU is specified by its ``MPIDR`` in a PSCI ``CPU_ON`` call. The ``pwr_domain_on()`` |
| 1935 | handler (if present) is called for the CPU power domain. |
| 1936 | |
| 1937 | The ``power-state`` parameter of a PSCI ``CPU_SUSPEND`` call can be used to |
| 1938 | describe composite power states specific to a platform. The PSCI implementation |
Antonio Nino Diaz | 7330861 | 2019-02-28 13:35:21 +0000 | [diff] [blame] | 1939 | defines a generic representation of the power-state parameter, which is an |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1940 | array of local power states where each index corresponds to a power domain |
| 1941 | level. Each entry contains the local power state the power domain at that power |
| 1942 | level could enter. It depends on the ``validate_power_state()`` handler to |
| 1943 | convert the power-state parameter (possibly encoding a composite power state) |
| 1944 | passed in a PSCI ``CPU_SUSPEND`` call to this representation. |
| 1945 | |
| 1946 | The following functions form part of platform port of PSCI functionality. |
| 1947 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1948 | Function : plat_psci_stat_accounting_start() [optional] |
| 1949 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1950 | |
| 1951 | :: |
| 1952 | |
| 1953 | Argument : const psci_power_state_t * |
| 1954 | Return : void |
| 1955 | |
| 1956 | This is an optional hook that platforms can implement for residency statistics |
| 1957 | accounting before entering a low power state. The ``pwr_domain_state`` field of |
| 1958 | ``state_info`` (first argument) can be inspected if stat accounting is done |
| 1959 | differently at CPU level versus higher levels. As an example, if the element at |
| 1960 | index 0 (CPU power level) in the ``pwr_domain_state`` array indicates a power down |
| 1961 | state, special hardware logic may be programmed in order to keep track of the |
| 1962 | residency statistics. For higher levels (array indices > 0), the residency |
| 1963 | statistics could be tracked in software using PMF. If ``ENABLE_PMF`` is set, the |
| 1964 | default implementation will use PMF to capture timestamps. |
| 1965 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1966 | Function : plat_psci_stat_accounting_stop() [optional] |
| 1967 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1968 | |
| 1969 | :: |
| 1970 | |
| 1971 | Argument : const psci_power_state_t * |
| 1972 | Return : void |
| 1973 | |
| 1974 | This is an optional hook that platforms can implement for residency statistics |
| 1975 | accounting after exiting from a low power state. The ``pwr_domain_state`` field |
| 1976 | of ``state_info`` (first argument) can be inspected if stat accounting is done |
| 1977 | differently at CPU level versus higher levels. As an example, if the element at |
| 1978 | index 0 (CPU power level) in the ``pwr_domain_state`` array indicates a power down |
| 1979 | state, special hardware logic may be programmed in order to keep track of the |
| 1980 | residency statistics. For higher levels (array indices > 0), the residency |
| 1981 | statistics could be tracked in software using PMF. If ``ENABLE_PMF`` is set, the |
| 1982 | default implementation will use PMF to capture timestamps. |
| 1983 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 1984 | Function : plat_psci_stat_get_residency() [optional] |
| 1985 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 1986 | |
| 1987 | :: |
| 1988 | |
| 1989 | Argument : unsigned int, const psci_power_state_t *, int |
| 1990 | Return : u_register_t |
| 1991 | |
| 1992 | This is an optional interface that is is invoked after resuming from a low power |
| 1993 | state and provides the time spent resident in that low power state by the power |
| 1994 | domain at a particular power domain level. When a CPU wakes up from suspend, |
| 1995 | all its parent power domain levels are also woken up. The generic PSCI code |
| 1996 | invokes this function for each parent power domain that is resumed and it |
| 1997 | identified by the ``lvl`` (first argument) parameter. The ``state_info`` (second |
| 1998 | argument) describes the low power state that the power domain has resumed from. |
| 1999 | The current CPU is the first CPU in the power domain to resume from the low |
| 2000 | power state and the ``last_cpu_idx`` (third parameter) is the index of the last |
| 2001 | CPU in the power domain to suspend and may be needed to calculate the residency |
| 2002 | for that power domain. |
| 2003 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2004 | Function : plat_get_target_pwr_state() [optional] |
| 2005 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2006 | |
| 2007 | :: |
| 2008 | |
| 2009 | Argument : unsigned int, const plat_local_state_t *, unsigned int |
| 2010 | Return : plat_local_state_t |
| 2011 | |
| 2012 | The PSCI generic code uses this function to let the platform participate in |
| 2013 | state coordination during a power management operation. The function is passed |
| 2014 | a pointer to an array of platform specific local power state ``states`` (second |
| 2015 | argument) which contains the requested power state for each CPU at a particular |
| 2016 | power domain level ``lvl`` (first argument) within the power domain. The function |
| 2017 | is expected to traverse this array of upto ``ncpus`` (third argument) and return |
| 2018 | a coordinated target power state by the comparing all the requested power |
| 2019 | states. The target power state should not be deeper than any of the requested |
| 2020 | power states. |
| 2021 | |
| 2022 | A weak definition of this API is provided by default wherein it assumes |
| 2023 | that the platform assigns a local state value in order of increasing depth |
| 2024 | of the power state i.e. for two power states X & Y, if X < Y |
| 2025 | then X represents a shallower power state than Y. As a result, the |
| 2026 | coordinated target local power state for a power domain will be the minimum |
| 2027 | of the requested local power state values. |
| 2028 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2029 | Function : plat_get_power_domain_tree_desc() [mandatory] |
| 2030 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2031 | |
| 2032 | :: |
| 2033 | |
| 2034 | Argument : void |
| 2035 | Return : const unsigned char * |
| 2036 | |
| 2037 | This function returns a pointer to the byte array containing the power domain |
| 2038 | topology tree description. The format and method to construct this array are |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 2039 | described in `Power Domain Topology Design`_. The BL31 PSCI initialization code |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2040 | requires this array to be described by the platform, either statically or |
| 2041 | dynamically, to initialize the power domain topology tree. In case the array |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2042 | is populated dynamically, then plat_core_pos_by_mpidr() and |
| 2043 | plat_my_core_pos() should also be implemented suitably so that the topology |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2044 | tree description matches the CPU indices returned by these APIs. These APIs |
| 2045 | together form the platform interface for the PSCI topology framework. |
| 2046 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2047 | Function : plat_setup_psci_ops() [mandatory] |
| 2048 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2049 | |
| 2050 | :: |
| 2051 | |
| 2052 | Argument : uintptr_t, const plat_psci_ops ** |
| 2053 | Return : int |
| 2054 | |
| 2055 | This function may execute with the MMU and data caches enabled if the platform |
| 2056 | port does the necessary initializations in ``bl31_plat_arch_setup()``. It is only |
| 2057 | called by the primary CPU. |
| 2058 | |
| 2059 | This function is called by PSCI initialization code. Its purpose is to let |
| 2060 | the platform layer know about the warm boot entrypoint through the |
| 2061 | ``sec_entrypoint`` (first argument) and to export handler routines for |
| 2062 | platform-specific psci power management actions by populating the passed |
| 2063 | pointer with a pointer to BL31's private ``plat_psci_ops`` structure. |
| 2064 | |
| 2065 | A description of each member of this structure is given below. Please refer to |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2066 | the Arm FVP specific implementation of these handlers in |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2067 | `plat/arm/board/fvp/fvp_pm.c`_ as an example. For each PSCI function that the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2068 | platform wants to support, the associated operation or operations in this |
| 2069 | structure must be provided and implemented (Refer section 4 of |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2070 | `Firmware Design`_ for the PSCI API supported in TF-A). To disable a PSCI |
| 2071 | function in a platform port, the operation should be removed from this |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2072 | structure instead of providing an empty implementation. |
| 2073 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2074 | plat_psci_ops.cpu_standby() |
| 2075 | ........................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2076 | |
| 2077 | Perform the platform-specific actions to enter the standby state for a cpu |
| 2078 | indicated by the passed argument. This provides a fast path for CPU standby |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 2079 | wherein overheads of PSCI state management and lock acquisition is avoided. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2080 | For this handler to be invoked by the PSCI ``CPU_SUSPEND`` API implementation, |
| 2081 | the suspend state type specified in the ``power-state`` parameter should be |
| 2082 | STANDBY and the target power domain level specified should be the CPU. The |
| 2083 | handler should put the CPU into a low power retention state (usually by |
| 2084 | issuing a wfi instruction) and ensure that it can be woken up from that |
| 2085 | state by a normal interrupt. The generic code expects the handler to succeed. |
| 2086 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2087 | plat_psci_ops.pwr_domain_on() |
| 2088 | ............................. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2089 | |
| 2090 | Perform the platform specific actions to power on a CPU, specified |
| 2091 | by the ``MPIDR`` (first argument). The generic code expects the platform to |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2092 | return PSCI_E_SUCCESS on success or PSCI_E_INTERN_FAIL for any failure. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2093 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2094 | plat_psci_ops.pwr_domain_off() |
| 2095 | .............................. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2096 | |
| 2097 | Perform the platform specific actions to prepare to power off the calling CPU |
| 2098 | and its higher parent power domain levels as indicated by the ``target_state`` |
| 2099 | (first argument). It is called by the PSCI ``CPU_OFF`` API implementation. |
| 2100 | |
| 2101 | The ``target_state`` encodes the platform coordinated target local power states |
| 2102 | for the CPU power domain and its parent power domain levels. The handler |
| 2103 | needs to perform power management operation corresponding to the local state |
| 2104 | at each power level. |
| 2105 | |
| 2106 | For this handler, the local power state for the CPU power domain will be a |
| 2107 | power down state where as it could be either power down, retention or run state |
| 2108 | for the higher power domain levels depending on the result of state |
| 2109 | coordination. The generic code expects the handler to succeed. |
| 2110 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2111 | plat_psci_ops.pwr_domain_suspend_pwrdown_early() [optional] |
| 2112 | ........................................................... |
Varun Wadekar | 1862d62 | 2017-07-10 16:02:05 -0700 | [diff] [blame] | 2113 | |
| 2114 | This optional function may be used as a performance optimization to replace |
| 2115 | or complement pwr_domain_suspend() on some platforms. Its calling semantics |
| 2116 | are identical to pwr_domain_suspend(), except the PSCI implementation only |
| 2117 | calls this function when suspending to a power down state, and it guarantees |
| 2118 | that data caches are enabled. |
| 2119 | |
| 2120 | When HW_ASSISTED_COHERENCY = 0, the PSCI implementation disables data caches |
| 2121 | before calling pwr_domain_suspend(). If the target_state corresponds to a |
| 2122 | power down state and it is safe to perform some or all of the platform |
| 2123 | specific actions in that function with data caches enabled, it may be more |
| 2124 | efficient to move those actions to this function. When HW_ASSISTED_COHERENCY |
| 2125 | = 1, data caches remain enabled throughout, and so there is no advantage to |
| 2126 | moving platform specific actions to this function. |
| 2127 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2128 | plat_psci_ops.pwr_domain_suspend() |
| 2129 | .................................. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2130 | |
| 2131 | Perform the platform specific actions to prepare to suspend the calling |
| 2132 | CPU and its higher parent power domain levels as indicated by the |
| 2133 | ``target_state`` (first argument). It is called by the PSCI ``CPU_SUSPEND`` |
| 2134 | API implementation. |
| 2135 | |
| 2136 | The ``target_state`` has a similar meaning as described in |
| 2137 | the ``pwr_domain_off()`` operation. It encodes the platform coordinated |
| 2138 | target local power states for the CPU power domain and its parent |
| 2139 | power domain levels. The handler needs to perform power management operation |
| 2140 | corresponding to the local state at each power level. The generic code |
| 2141 | expects the handler to succeed. |
| 2142 | |
Douglas Raillard | c5229f8 | 2017-08-02 16:57:32 +0100 | [diff] [blame] | 2143 | The difference between turning a power domain off versus suspending it is that |
| 2144 | in the former case, the power domain is expected to re-initialize its state |
| 2145 | when it is next powered on (see ``pwr_domain_on_finish()``). In the latter |
| 2146 | case, the power domain is expected to save enough state so that it can resume |
| 2147 | execution by restoring this state when its powered on (see |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2148 | ``pwr_domain_suspend_finish()``). |
| 2149 | |
Douglas Raillard | c5229f8 | 2017-08-02 16:57:32 +0100 | [diff] [blame] | 2150 | When suspending a core, the platform can also choose to power off the GICv3 |
| 2151 | Redistributor and ITS through an implementation-defined sequence. To achieve |
| 2152 | this safely, the ITS context must be saved first. The architectural part is |
| 2153 | implemented by the ``gicv3_its_save_disable()`` helper, but most of the needed |
| 2154 | sequence is implementation defined and it is therefore the responsibility of |
| 2155 | the platform code to implement the necessary sequence. Then the GIC |
| 2156 | Redistributor context can be saved using the ``gicv3_rdistif_save()`` helper. |
| 2157 | Powering off the Redistributor requires the implementation to support it and it |
| 2158 | is the responsibility of the platform code to execute the right implementation |
| 2159 | defined sequence. |
| 2160 | |
| 2161 | When a system suspend is requested, the platform can also make use of the |
| 2162 | ``gicv3_distif_save()`` helper to save the context of the GIC Distributor after |
| 2163 | it has saved the context of the Redistributors and ITS of all the cores in the |
| 2164 | system. The context of the Distributor can be large and may require it to be |
| 2165 | allocated in a special area if it cannot fit in the platform's global static |
| 2166 | data, for example in DRAM. The Distributor can then be powered down using an |
| 2167 | implementation-defined sequence. |
| 2168 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2169 | plat_psci_ops.pwr_domain_pwr_down_wfi() |
| 2170 | ....................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2171 | |
| 2172 | This is an optional function and, if implemented, is expected to perform |
| 2173 | platform specific actions including the ``wfi`` invocation which allows the |
| 2174 | CPU to powerdown. Since this function is invoked outside the PSCI locks, |
| 2175 | the actions performed in this hook must be local to the CPU or the platform |
| 2176 | must ensure that races between multiple CPUs cannot occur. |
| 2177 | |
| 2178 | The ``target_state`` has a similar meaning as described in the ``pwr_domain_off()`` |
| 2179 | operation and it encodes the platform coordinated target local power states for |
| 2180 | the CPU power domain and its parent power domain levels. This function must |
| 2181 | not return back to the caller. |
| 2182 | |
| 2183 | If this function is not implemented by the platform, PSCI generic |
| 2184 | implementation invokes ``psci_power_down_wfi()`` for power down. |
| 2185 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2186 | plat_psci_ops.pwr_domain_on_finish() |
| 2187 | .................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2188 | |
| 2189 | This function is called by the PSCI implementation after the calling CPU is |
| 2190 | powered on and released from reset in response to an earlier PSCI ``CPU_ON`` call. |
| 2191 | It performs the platform-specific setup required to initialize enough state for |
| 2192 | this CPU to enter the normal world and also provide secure runtime firmware |
| 2193 | services. |
| 2194 | |
| 2195 | The ``target_state`` (first argument) is the prior state of the power domains |
| 2196 | immediately before the CPU was turned on. It indicates which power domains |
| 2197 | above the CPU might require initialization due to having previously been in |
| 2198 | low power states. The generic code expects the handler to succeed. |
| 2199 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2200 | plat_psci_ops.pwr_domain_suspend_finish() |
| 2201 | ......................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2202 | |
| 2203 | This function is called by the PSCI implementation after the calling CPU is |
| 2204 | powered on and released from reset in response to an asynchronous wakeup |
| 2205 | event, for example a timer interrupt that was programmed by the CPU during the |
| 2206 | ``CPU_SUSPEND`` call or ``SYSTEM_SUSPEND`` call. It performs the platform-specific |
| 2207 | setup required to restore the saved state for this CPU to resume execution |
| 2208 | in the normal world and also provide secure runtime firmware services. |
| 2209 | |
| 2210 | The ``target_state`` (first argument) has a similar meaning as described in |
| 2211 | the ``pwr_domain_on_finish()`` operation. The generic code expects the platform |
| 2212 | to succeed. |
| 2213 | |
Douglas Raillard | c5229f8 | 2017-08-02 16:57:32 +0100 | [diff] [blame] | 2214 | If the Distributor, Redistributors or ITS have been powered off as part of a |
| 2215 | suspend, their context must be restored in this function in the reverse order |
| 2216 | to how they were saved during suspend sequence. |
| 2217 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2218 | plat_psci_ops.system_off() |
| 2219 | .......................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2220 | |
| 2221 | This function is called by PSCI implementation in response to a ``SYSTEM_OFF`` |
| 2222 | call. It performs the platform-specific system poweroff sequence after |
| 2223 | notifying the Secure Payload Dispatcher. |
| 2224 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2225 | plat_psci_ops.system_reset() |
| 2226 | ............................ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2227 | |
| 2228 | This function is called by PSCI implementation in response to a ``SYSTEM_RESET`` |
| 2229 | call. It performs the platform-specific system reset sequence after |
| 2230 | notifying the Secure Payload Dispatcher. |
| 2231 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2232 | plat_psci_ops.validate_power_state() |
| 2233 | .................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2234 | |
| 2235 | This function is called by the PSCI implementation during the ``CPU_SUSPEND`` |
| 2236 | call to validate the ``power_state`` parameter of the PSCI API and if valid, |
| 2237 | populate it in ``req_state`` (second argument) array as power domain level |
| 2238 | specific local states. If the ``power_state`` is invalid, the platform must |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2239 | return PSCI_E_INVALID_PARAMS as error, which is propagated back to the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2240 | normal world PSCI client. |
| 2241 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2242 | plat_psci_ops.validate_ns_entrypoint() |
| 2243 | ...................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2244 | |
| 2245 | This function is called by the PSCI implementation during the ``CPU_SUSPEND``, |
| 2246 | ``SYSTEM_SUSPEND`` and ``CPU_ON`` calls to validate the non-secure ``entry_point`` |
| 2247 | parameter passed by the normal world. If the ``entry_point`` is invalid, |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2248 | the platform must return PSCI_E_INVALID_ADDRESS as error, which is |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2249 | propagated back to the normal world PSCI client. |
| 2250 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2251 | plat_psci_ops.get_sys_suspend_power_state() |
| 2252 | ........................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2253 | |
| 2254 | This function is called by the PSCI implementation during the ``SYSTEM_SUSPEND`` |
| 2255 | call to get the ``req_state`` parameter from platform which encodes the power |
| 2256 | domain level specific local states to suspend to system affinity level. The |
| 2257 | ``req_state`` will be utilized to do the PSCI state coordination and |
| 2258 | ``pwr_domain_suspend()`` will be invoked with the coordinated target state to |
| 2259 | enter system suspend. |
| 2260 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2261 | plat_psci_ops.get_pwr_lvl_state_idx() |
| 2262 | ..................................... |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2263 | |
| 2264 | This is an optional function and, if implemented, is invoked by the PSCI |
| 2265 | implementation to convert the ``local_state`` (first argument) at a specified |
| 2266 | ``pwr_lvl`` (second argument) to an index between 0 and |
| 2267 | ``PLAT_MAX_PWR_LVL_STATES`` - 1. This function is only needed if the platform |
| 2268 | supports more than two local power states at each power domain level, that is |
| 2269 | ``PLAT_MAX_PWR_LVL_STATES`` is greater than 2, and needs to account for these |
| 2270 | local power states. |
| 2271 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2272 | plat_psci_ops.translate_power_state_by_mpidr() |
| 2273 | .............................................. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2274 | |
| 2275 | This is an optional function and, if implemented, verifies the ``power_state`` |
| 2276 | (second argument) parameter of the PSCI API corresponding to a target power |
| 2277 | domain. The target power domain is identified by using both ``MPIDR`` (first |
| 2278 | argument) and the power domain level encoded in ``power_state``. The power domain |
| 2279 | level specific local states are to be extracted from ``power_state`` and be |
| 2280 | populated in the ``output_state`` (third argument) array. The functionality |
| 2281 | is similar to the ``validate_power_state`` function described above and is |
| 2282 | envisaged to be used in case the validity of ``power_state`` depend on the |
| 2283 | targeted power domain. If the ``power_state`` is invalid for the targeted power |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2284 | domain, the platform must return PSCI_E_INVALID_PARAMS as error. If this |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2285 | function is not implemented, then the generic implementation relies on |
| 2286 | ``validate_power_state`` function to translate the ``power_state``. |
| 2287 | |
| 2288 | This function can also be used in case the platform wants to support local |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2289 | power state encoding for ``power_state`` parameter of PSCI_STAT_COUNT/RESIDENCY |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2290 | APIs as described in Section 5.18 of `PSCI`_. |
| 2291 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2292 | plat_psci_ops.get_node_hw_state() |
| 2293 | ................................. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2294 | |
| 2295 | This is an optional function. If implemented this function is intended to return |
| 2296 | the power state of a node (identified by the first parameter, the ``MPIDR``) in |
| 2297 | the power domain topology (identified by the second parameter, ``power_level``), |
| 2298 | as retrieved from a power controller or equivalent component on the platform. |
| 2299 | Upon successful completion, the implementation must map and return the final |
| 2300 | status among ``HW_ON``, ``HW_OFF`` or ``HW_STANDBY``. Upon encountering failures, it |
| 2301 | must return either ``PSCI_E_INVALID_PARAMS`` or ``PSCI_E_NOT_SUPPORTED`` as |
| 2302 | appropriate. |
| 2303 | |
| 2304 | Implementations are not expected to handle ``power_levels`` greater than |
| 2305 | ``PLAT_MAX_PWR_LVL``. |
| 2306 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2307 | plat_psci_ops.system_reset2() |
| 2308 | ............................. |
Roberto Vargas | fe3e40e | 2017-09-12 10:28:35 +0100 | [diff] [blame] | 2309 | |
| 2310 | This is an optional function. If implemented this function is |
| 2311 | called during the ``SYSTEM_RESET2`` call to perform a reset |
| 2312 | based on the first parameter ``reset_type`` as specified in |
| 2313 | `PSCI`_. The parameter ``cookie`` can be used to pass additional |
| 2314 | reset information. If the ``reset_type`` is not supported, the |
| 2315 | function must return ``PSCI_E_NOT_SUPPORTED``. For architectural |
| 2316 | resets, all failures must return ``PSCI_E_INVALID_PARAMETERS`` |
| 2317 | and vendor reset can return other PSCI error codes as defined |
| 2318 | in `PSCI`_. On success this function will not return. |
| 2319 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2320 | plat_psci_ops.write_mem_protect() |
| 2321 | ................................. |
Roberto Vargas | fe3e40e | 2017-09-12 10:28:35 +0100 | [diff] [blame] | 2322 | |
| 2323 | This is an optional function. If implemented it enables or disables the |
| 2324 | ``MEM_PROTECT`` functionality based on the value of ``val``. |
| 2325 | A non-zero value enables ``MEM_PROTECT`` and a value of zero |
| 2326 | disables it. Upon encountering failures it must return a negative value |
| 2327 | and on success it must return 0. |
| 2328 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2329 | plat_psci_ops.read_mem_protect() |
| 2330 | ................................ |
Roberto Vargas | fe3e40e | 2017-09-12 10:28:35 +0100 | [diff] [blame] | 2331 | |
| 2332 | This is an optional function. If implemented it returns the current |
| 2333 | state of ``MEM_PROTECT`` via the ``val`` parameter. Upon encountering |
| 2334 | failures it must return a negative value and on success it must |
| 2335 | return 0. |
| 2336 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2337 | plat_psci_ops.mem_protect_chk() |
| 2338 | ............................... |
Roberto Vargas | fe3e40e | 2017-09-12 10:28:35 +0100 | [diff] [blame] | 2339 | |
| 2340 | This is an optional function. If implemented it checks if a memory |
| 2341 | region defined by a base address ``base`` and with a size of ``length`` |
| 2342 | bytes is protected by ``MEM_PROTECT``. If the region is protected |
| 2343 | then it must return 0, otherwise it must return a negative number. |
| 2344 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2345 | Interrupt Management framework (in BL31) |
| 2346 | ---------------------------------------- |
| 2347 | |
| 2348 | BL31 implements an Interrupt Management Framework (IMF) to manage interrupts |
| 2349 | generated in either security state and targeted to EL1 or EL2 in the non-secure |
| 2350 | state or EL3/S-EL1 in the secure state. The design of this framework is |
| 2351 | described in the `IMF Design Guide`_ |
| 2352 | |
| 2353 | A platform should export the following APIs to support the IMF. The following |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 2354 | text briefly describes each API and its implementation in Arm standard |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2355 | platforms. The API implementation depends upon the type of interrupt controller |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2356 | present in the platform. Arm standard platform layer supports both |
| 2357 | `Arm Generic Interrupt Controller version 2.0 (GICv2)`_ |
| 2358 | and `3.0 (GICv3)`_. Juno builds the Arm platform layer to use GICv2 and the |
| 2359 | FVP can be configured to use either GICv2 or GICv3 depending on the build flag |
| 2360 | ``FVP_USE_GIC_DRIVER`` (See FVP platform specific build options in |
| 2361 | `User Guide`_ for more details). |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2362 | |
Jeenu Viswambharan | eb68ea9 | 2017-09-22 08:32:09 +0100 | [diff] [blame] | 2363 | See also: `Interrupt Controller Abstraction APIs`__. |
| 2364 | |
| 2365 | .. __: platform-interrupt-controller-API.rst |
| 2366 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2367 | Function : plat_interrupt_type_to_line() [mandatory] |
| 2368 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2369 | |
| 2370 | :: |
| 2371 | |
| 2372 | Argument : uint32_t, uint32_t |
| 2373 | Return : uint32_t |
| 2374 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2375 | The Arm processor signals an interrupt exception either through the IRQ or FIQ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2376 | interrupt line. The specific line that is signaled depends on how the interrupt |
| 2377 | controller (IC) reports different interrupt types from an execution context in |
| 2378 | either security state. The IMF uses this API to determine which interrupt line |
| 2379 | the platform IC uses to signal each type of interrupt supported by the framework |
| 2380 | from a given security state. This API must be invoked at EL3. |
| 2381 | |
| 2382 | The first parameter will be one of the ``INTR_TYPE_*`` values (see |
| 2383 | `IMF Design Guide`_) indicating the target type of the interrupt, the second parameter is the |
| 2384 | security state of the originating execution context. The return result is the |
| 2385 | bit position in the ``SCR_EL3`` register of the respective interrupt trap: IRQ=1, |
| 2386 | FIQ=2. |
| 2387 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2388 | In the case of Arm standard platforms using GICv2, S-EL1 interrupts are |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2389 | configured as FIQs and Non-secure interrupts as IRQs from either security |
| 2390 | state. |
| 2391 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2392 | In the case of Arm standard platforms using GICv3, the interrupt line to be |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2393 | configured depends on the security state of the execution context when the |
| 2394 | interrupt is signalled and are as follows: |
| 2395 | |
| 2396 | - The S-EL1 interrupts are signaled as IRQ in S-EL0/1 context and as FIQ in |
| 2397 | NS-EL0/1/2 context. |
| 2398 | - The Non secure interrupts are signaled as FIQ in S-EL0/1 context and as IRQ |
| 2399 | in the NS-EL0/1/2 context. |
| 2400 | - The EL3 interrupts are signaled as FIQ in both S-EL0/1 and NS-EL0/1/2 |
| 2401 | context. |
| 2402 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2403 | Function : plat_ic_get_pending_interrupt_type() [mandatory] |
| 2404 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2405 | |
| 2406 | :: |
| 2407 | |
| 2408 | Argument : void |
| 2409 | Return : uint32_t |
| 2410 | |
| 2411 | This API returns the type of the highest priority pending interrupt at the |
| 2412 | platform IC. The IMF uses the interrupt type to retrieve the corresponding |
| 2413 | handler function. ``INTR_TYPE_INVAL`` is returned when there is no interrupt |
| 2414 | pending. The valid interrupt types that can be returned are ``INTR_TYPE_EL3``, |
| 2415 | ``INTR_TYPE_S_EL1`` and ``INTR_TYPE_NS``. This API must be invoked at EL3. |
| 2416 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2417 | In the case of Arm standard platforms using GICv2, the *Highest Priority |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2418 | Pending Interrupt Register* (``GICC_HPPIR``) is read to determine the id of |
| 2419 | the pending interrupt. The type of interrupt depends upon the id value as |
| 2420 | follows. |
| 2421 | |
| 2422 | #. id < 1022 is reported as a S-EL1 interrupt |
| 2423 | #. id = 1022 is reported as a Non-secure interrupt. |
| 2424 | #. id = 1023 is reported as an invalid interrupt type. |
| 2425 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2426 | In the case of Arm standard platforms using GICv3, the system register |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2427 | ``ICC_HPPIR0_EL1``, *Highest Priority Pending group 0 Interrupt Register*, |
| 2428 | is read to determine the id of the pending interrupt. The type of interrupt |
| 2429 | depends upon the id value as follows. |
| 2430 | |
| 2431 | #. id = ``PENDING_G1S_INTID`` (1020) is reported as a S-EL1 interrupt |
| 2432 | #. id = ``PENDING_G1NS_INTID`` (1021) is reported as a Non-secure interrupt. |
| 2433 | #. id = ``GIC_SPURIOUS_INTERRUPT`` (1023) is reported as an invalid interrupt type. |
| 2434 | #. All other interrupt id's are reported as EL3 interrupt. |
| 2435 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2436 | Function : plat_ic_get_pending_interrupt_id() [mandatory] |
| 2437 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2438 | |
| 2439 | :: |
| 2440 | |
| 2441 | Argument : void |
| 2442 | Return : uint32_t |
| 2443 | |
| 2444 | This API returns the id of the highest priority pending interrupt at the |
| 2445 | platform IC. ``INTR_ID_UNAVAILABLE`` is returned when there is no interrupt |
| 2446 | pending. |
| 2447 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2448 | In the case of Arm standard platforms using GICv2, the *Highest Priority |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2449 | Pending Interrupt Register* (``GICC_HPPIR``) is read to determine the id of the |
| 2450 | pending interrupt. The id that is returned by API depends upon the value of |
| 2451 | the id read from the interrupt controller as follows. |
| 2452 | |
| 2453 | #. id < 1022. id is returned as is. |
| 2454 | #. id = 1022. The *Aliased Highest Priority Pending Interrupt Register* |
| 2455 | (``GICC_AHPPIR``) is read to determine the id of the non-secure interrupt. |
| 2456 | This id is returned by the API. |
| 2457 | #. id = 1023. ``INTR_ID_UNAVAILABLE`` is returned. |
| 2458 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2459 | In the case of Arm standard platforms using GICv3, if the API is invoked from |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2460 | EL3, the system register ``ICC_HPPIR0_EL1``, *Highest Priority Pending Interrupt |
| 2461 | group 0 Register*, is read to determine the id of the pending interrupt. The id |
| 2462 | that is returned by API depends upon the value of the id read from the |
| 2463 | interrupt controller as follows. |
| 2464 | |
| 2465 | #. id < ``PENDING_G1S_INTID`` (1020). id is returned as is. |
| 2466 | #. id = ``PENDING_G1S_INTID`` (1020) or ``PENDING_G1NS_INTID`` (1021). The system |
| 2467 | register ``ICC_HPPIR1_EL1``, *Highest Priority Pending Interrupt group 1 |
| 2468 | Register* is read to determine the id of the group 1 interrupt. This id |
| 2469 | is returned by the API as long as it is a valid interrupt id |
| 2470 | #. If the id is any of the special interrupt identifiers, |
| 2471 | ``INTR_ID_UNAVAILABLE`` is returned. |
| 2472 | |
| 2473 | When the API invoked from S-EL1 for GICv3 systems, the id read from system |
| 2474 | register ``ICC_HPPIR1_EL1``, *Highest Priority Pending group 1 Interrupt |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2475 | Register*, is returned if is not equal to GIC_SPURIOUS_INTERRUPT (1023) else |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2476 | ``INTR_ID_UNAVAILABLE`` is returned. |
| 2477 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2478 | Function : plat_ic_acknowledge_interrupt() [mandatory] |
| 2479 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2480 | |
| 2481 | :: |
| 2482 | |
| 2483 | Argument : void |
| 2484 | Return : uint32_t |
| 2485 | |
| 2486 | This API is used by the CPU to indicate to the platform IC that processing of |
Jeenu Viswambharan | 4ee8d0b | 2017-10-24 15:13:59 +0100 | [diff] [blame] | 2487 | the highest pending interrupt has begun. It should return the raw, unmodified |
| 2488 | value obtained from the interrupt controller when acknowledging an interrupt. |
| 2489 | The actual interrupt number shall be extracted from this raw value using the API |
| 2490 | `plat_ic_get_interrupt_id()`__. |
| 2491 | |
| 2492 | .. __: platform-interrupt-controller-API.rst#function-unsigned-int-plat-ic-get-interrupt-id-unsigned-int-raw-optional |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2493 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2494 | This function in Arm standard platforms using GICv2, reads the *Interrupt |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2495 | Acknowledge Register* (``GICC_IAR``). This changes the state of the highest |
| 2496 | priority pending interrupt from pending to active in the interrupt controller. |
Jeenu Viswambharan | 4ee8d0b | 2017-10-24 15:13:59 +0100 | [diff] [blame] | 2497 | It returns the value read from the ``GICC_IAR``, unmodified. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2498 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2499 | In the case of Arm standard platforms using GICv3, if the API is invoked |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2500 | from EL3, the function reads the system register ``ICC_IAR0_EL1``, *Interrupt |
| 2501 | Acknowledge Register group 0*. If the API is invoked from S-EL1, the function |
| 2502 | reads the system register ``ICC_IAR1_EL1``, *Interrupt Acknowledge Register |
| 2503 | group 1*. The read changes the state of the highest pending interrupt from |
| 2504 | pending to active in the interrupt controller. The value read is returned |
Jeenu Viswambharan | 4ee8d0b | 2017-10-24 15:13:59 +0100 | [diff] [blame] | 2505 | unmodified. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2506 | |
| 2507 | The TSP uses this API to start processing of the secure physical timer |
| 2508 | interrupt. |
| 2509 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2510 | Function : plat_ic_end_of_interrupt() [mandatory] |
| 2511 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2512 | |
| 2513 | :: |
| 2514 | |
| 2515 | Argument : uint32_t |
| 2516 | Return : void |
| 2517 | |
| 2518 | This API is used by the CPU to indicate to the platform IC that processing of |
| 2519 | the interrupt corresponding to the id (passed as the parameter) has |
| 2520 | finished. The id should be the same as the id returned by the |
| 2521 | ``plat_ic_acknowledge_interrupt()`` API. |
| 2522 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2523 | Arm standard platforms write the id to the *End of Interrupt Register* |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2524 | (``GICC_EOIR``) in case of GICv2, and to ``ICC_EOIR0_EL1`` or ``ICC_EOIR1_EL1`` |
| 2525 | system register in case of GICv3 depending on where the API is invoked from, |
| 2526 | EL3 or S-EL1. This deactivates the corresponding interrupt in the interrupt |
| 2527 | controller. |
| 2528 | |
| 2529 | The TSP uses this API to finish processing of the secure physical timer |
| 2530 | interrupt. |
| 2531 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2532 | Function : plat_ic_get_interrupt_type() [mandatory] |
| 2533 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2534 | |
| 2535 | :: |
| 2536 | |
| 2537 | Argument : uint32_t |
| 2538 | Return : uint32_t |
| 2539 | |
| 2540 | This API returns the type of the interrupt id passed as the parameter. |
| 2541 | ``INTR_TYPE_INVAL`` is returned if the id is invalid. If the id is valid, a valid |
| 2542 | interrupt type (one of ``INTR_TYPE_EL3``, ``INTR_TYPE_S_EL1`` and ``INTR_TYPE_NS``) is |
| 2543 | returned depending upon how the interrupt has been configured by the platform |
| 2544 | IC. This API must be invoked at EL3. |
| 2545 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2546 | Arm standard platforms using GICv2 configures S-EL1 interrupts as Group0 interrupts |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2547 | and Non-secure interrupts as Group1 interrupts. It reads the group value |
| 2548 | corresponding to the interrupt id from the relevant *Interrupt Group Register* |
| 2549 | (``GICD_IGROUPRn``). It uses the group value to determine the type of interrupt. |
| 2550 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2551 | In the case of Arm standard platforms using GICv3, both the *Interrupt Group |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2552 | Register* (``GICD_IGROUPRn``) and *Interrupt Group Modifier Register* |
| 2553 | (``GICD_IGRPMODRn``) is read to figure out whether the interrupt is configured |
| 2554 | as Group 0 secure interrupt, Group 1 secure interrupt or Group 1 NS interrupt. |
| 2555 | |
| 2556 | Crash Reporting mechanism (in BL31) |
| 2557 | ----------------------------------- |
| 2558 | |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 2559 | BL31 implements a crash reporting mechanism which prints the various registers |
Antonio Nino Diaz | 6c9ada3 | 2018-10-16 14:32:34 +0100 | [diff] [blame] | 2560 | of the CPU to enable quick crash analysis and debugging. This mechanism relies |
Paul Beesley | 8aabea3 | 2019-01-11 18:26:51 +0000 | [diff] [blame] | 2561 | on the platform implementing ``plat_crash_console_init``, |
Antonio Nino Diaz | 6c9ada3 | 2018-10-16 14:32:34 +0100 | [diff] [blame] | 2562 | ``plat_crash_console_putc`` and ``plat_crash_console_flush``. |
| 2563 | |
| 2564 | The file ``plat/common/aarch64/crash_console_helpers.S`` contains sample |
| 2565 | implementation of all of them. Platforms may include this file to their |
| 2566 | makefiles in order to benefit from them. By default, they will cause the crash |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 2567 | output to be routed over the normal console infrastructure and get printed on |
| 2568 | consoles configured to output in crash state. ``console_set_scope()`` can be |
| 2569 | used to control whether a console is used for crash output. |
Julius Werner | 63c52d0 | 2018-11-19 14:25:55 -0800 | [diff] [blame] | 2570 | NOTE: Platforms are responsible for making sure that they only mark consoles for |
| 2571 | use in the crash scope that are able to support this, i.e. that are written in |
| 2572 | assembly and conform with the register clobber rules for putc() (x0-x2, x16-x17) |
| 2573 | and flush() (x0-x3, x16-x17) crash callbacks. |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 2574 | |
| 2575 | In some cases (such as debugging very early crashes that happen before the |
| 2576 | normal boot console can be set up), platforms may want to control crash output |
Julius Werner | 63c52d0 | 2018-11-19 14:25:55 -0800 | [diff] [blame] | 2577 | more explicitly. These platforms may instead provide custom implementations for |
| 2578 | these. They are executed outside of a C environment and without a stack. Many |
| 2579 | console drivers provide functions named ``console_xxx_core_init/putc/flush`` |
| 2580 | that are designed to be used by these functions. See Arm platforms (like juno) |
| 2581 | for an example of this. |
Antonio Nino Diaz | 6c9ada3 | 2018-10-16 14:32:34 +0100 | [diff] [blame] | 2582 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2583 | Function : plat_crash_console_init [mandatory] |
| 2584 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2585 | |
| 2586 | :: |
| 2587 | |
| 2588 | Argument : void |
| 2589 | Return : int |
| 2590 | |
| 2591 | This API is used by the crash reporting mechanism to initialize the crash |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 2592 | console. It must only use the general purpose registers x0 through x7 to do the |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2593 | initialization and returns 1 on success. |
| 2594 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2595 | Function : plat_crash_console_putc [mandatory] |
| 2596 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2597 | |
| 2598 | :: |
| 2599 | |
| 2600 | Argument : int |
| 2601 | Return : int |
| 2602 | |
| 2603 | This API is used by the crash reporting mechanism to print a character on the |
| 2604 | designated crash console. It must only use general purpose registers x1 and |
| 2605 | x2 to do its work. The parameter and the return value are in general purpose |
| 2606 | register x0. |
| 2607 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2608 | Function : plat_crash_console_flush [mandatory] |
| 2609 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2610 | |
| 2611 | :: |
| 2612 | |
| 2613 | Argument : void |
| 2614 | Return : int |
| 2615 | |
| 2616 | This API is used by the crash reporting mechanism to force write of all buffered |
| 2617 | data on the designated crash console. It should only use general purpose |
Julius Werner | 17cd67d | 2017-09-18 16:49:48 -0700 | [diff] [blame] | 2618 | registers x0 through x5 to do its work. The return value is 0 on successful |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2619 | completion; otherwise the return value is -1. |
| 2620 | |
Jeenu Viswambharan | 63eb241 | 2018-10-12 08:48:36 +0100 | [diff] [blame] | 2621 | External Abort handling and RAS Support |
| 2622 | --------------------------------------- |
Jeenu Viswambharan | 4431aae | 2018-07-12 10:00:01 +0100 | [diff] [blame] | 2623 | |
| 2624 | Function : plat_ea_handler |
| 2625 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2626 | |
| 2627 | :: |
| 2628 | |
| 2629 | Argument : int |
| 2630 | Argument : uint64_t |
| 2631 | Argument : void * |
| 2632 | Argument : void * |
| 2633 | Argument : uint64_t |
| 2634 | Return : void |
| 2635 | |
| 2636 | This function is invoked by the RAS framework for the platform to handle an |
| 2637 | External Abort received at EL3. The intention of the function is to attempt to |
| 2638 | resolve the cause of External Abort and return; if that's not possible, to |
| 2639 | initiate orderly shutdown of the system. |
| 2640 | |
| 2641 | The first parameter (``int ea_reason``) indicates the reason for External Abort. |
| 2642 | Its value is one of ``ERROR_EA_*`` constants defined in ``ea_handle.h``. |
| 2643 | |
| 2644 | The second parameter (``uint64_t syndrome``) is the respective syndrome |
| 2645 | presented to EL3 after having received the External Abort. Depending on the |
| 2646 | nature of the abort (as can be inferred from the ``ea_reason`` parameter), this |
| 2647 | can be the content of either ``ESR_EL3`` or ``DISR_EL1``. |
| 2648 | |
| 2649 | The third parameter (``void *cookie``) is unused for now. The fourth parameter |
| 2650 | (``void *handle``) is a pointer to the preempted context. The fifth parameter |
| 2651 | (``uint64_t flags``) indicates the preempted security state. These parameters |
| 2652 | are received from the top-level exception handler. |
| 2653 | |
| 2654 | If ``RAS_EXTENSION`` is set to ``1``, the default implementation of this |
| 2655 | function iterates through RAS handlers registered by the platform. If any of the |
| 2656 | RAS handlers resolve the External Abort, no further action is taken. |
| 2657 | |
| 2658 | If ``RAS_EXTENSION`` is set to ``0``, or if none of the platform RAS handlers |
| 2659 | could resolve the External Abort, the default implementation prints an error |
| 2660 | message, and panics. |
| 2661 | |
| 2662 | Function : plat_handle_uncontainable_ea |
| 2663 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2664 | |
| 2665 | :: |
| 2666 | |
| 2667 | Argument : int |
| 2668 | Argument : uint64_t |
| 2669 | Return : void |
| 2670 | |
| 2671 | This function is invoked by the RAS framework when an External Abort of |
| 2672 | Uncontainable type is received at EL3. Due to the critical nature of |
| 2673 | Uncontainable errors, the intention of this function is to initiate orderly |
| 2674 | shutdown of the system, and is not expected to return. |
| 2675 | |
| 2676 | This function must be implemented in assembly. |
| 2677 | |
| 2678 | The first and second parameters are the same as that of ``plat_ea_handler``. |
| 2679 | |
| 2680 | The default implementation of this function calls |
| 2681 | ``report_unhandled_exception``. |
| 2682 | |
| 2683 | Function : plat_handle_double_fault |
| 2684 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2685 | |
| 2686 | :: |
| 2687 | |
| 2688 | Argument : int |
| 2689 | Argument : uint64_t |
| 2690 | Return : void |
| 2691 | |
| 2692 | This function is invoked by the RAS framework when another External Abort is |
| 2693 | received at EL3 while one is already being handled. I.e., a call to |
| 2694 | ``plat_ea_handler`` is outstanding. Due to its critical nature, the intention of |
| 2695 | this function is to initiate orderly shutdown of the system, and is not expected |
| 2696 | recover or return. |
| 2697 | |
| 2698 | This function must be implemented in assembly. |
| 2699 | |
| 2700 | The first and second parameters are the same as that of ``plat_ea_handler``. |
| 2701 | |
| 2702 | The default implementation of this function calls |
| 2703 | ``report_unhandled_exception``. |
| 2704 | |
| 2705 | Function : plat_handle_el3_ea |
| 2706 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 2707 | |
| 2708 | :: |
| 2709 | |
| 2710 | Return : void |
| 2711 | |
| 2712 | This function is invoked when an External Abort is received while executing in |
| 2713 | EL3. Due to its critical nature, the intention of this function is to initiate |
| 2714 | orderly shutdown of the system, and is not expected recover or return. |
| 2715 | |
| 2716 | This function must be implemented in assembly. |
| 2717 | |
| 2718 | The default implementation of this function calls |
| 2719 | ``report_unhandled_exception``. |
| 2720 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2721 | Build flags |
| 2722 | ----------- |
| 2723 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2724 | There are some build flags which can be defined by the platform to control |
| 2725 | inclusion or exclusion of certain BL stages from the FIP image. These flags |
| 2726 | need to be defined in the platform makefile which will get included by the |
| 2727 | build system. |
| 2728 | |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2729 | - **NEED_BL33** |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2730 | By default, this flag is defined ``yes`` by the build system and ``BL33`` |
| 2731 | build option should be supplied as a build option. The platform has the |
| 2732 | option of excluding the BL33 image in the ``fip`` image by defining this flag |
| 2733 | to ``no``. If any of the options ``EL3_PAYLOAD_BASE`` or ``PRELOADED_BL33_BASE`` |
| 2734 | are used, this flag will be set to ``no`` automatically. |
| 2735 | |
| 2736 | C Library |
| 2737 | --------- |
| 2738 | |
| 2739 | To avoid subtle toolchain behavioral dependencies, the header files provided |
| 2740 | by the compiler are not used. The software is built with the ``-nostdinc`` flag |
| 2741 | to ensure no headers are included from the toolchain inadvertently. Instead the |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2742 | required headers are included in the TF-A source tree. The library only |
| 2743 | contains those C library definitions required by the local implementation. If |
| 2744 | more functionality is required, the needed library functions will need to be |
| 2745 | added to the local implementation. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2746 | |
Antonio Nino Diaz | 27989a8 | 2018-08-17 10:45:47 +0100 | [diff] [blame] | 2747 | Some C headers have been obtained from `FreeBSD`_ and `SCC`_, while others have |
| 2748 | been written specifically for TF-A. Fome implementation files have been obtained |
| 2749 | from `FreeBSD`_, others have been written specifically for TF-A as well. The |
| 2750 | files can be found in ``include/lib/libc`` and ``lib/libc``. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2751 | |
Sandrine Bailleux | 9aa6b63 | 2019-02-08 14:46:42 +0100 | [diff] [blame] | 2752 | SCC can be found in http://www.simple-cc.org/. A copy of the `FreeBSD`_ sources |
| 2753 | can be obtained from http://github.com/freebsd/freebsd. |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2754 | |
| 2755 | Storage abstraction layer |
| 2756 | ------------------------- |
| 2757 | |
| 2758 | In order to improve platform independence and portability an storage abstraction |
| 2759 | layer is used to load data from non-volatile platform storage. |
| 2760 | |
| 2761 | Each platform should register devices and their drivers via the Storage layer. |
| 2762 | These drivers then need to be initialized by bootloader phases as |
| 2763 | required in their respective ``blx_platform_setup()`` functions. Currently |
| 2764 | storage access is only required by BL1 and BL2 phases. The ``load_image()`` |
| 2765 | function uses the storage layer to access non-volatile platform storage. |
| 2766 | |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2767 | It is mandatory to implement at least one storage driver. For the Arm |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2768 | development platforms the Firmware Image Package (FIP) driver is provided as |
| 2769 | the default means to load data from storage (see the "Firmware Image Package" |
| 2770 | section in the `User Guide`_). The storage layer is described in the header file |
| 2771 | ``include/drivers/io/io_storage.h``. The implementation of the common library |
| 2772 | is in ``drivers/io/io_storage.c`` and the driver files are located in |
| 2773 | ``drivers/io/``. |
| 2774 | |
| 2775 | Each IO driver must provide ``io_dev_*`` structures, as described in |
| 2776 | ``drivers/io/io_driver.h``. These are returned via a mandatory registration |
| 2777 | function that is called on platform initialization. The semi-hosting driver |
| 2778 | implementation in ``io_semihosting.c`` can be used as an example. |
| 2779 | |
| 2780 | The Storage layer provides mechanisms to initialize storage devices before |
| 2781 | IO operations are called. The basic operations supported by the layer |
| 2782 | include ``open()``, ``close()``, ``read()``, ``write()``, ``size()`` and ``seek()``. |
| 2783 | Drivers do not have to implement all operations, but each platform must |
| 2784 | provide at least one driver for a device capable of supporting generic |
| 2785 | operations such as loading a bootloader image. |
| 2786 | |
| 2787 | The current implementation only allows for known images to be loaded by the |
| 2788 | firmware. These images are specified by using their identifiers, as defined in |
Antonio Nino Diaz | 8f457da | 2019-02-13 14:07:38 +0000 | [diff] [blame] | 2789 | ``include/plat/common/common_def.h`` (or a separate header file included from |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2790 | there). The platform layer (``plat_get_image_source()``) then returns a reference |
| 2791 | to a device and a driver-specific ``spec`` which will be understood by the driver |
| 2792 | to allow access to the image data. |
| 2793 | |
| 2794 | The layer is designed in such a way that is it possible to chain drivers with |
| 2795 | other drivers. For example, file-system drivers may be implemented on top of |
| 2796 | physical block devices, both represented by IO devices with corresponding |
| 2797 | drivers. In such a case, the file-system "binding" with the block device may |
| 2798 | be deferred until the file-system device is initialised. |
| 2799 | |
| 2800 | The abstraction currently depends on structures being statically allocated |
| 2801 | by the drivers and callers, as the system does not yet provide a means of |
| 2802 | dynamically allocating memory. This may also have the affect of limiting the |
| 2803 | amount of open resources per driver. |
| 2804 | |
| 2805 | -------------- |
| 2806 | |
Antonio Nino Diaz | 8f457da | 2019-02-13 14:07:38 +0000 | [diff] [blame] | 2807 | *Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.* |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2808 | |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2809 | .. _include/plat/common/platform.h: ../include/plat/common/platform.h |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2810 | .. _include/plat/arm/common/plat_arm.h: ../include/plat/arm/common/plat_arm.h%5D |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2811 | .. _User Guide: user-guide.rst |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2812 | .. _include/plat/common/common_def.h: ../include/plat/common/common_def.h |
| 2813 | .. _include/plat/arm/common/arm_def.h: ../include/plat/arm/common/arm_def.h |
| 2814 | .. _plat/common/aarch64/platform_mp_stack.S: ../plat/common/aarch64/platform_mp_stack.S |
| 2815 | .. _plat/common/aarch64/platform_up_stack.S: ../plat/common/aarch64/platform_up_stack.S |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2816 | .. _For example, define the build flag in platform.mk: PLAT_PL061_MAX_GPIOS%20:=%20160 |
| 2817 | .. _Power Domain Topology Design: psci-pd-tree.rst |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2818 | .. _include/common/bl_common.h: ../include/common/bl_common.h |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2819 | .. _include/lib/aarch32/arch.h: ../include/lib/aarch32/arch.h |
| 2820 | .. _Firmware Design: firmware-design.rst |
| 2821 | .. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022c/DEN0022C_Power_State_Coordination_Interface.pdf |
Sandrine Bailleux | ab4a90c | 2019-02-08 14:44:53 +0100 | [diff] [blame] | 2822 | .. _plat/arm/board/fvp/fvp_pm.c: ../plat/arm/board/fvp/fvp_pm.c |
Soby Mathew | fad365d | 2018-10-02 14:01:03 +0100 | [diff] [blame] | 2823 | .. _Platform compatibility policy: ./platform-compatibility-policy.rst |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2824 | .. _IMF Design Guide: interrupt-framework-design.rst |
Dan Handley | 4def07d | 2018-03-01 18:44:00 +0000 | [diff] [blame] | 2825 | .. _Arm Generic Interrupt Controller version 2.0 (GICv2): http://infocenter.arm.com/help/topic/com.arm.doc.ihi0048b/index.html |
Douglas Raillard | 6f62574 | 2017-06-28 15:23:03 +0100 | [diff] [blame] | 2826 | .. _3.0 (GICv3): http://infocenter.arm.com/help/topic/com.arm.doc.ihi0069b/index.html |
Paul Beesley | dd4e9a7 | 2019-02-08 16:43:05 +0000 | [diff] [blame] | 2827 | .. _FreeBSD: https://www.freebsd.org |
Antonio Nino Diaz | 27989a8 | 2018-08-17 10:45:47 +0100 | [diff] [blame] | 2828 | .. _SCC: http://www.simple-cc.org/ |