| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H 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 …]
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | trusty-dispatcher.rst | 11 Boot parameters
14 Custom boot parameters can be passed to Trusty by providing a platform
|
| H A D | tlk-dispatcher.rst | 62 Input parameters to TLK
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-cortex-a32.rst | 7 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
25 The following ``FVP_Base_Cortex-A32x4`` model parameters should be used to
|
| H A D | fvp-cortex-a57-a53.rst | 7 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
25 The following ``FVP_Base_Cortex-A57x4-A53x4`` model parameters should be used to
|
| H A D | fvp-aemv8-base.rst | 7 The following ``FVP_Base_RevC-2xAEMv8A`` parameters should be used to boot Linux
31 The following ``FVP_Base_AEMv8A-AEMv8A`` parameters should be used to boot Linux
59 The following ``FVP_Base_RevC-2xAEMv8A`` parameters should be used to boot Linux
114 The following ``FVP_Base_AEMv8A-AEMv8A`` parameters should be used to boot Linux
|
| H A D | fvp-foundation.rst | 4 The following ``Foundation_Platform`` parameters should be used to boot Linux with
|
| H A D | fvp-specific-configs.rst | 36 using the following model parameters:
66 model parameters:
|
| /rk3399_ARM-atf/lib/semihosting/ |
| H 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()
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/misc/ |
| H A D | mvebu-ccu.rst | 20 a struct which has 3 parameters:
|
| H A D | mvebu-amb.rst | 46 struct which has 2 parameters:
|
| H A D | mvebu-io-win.rst | 31 a struct which has 3 parameters:
|
| H A D | mvebu-iob.rst | 24 a struct which has 3 parameters:
|
| /rk3399_ARM-atf/docs/design/ |
| H 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
326 #. Extracting parameters used for authenticating an image based upon a
334 check the image integrity and extract the authentication parameters.
351 the same CoT. The number and type of parameters are method specific. These
352 parameters should be obtained from the parent image using the IPM.
389 The Public Key parameters will be represented by the DER encoding of the
405 parameters ALGORITHM.&Type({IOSet}{@algorithm}) OPTIONAL
528 #. Correctly marshall the parameters while calling the verification function
531 #. Extract authentication parameters from a parent image in order to verify a
[all …]
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | arm-sip-service.rst | 61 The parameters *PC hi* and *PC lo* defines upper and lower words, respectively,
66 switched, the parameters *Cookie hi* and *Cookie lo* are passed in CPU registers
82 - ``STATE_SW_E_PARAM``: If any of the parameters were deemed invalid for
|
| H A D | ven-el3-debugfs.rst | 7 String parameters are passed through a shared buffer using a specific union:
289 parameters with filesystem primitives.
|
| H A D | granule-protection-tables-design.rst | 64 There are three main parameters that determine how the tables are organized and
186 as arguments. These parameters are not used in case of a single spinlock for
243 If an invalid combination of parameters is supplied, the APIs will print an
|
| H A D | debugfs-design.rst | 82 shared buffer is used to pass path string parameters, or e.g. to exchange
|
| H A D | secure-partition-manager-mm.rst | 332 - Return parameters
531 - Return parameters
576 delegated to the partition. The return parameters describe the next event.
592 event to the Secure Partition. The return parameters of this interface must
662 - Return parameters
771 - Return parameters
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | cmake_framework.rst | 58 The framework provides a solution to describe the input build parameters, flags,
64 The related parameters shall be packed into a group (or "setting group"). The
122 parameters. It is worth noting the difference between *CONFIG* and *DEFINE*
128 the parameters declared in the setting group. Then we set the target type to
129 executable, and add some source files. Since the target has the parameters from
|
| H A D | drtm_poc.rst | 28 and preparing input parameters needed by DRTM. Finally, it invokes the
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 73 calling convention, where all parameters are 32-bit, or the SMC64 calling
74 convention, where the parameters are 64-bit. The framework identifies and
220 #. Truncating parameters for calls made using the SMC32 calling convention.
228 For such calls, the upper bits of the parameters x1-x4 and the saved
229 parameters X5-X7 are UNDEFINED and must be explicitly ignored by the
232 to handle individual SMC Functions use appropriate 32-bit parameters.
235 immediate parameters x1-x4 and/or the additional saved parameters X5-X7.
|
| /rk3399_ARM-atf/docs/plat/arm/fvp-ve/ |
| H A D | index.rst | 72 The following model parameters should be used to boot Linux using the build of
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rdaspen.rst | 41 * Setting up the required system parameters.
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-4.rst | 47 overflows when the sum of its two parameters fall into the ``[2^32, 2^64 - 1]``
|