| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | platform-interrupt-controller-API.rst.txt | 72 first parameter, ``id``.
86 This API should enable the interrupt ID specified by the first parameter,
101 This API should disable the interrupt ID specified by the first parameter,
118 ``id`` to the value set by the second parameter ``priority``.
168 type specified by second parameter ``type``. The ``type`` parameter can be
225 specified by first parameter ``id`` to that specified by the second parameter
228 The ``routing_mode`` parameter can be one of:
231 system. The ``mpidr`` parameter is ignored in this case.
234 value is specified by the parameter ``mpidr``.
248 This API should set the interrupt specified by first parameter ``id`` to
[all …]
|
| A D | secure-partition-manager-mm.rst.txt | 212 is passed as a parameter to the ``MM_COMMUNICATE`` SMC. The shared memory area
545 In the current implementation, this parameter contains the function ID of
566 For the SVC64 version, this parameter is a 64-bit Virtual Address (VA).
568 For the SVC32 version, this parameter is a 32-bit Virtual Address (VA).
576 This is an optional parameter. If unused its value is SBZ.
657 This parameter is a 64-bit Virtual Address (VA).
730 This parameter is a 64-bit Virtual Address (VA).
|
| /trusted-firmware-a/docs/components/ |
| A D | platform-interrupt-controller-API.rst | 72 first parameter, ``id``.
86 This API should enable the interrupt ID specified by the first parameter,
101 This API should disable the interrupt ID specified by the first parameter,
118 ``id`` to the value set by the second parameter ``priority``.
168 type specified by second parameter ``type``. The ``type`` parameter can be
225 specified by first parameter ``id`` to that specified by the second parameter
228 The ``routing_mode`` parameter can be one of:
231 system. The ``mpidr`` parameter is ignored in this case.
234 value is specified by the parameter ``mpidr``.
248 This API should set the interrupt specified by first parameter ``id`` to
[all …]
|
| A D | secure-partition-manager-mm.rst | 212 is passed as a parameter to the ``MM_COMMUNICATE`` SMC. The shared memory area
545 In the current implementation, this parameter contains the function ID of
566 For the SVC64 version, this parameter is a 64-bit Virtual Address (VA).
568 For the SVC32 version, this parameter is a 32-bit Virtual Address (VA).
576 This is an optional parameter. If unused its value is SBZ.
657 This parameter is a 64-bit Virtual Address (VA).
730 This parameter is a 64-bit Virtual Address (VA).
|
| /trusted-firmware-a/tools/conventional-changelog-tf-a/ |
| A D | index.js | 191 module.exports = function (parameter) { argument
192 const config = parameter || {};
205 if (_.isFunction(parameter)) {
206 return parameter(null, {
|
| /trusted-firmware-a/plat/rockchip/rk3328/ |
| A D | platform.mk | 21 -I${RK_PLAT_COMMON}/drivers/parameter/ \
60 BL31_SOURCES += ${RK_PLAT_COMMON}/drivers/parameter/ddr_parameter.c
|
| /trusted-firmware-a/docs/design/ |
| A D | auth-framework.rst | 170 #. Statically allocating memory for each parameter in each image which is
419 - ``_get_param``: extract authentication parameter function pointer.
457 parameter should be extracted from an image.
488 which enables it to uniquely identify the parameter that should be extracted
549 authentication parameter.
675 authenticated. Each method consists of a type and a list of parameter
678 the image (i.e. if the parameter is stored in an x509v3 extension, the
685 from the parent image. The following parameter descriptors must be
703 Each parameter consists of a parameter descriptor and the buffer
714 be used to extract the parameter data from the corresponding image.
[all …]
|
| A D | interrupt-framework-design.rst | 246 ``flags`` parameter.
318 The ``id`` is parameter is reserved and could be used in the future for passing
322 The ``flags`` parameter contains miscellaneous information as follows.
333 The ``handle`` parameter points to the ``cpu_context`` structure of the current CPU
334 for the security state specified in the ``flags`` parameter.
360 The ``type`` parameter can be one of the three interrupt types listed above i.e.
361 ``INTR_TYPE_S_EL1``, ``INTR_TYPE_NS`` & ``INTR_TYPE_EL3``. The ``flags`` parameter
670 The ``id`` parameter is set to ``INTR_ID_UNAVAILABLE`` currently. The id along
696 exception level (passed in the ``flags`` parameter of the handler) where
765 #. It uses the security state provided in the ``flags`` parameter to ensure
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | auth-framework.rst.txt | 170 #. Statically allocating memory for each parameter in each image which is
419 - ``_get_param``: extract authentication parameter function pointer.
457 parameter should be extracted from an image.
488 which enables it to uniquely identify the parameter that should be extracted
549 authentication parameter.
675 authenticated. Each method consists of a type and a list of parameter
678 the image (i.e. if the parameter is stored in an x509v3 extension, the
685 from the parent image. The following parameter descriptors must be
703 Each parameter consists of a parameter descriptor and the buffer
714 be used to extract the parameter data from the corresponding image.
[all …]
|
| /trusted-firmware-a/plat/rockchip/px30/ |
| A D | platform.mk | 20 -I${RK_PLAT_COMMON}/drivers/parameter/ \
63 BL31_SOURCES += ${RK_PLAT_COMMON}/drivers/parameter/ddr_parameter.c
|
| /trusted-firmware-a/tools/cert_create/src/ |
| A D | ext.c | 205 hash->hashAlgorithm->parameter = ASN1_TYPE_new(); in ext_new_hash()
206 ASN1_TYPE_set(hash->hashAlgorithm->parameter, V_ASN1_NULL, NULL); in ext_new_hash()
|
| /trusted-firmware-a/docs/plat/marvell/armada/ |
| A D | build.rst | 106 This parameter is used only for ``mrvl_flash`` and ``mrvl_uart`` targets.
110 This parameter is required for ``mrvl_flash`` and ``mrvl_uart`` targets.
126 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
128 package: 1 or 2 depending on the SoC used. The parameter is valid for OcteonTX2 CN913x SoC
138 The parameter is optional, its default value is ``plat/marvell/armada/a8k/common/ble``
267 To boot from eMMC, the value should be aligned with the parameter in
309 Use this parameter to point to Crypto++ source code
317 Use this parameter to point to the directory with
322 Use this parameter to point to the directory with
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/ |
| A D | build.rst.txt | 106 This parameter is used only for ``mrvl_flash`` and ``mrvl_uart`` targets.
110 This parameter is required for ``mrvl_flash`` and ``mrvl_uart`` targets.
126 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
128 package: 1 or 2 depending on the SoC used. The parameter is valid for OcteonTX2 CN913x SoC
138 The parameter is optional, its default value is ``plat/marvell/armada/a8k/common/ble``
267 To boot from eMMC, the value should be aligned with the parameter in
309 Use this parameter to point to Crypto++ source code
317 Use this parameter to point to the directory with
322 Use this parameter to point to the directory with
|
| /trusted-firmware-a/docs/components/spd/ |
| A D | trusty-dispatcher.rst | 25 can be set to a platform specific parameter block, and ``args->arg2``
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/spd/ |
| A D | trusty-dispatcher.rst.txt | 25 can be set to a platform specific parameter block, and ``args->arg2``
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | qemu-sbsa.rst.txt | 7 is made by EDK2 build system by composing BL1 and FIP. Second parameter for Qemu
|
| /trusted-firmware-a/docs/plat/ |
| A D | qemu-sbsa.rst | 7 is made by EDK2 build system by composing BL1 and FIP. Second parameter for Qemu
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/arm/fvp/ |
| A D | index.rst.txt | 8 documentation for a detailed description of the model parameter options.
79 with the ``--version`` parameter.
199 flash memory. On Base Cortex and AEM FVPs, the following model parameter
533 parameter is needed to load the individual bootloader images in memory.
537 parameter.
542 - The ``-C cluster<X>.cpu<Y>.RVBAR=@<base-address-of-bl31>`` parameter, where
|
| /trusted-firmware-a/docs/plat/arm/fvp/ |
| A D | index.rst | 8 documentation for a detailed description of the model parameter options.
79 with the ``--version`` parameter.
199 flash memory. On Base Cortex and AEM FVPs, the following model parameter
533 parameter is needed to load the individual bootloader images in memory.
537 parameter.
542 - The ``-C cluster<X>.cpu<Y>.RVBAR=@<base-address-of-bl31>`` parameter, where
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | porting-guide.rst.txt | 721 to the ROTPK in the flags parameter:
2536 parameter passed by the normal world. If the ``entry_point`` is invalid,
2601 based on the first parameter ``reset_type`` as specified in
2602 `PSCI`_. The parameter ``cookie`` can be used to pass additional
2622 state of ``MEM_PROTECT`` via the ``val`` parameter. Upon encountering
2671 The first parameter will be one of the ``INTR_TYPE_*`` values (see
2673 interrupt, the second parameter is the security state of the originating
2806 the interrupt corresponding to the id (passed as the parameter) has
2827 This API returns the type of the interrupt id passed as the parameter.
2934 The second parameter (``uint64_t syndrome``) is the respective syndrome
[all …]
|
| A D | rt-svc-writers-guide.rst.txt | 206 The ``flags`` parameter to this function indicates the caller security state
219 ``smc_fid`` parameter, for example by using:
277 The ``cookie`` parameter to the handler is reserved for future use and can be
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | porting-guide.rst | 721 to the ROTPK in the flags parameter:
2536 parameter passed by the normal world. If the ``entry_point`` is invalid,
2601 based on the first parameter ``reset_type`` as specified in
2602 `PSCI`_. The parameter ``cookie`` can be used to pass additional
2622 state of ``MEM_PROTECT`` via the ``val`` parameter. Upon encountering
2671 The first parameter will be one of the ``INTR_TYPE_*`` values (see
2673 interrupt, the second parameter is the security state of the originating
2806 the interrupt corresponding to the id (passed as the parameter) has
2827 This API returns the type of the interrupt id passed as the parameter.
2934 The second parameter (``uint64_t syndrome``) is the respective syndrome
[all …]
|
| A D | rt-svc-writers-guide.rst | 206 The ``flags`` parameter to this function indicates the caller security state
219 ``smc_fid`` parameter, for example by using:
277 The ``cookie`` parameter to the handler is reserved for future use and can be
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/arm/ |
| A D | arm-build-options.rst.txt | 44 for the construction of composite state-ID in the power-state parameter.
49 field of power-state parameter.
|
| /trusted-firmware-a/docs/plat/arm/ |
| A D | arm-build-options.rst | 44 for the construction of composite state-ID in the power-state parameter.
49 field of power-state parameter.
|