Searched refs:parameters (Results 1 – 25 of 36) sorted by relevance
12
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | porting.rst | 59 specific board parameters.
83 This file defines the dram topology and parameters of the target board.
105 Some of the comphy's parameters value depend on the HW connection between
107 wire length. Due to those differences some comphy parameters vary between
109 all relevant comphy parameters. The PHY porting layer specifies which
110 parameters need to be suited and the board designer should provide relevant
117 The parameters for the same type of comphy may vary even for the same
125 defaults. Those default parameters are used only if there is no appropriate
139 - adjust relevant parameters or
143 The final table size with comphy parameters can be different, depending
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/components/spd/ |
| A D | trusty-dispatcher.rst | 11 Boot parameters
14 Custom boot parameters can be passed to Trusty by providing a platform
|
| A D | tlk-dispatcher.rst | 62 Input parameters to TLK
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/misc/ |
| A D | mvebu-ccu.rst | 20 a struct which has 3 parameters:
|
| A D | mvebu-amb.rst | 46 struct which has 2 parameters:
|
| A D | mvebu-io-win.rst | 31 a struct which has 3 parameters:
|
| A D | mvebu-iob.rst | 24 a struct which has 3 parameters:
|
| /arm-trusted-firmware-2.8.0/lib/semihosting/ |
| A D | semihosting.c | 228 uint64_t parameters[] = {reason, subcode}; in semihosting_exit() local
230 (void)semihosting_call(SEMIHOSTING_SYS_EXIT, (uintptr_t)¶meters); in semihosting_exit()
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | auth-framework.rst | 176 extract authentication parameters contained in an image, e.g. if the
177 parameters are stored as X509v3 extensions, the corresponding OID must be
257 #. Extracting parameters used for authenticating an image based upon a
265 check the image integrity and extract the authentication parameters.
282 the same CoT. The number and type of parameters are method specific. These
283 parameters should be obtained from the parent image using the IPM.
320 The Public Key parameters will be represented by the DER encoding of the
336 parameters ALGORITHM.&Type({IOSet}{@algorithm}) OPTIONAL
496 For each method, the AM defines a structure with the parameters required to
538 Storing Authentication parameters
[all …]
|
| A D | reset-design.rst | 144 In this configuration, when the CPU resets to BL31 there should be no parameters
152 receive parameters in registers depending on their actual boot sequence. On
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | cmake_framework.rst | 62 The framework provides a solution to describe the input build parameters, flags,
68 The related parameters shall be packed into a group (or "setting group"). The
126 parameters. It is worth noting the difference between *CONFIG* and *DEFINE*
132 the parameters declared in the setting group. Then we set the target type to
133 executable, and add some source files. Since the target has the parameters from
|
| A D | drtm_poc.rst | 26 and preparing input parameters needed by DRTM. Finally, it invokes the
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | arm-sip-service.rst | 60 The parameters *PC hi* and *PC lo* defines upper and lower words, respectively,
65 switched, the parameters *Cookie hi* and *Cookie lo* are passed in CPU registers
81 - ``STATE_SW_E_PARAM``: If any of the parameters were deemed invalid for
97 String parameters are passed through a shared buffer using a specific union:
379 parameters with filesystem primitives.
|
| A D | debugfs-design.rst | 82 shared buffer is used to pass path string parameters, or e.g. to exchange
|
| A D | granule-protection-tables-design.rst | 61 There are three main parameters that determine how the tables are organized and
210 If an invalid combination of parameters is supplied, the APIs will print an
|
| A D | secure-partition-manager-mm.rst | 339 - Return parameters
538 - Return parameters
583 delegated to the partition. The return parameters describe the next event.
599 event to the Secure Partition. The return parameters of this interface must
662 - Return parameters
761 - Return parameters
|
| A D | sdei.rst | 80 should be used. It accepts two parameters:
126 ``OR``\ ed to form parameters to macros that define events (see
|
| A D | ras.rst | 114 ``cookie``, and ``handle`` parameters from the :ref:`top-level exception handler
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | rt-svc-writers-guide.rst | 70 calling convention, where all parameters are 32-bit, or the SMC64 calling
71 convention, where the parameters are 64-bit. The framework identifies and
217 #. Truncating parameters for calls made using the SMC32 calling convention.
225 For such calls, the upper bits of the parameters x1-x4 and the saved
226 parameters X5-X7 are UNDEFINED and must be explicitly ignored by the
229 to handle individual SMC Functions use appropriate 32-bit parameters.
232 immediate parameters x1-x4 and/or the additional saved parameters X5-X7.
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/fvp/ |
| A D | index.rst | 186 using the following model parameters:
216 model parameters:
361 The following ``Foundation_Platform`` parameters should be used to boot Linux with
398 The following ``FVP_Base_RevC-2xAEMv8A`` parameters should be used to boot Linux
422 The following ``FVP_Base_AEMv8A-AEMv8A`` parameters should be used to boot Linux
450 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
468 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
487 The following ``FVP_Base_RevC-2xAEMv8A`` parameters should be used to boot Linux
543 The following ``FVP_Base_AEMv8A-AEMv8A`` parameters should be used to boot Linux
584 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/fvp-ve/ |
| A D | index.rst | 72 The following model parameters should be used to boot Linux using the build of
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A D | security-advisory-tfv-4.rst | 47 overflows when the sum of its two parameters fall into the ``[2^32, 2^64 - 1]``
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | rz-g2.rst | 77 memory (BOOT_KIND_BASE) together with the BL31 parameters
|
| A D | rcar-gen3.rst | 82 memory (BOOT_KIND_BASE) together with the BL31 parameters
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/juno/ |
| A D | index.rst | 144 - The following parameters should be used to build BL1 and BL2 in AArch64
|
Completed in 27 milliseconds
12