Searched refs:parameter (Results 1 – 25 of 31) sorted by relevance
12
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | platform-interrupt-controller-API.rst | 32 The API should return whether the interrupt ID (first parameter) is categorized
45 The API should return whether the interrupt ID (first parameter) is categorized
58 The API should return whether the interrupt ID (first parameter) is categorized
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,
117 This API should set the priority of the interrupt specified by first parameter
118 ``id`` to the value set by the second parameter ``priority``.
132 parameter ``type`` shall be one of ``INTR_TYPE_EL3``, ``INTR_TYPE_S_EL1``, or
167 This API should set the interrupt specified by first parameter ``id`` to the
[all …]
|
| 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).
|
| D | ras.rst | 98 otherwise. The ``probe_data`` output parameter can be used to pass any useful
111 The ``data`` constant parameter describes the various properties of the error,
|
| D | sdei.rst | 76 macro takes only one parameter: an SGI number to signal other PEs.
225 The parameter ``ev_num`` is the event number to dispatch. The API returns ``0``
|
| D | arm-sip-service.rst | 57 The function ID parameter must be ``0x82000020``. It uniquely identifies the
|
| D | xlat-tables-lib-v2-design.rst | 145 which ``_xlat_ctx`` is appended. For example, if the macro name parameter is
156 allocated. For example, if the initial lookup level is 1, this parameter would
|
| /trusted-firmware-a-3.4.0/tools/conventional-changelog-tf-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-3.4.0/plat/rockchip/rk3328/ |
| D | platform.mk | 21 -I${RK_PLAT_COMMON}/drivers/parameter/ \
60 BL31_SOURCES += ${RK_PLAT_COMMON}/drivers/parameter/ddr_parameter.c
|
| /trusted-firmware-a-3.4.0/plat/rockchip/px30/ |
| D | platform.mk | 20 -I${RK_PLAT_COMMON}/drivers/parameter/ \
63 BL31_SOURCES += ${RK_PLAT_COMMON}/drivers/parameter/ddr_parameter.c
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | auth-framework.rst | 170 #. Statically allocating memory for each parameter in each image which is
419 - ``_get_param``: extract authentication parameter function pointer.
429 The ``get_auth_param()`` function is passed a parameter descriptor containing
430 information about the parameter (``type_desc`` and ``cookie``) to identify and
431 extract the data corresponding to that parameter from an image. This data will
453 The AM defines the type of each parameter used by an authentication method. It
457 parameter should be extracted from an image.
477 The AM defines the following structure to identify an authentication parameter
488 which enables it to uniquely identify the parameter that should be extracted
541 A parameter described by ``auth_param_type_desc_t`` to verify an image could be
[all …]
|
| 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-3.4.0/tools/cert_create/src/ |
| 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-3.4.0/docs/components/spd/ |
| D | trusty-dispatcher.rst | 25 can be set to a platform specific parameter block, and ``args->arg2``
|
| /trusted-firmware-a-3.4.0/docs/plat/marvell/armada/ |
| D | build.rst | 107 This parameter is used only for ``mrvl_flash`` and ``mrvl_uart`` targets.
111 This parameter is required for ``mrvl_flash`` and ``mrvl_uart`` targets.
127 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
129 package: 1 or 2 depending on the SoC used. The parameter is valid for OcteonTX2 CN913x SoC
139 The parameter is optional, its default value is ``plat/marvell/armada/a8k/common/ble``
268 To boot from eMMC, the value should be aligned with the parameter in
310 Use this parameter to point to Crypto++ source code
318 Use this parameter to point to the directory with
327 Use this parameter to point to the directory with
|
| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | qemu-sbsa.rst | 7 is made by EDK2 build system by composing BL1 and FIP. Second parameter for Qemu
|
| D | qti-msm8916.rst | 51 but can be changed using the ``PRELOADED_BL33_BASE`` make file parameter.
|
| D | nvidia-tegra.rst | 139 parameter to be used during the 'SYSTEM SUSPEND' call. The state-id field
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/fvp/ |
| 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
534 parameter is needed to load the individual bootloader images in memory.
538 parameter.
543 - The ``-C cluster<X>.cpu<Y>.RVBAR=@<base-address-of-bl31>`` parameter, where
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | porting-guide.rst | 723 to the ROTPK in the flags parameter:
1071 The parameter indicates the type of error using standard codes from ``errno.h``.
2039 function returns the platform token length in this parameter.
2067 function returns the attestation key length in this parameter.
2314 The ``power-state`` parameter of a PSCI ``CPU_SUSPEND`` call can be used to
2316 defines a generic representation of the power-state parameter, which is an
2320 convert the power-state parameter (possibly encoding a composite power state)
2374 identified by the ``lvl`` (first argument) parameter. The ``state_info`` (second
2377 power state and the ``last_cpu_idx`` (third parameter) is the index of the last
2458 the suspend state type specified in the ``power-state`` parameter should be
[all …]
|
| 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
|
| D | psci-lib-integration-guide.rst | 257 described in `PSCI spec`_. The 'flags' (8th argument) is a bit field parameter
496 (first parameter) denotes the highest power domain level being powered down
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/ |
| D | arm-build-options.rst | 44 for the construction of composite state-ID in the power-state parameter.
49 field of power-state parameter.
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | security-hardening.rst | 138 The ``Wunused`` with ``Wno-unused-parameter``, ``Wdisabled-optimization``
|
| /trusted-firmware-a-3.4.0/docs/design_documents/ |
| D | cmake_framework.rst | 72 files. Therefore, the framework does not contain parameter validation and
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/juno/ |
| D | index.rst | 104 as a build parameter.
|
12
