Searched refs:function (Results 1 – 25 of 56) sorted by relevance
123
27 #define SECURE_REDUNDANT_CALL(status, status_tmp, function, ...) \ argument29 status = function(__VA_ARGS__); \30 status_tmp = function(__VA_ARGS__); \
34 lib function [patch]36 lib -- Name of the library the function belongs to37 function -- Name of the function to be placed in library at ROM38 [patch] -- Option to patch the function41 "reserved" rather than the "lib" and "function" names as shown below:60 When invoking a function of the "library at ROM", the calling sequence is as63 BL image --> wrapper function --> jump table entry --> library at ROM68 corresponding to the original function. Finally, the original function in the BL69 image(s) is replaced with the wrapper function.71 The "library at ROM" contains a necessary init function that initialises the[all …]
114 as part of the :ref:`PSA Firmware Update` procedure have failed to function.233 uint32_t function ID : 0x0246 uint32_t function ID : 0x1260 uint32_t function ID : 0x3274 uint32_t function ID : 0x4294 uint32_t function ID : 0x10343 uint32_t function ID : 0x11383 uint32_t function ID : 0x12411 uint32_t function ID : 0x13438 uint32_t function ID : 0x14[all …]
55 - A range of synchronous exceptions (e.g. SMC function identifiers).299 The current implementation reserves function IDs for Fast Calls in the Standard302 function prototypes for each function ID. The function IDs specify whether one351 This function returns the version of the Secure Partition Manager361 minor revision value of revision A, then every function in revision A must363 revision B to have a higher function count than revision A.367 If this function returns a valid version number, all the functions that are369 that a function is optional.538 In the current implementation, this parameter contains the function ID of573 This function signals to the SPM that the handling of the last event delegated[all …]
27 - A platform implementation of the ``plat_amu_topology`` function (the default).
11 - Implementing a platform-specific function or variable,77 platform-specific architecture setup function, ``blX_plat_arch_setup()``, and uses143 function.640 behaviour of the ``assert()`` function (for example, to save memory).712 This function is called with the MMU and caches disabled713 (``SCTLR_EL3.M`` = 0 and ``SCTLR_EL3.C`` = 0). The function is responsible for717 BL31 initialization. If it's a cold reset then this function must return zero.719 This function does not follow the Procedure Call Standard used by the722 function.724 This function fulfills requirement 1 and 3 listed above.[all …]
15 specific function:21 If this function is provided ``args->arg0`` must be set to the memory23 function, but defines ``TSP_SEC_MEM_SIZE``, a default implementation
40 then the platform has to provide a ``populate()`` function which essentially44 Such a ``populate()`` function is usually platform specific and is associated45 with a specific backend source. For example, a populator function which47 Hence each ``populate()`` function must be registered with a specific60 with the ``FCONF_REGISTER_POPULATOR()`` macro. This ensures that the function61 would be called inside the generic ``fconf_populate()`` function during84 anything appropriate: structure, array, function, etc..103 Once a valid device tree is available, the ``fconf_populate(config)`` function105 This function will call all the ``populate()`` callbacks which have been
130 - In BL1, this function is used to initialize the Event Log backend133 - In BL2, this function is used to initialize the Event Log buffer with144 - Measure the image using a hash function of the crypto module.152 - This function must return 0 on success, a signed integer error code154 - On the Arm FVP port, this function measures the given image and then178 - In BL1, this function is used to pass the base address of182 - In BL2, this function is used to pass the Event Log buffer information199 This function measures the given critical data structure and records its201 This function must return 0 on success, a signed integer error code214 - This function is used by the platform to measure the passed key and[all …]
118 PSCI_FEATURES is for checking whether or not a PSCI function is implemented and124 :param psci_func_id: the function ID of a PSCI function.125 :retval NOT_SUPPORTED: if the function is not implemented.126 :retval feature flags associated with the function: if the function is299 * This function calls a platform specific ``validate_power_state`` handler,305 * This function takes the ``state_info`` object containing the requested power311 * This function takes the target power level and the ``state_info`` object340 * Implement a new function handler ``psci_set_suspend_mode`` for347 * Implement a new function ``psci_validate_state_coordination`` that ensures the355 This function differs from ``psci_do_state_coordination`` in that:
7 # lib function [patch]8 # Add "patch" at the end of the line to patch a function. For example:
73 ``bl1_fwu_image_copy()`` function, which has the following function prototype:87 the platform-specific function ``bl1_plat_mem_check()`` might get defeated by95 function, which has the following function prototype:106 they might defeat the ``bl1_plat_mem_check()`` function and make the
58 Two of the vulnerabilities are in the function ``bl1_fwu_image_copy()`` in135 ARM platform version of this function contains a similar vulnerability:137 - Line 88 of ``plat/arm/common/arm_bl1_fwu.c`` in function of153 This function checks that the passed memory region is within one of the156 ``mem_size`` may result in an integer overflow and the function to incorrectly
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function107 - ``_setup`` is the initialization function with the ``rt_svc_init`` signature:113 - ``_smch`` is the SMC handler function with the ``rt_svc_handle`` signature:155 the service initialization function (``_setup`` in the declaration). This156 function must carry out any essential EL3 initialization prior to receiving a157 SMC Function call via the handler function.159 On success, the initialization function must return ``0``. Any other return value171 initialization function must itself cause the firmware boot to be halted.181 handler function (``_smch`` in the service declaration). This function must have202 #. Determining if the requested function is valid for the calling security[all …]
65 #. If the SMC function identifier corresponds to a SMC32 PSCI API, construct180 This function is to be called by the primary CPU during cold boot before190 /* The warm boot entrypoint function */217 After ``psci_setup()`` and prior to exit to the non-secure world, this function220 argument) will be used to determine the non-secure context. After this function235 management operations. This function is used to register the ``spd_pm_ops_t``237 appropriately during power management. Calling this function is optional and252 This function is the top level handler for SMCs which fall within the253 PSCI service range specified in `SMCCC`_. The function ID ``smc_fid`` (first263 PSCI API corresponding to ``smc_fid``. This function may not return back to the[all …]
24 const char *function);
14 .type \_name, %function
17 .type \_name, %function
33 .type \_name, %function
100 Note that there is no space between the name of a function and the following148 Example for a function:209 Use lowercase for function names, separating multiple words with an underscore223 Local variables and function parameters use the same format as function names:252 Place any function attributes after the function type and before the function459 This allows function declarations in other header files that depend on the478 function shall use the same names and type qualifiers".
158 | libc function | Status | Comments |228 interpreting invalid state or bad function arguments as programming errors using241 - Bad argument supplied to library function242 - Bad argument provided by platform porting function292 call ``panic()``. This will end up calling the platform-specific function295 then emit an ``ERROR`` message and call the platform-specific function388 - If an argument in a function declaration is pointing to a known type then391 - If a variable (including an argument in a function declaration) is pointing398 - For other pointer arguments in a function declaration, use ``void *``. This400 pointers to arbitrary data. This allows the calling function to pass a[all …]
12 # lib function [patch]
364 The function will return ``0`` upon a successful registration. It will return375 in the ``cpu_context`` is used by the ``el3_exit()`` function to program the411 SPD initialisation function pointed to by the ``bl32_init`` variable.443 It performs the following actions in the ``tspd_init()`` function to fulfill the458 #. The TSPD implements a handler function for Secure-EL1 interrupts. This459 function is registered with the EL3 runtime firmware using the475 implements a handler function for non-secure interrupts. This function is561 allocate a function identifier to issue a SMC64 or SMC32 to the SPD563 non-secure interrupt. If this function identifier is not known to the SPD669 #. Calling the registered handler function for the interrupt type generated.[all …]
