Lines Matching refs:function

37 … involve any platform-specific consideration. Driver calls are simple C function calls. Interactio…
94 …#driver-entry-points) or driver entry point family. An entry point is a function defined by the dr…
98 …function in the driver that implements the corresponding function. If a function is not listed her…
121 …function name, the driver is considered available for this cryptographic mechanism. If a driver in…
129 …e that the core supports. If the prefix of this driver is `"acme"`, the function that performs the…
137 …ation with either curve). If the prefix of this driver is `"acme"`, the function that performs the…
181 …function in the PSA Cryptography API. For example, if a call to `psa_sign_hash()` is dispatched to…
183 …nd for PSA Cryptography in particular: `PSA_SUCCESS` indicates that the function succeeded, and `P…
210 …is provided to report the actual length of the data written in the buffer if the function succeeds.
351 …ling one of the type-specific functions below. To determine the correct function, the driver can c…
369 The function `psa_crypto_driver_key_derivation_get_input_type()` determines whether a given step is…
402 … bytes. The value of `buffer_size` must be at least *N*, otherwise this function fails with the st…
410 …function or was omitted. Call `psa_crypto_driver_key_derivation_get_input_type()` to find out the …
411 …fatal error and the driver can, for example, subsequently call the same function again with a larg…
514 * `"names"` (optional, object). A mapping from entry point names to C function and type names, as u…
517 …prefix `"acme"` that implements cooked key derivation must provide the following type and function:
671 …fatal error and the driver can, for example, subsequently call the same function again with a larg…
683 The setup driver function should preserve the inputs using get-data functions.
875 …ties' `"names"` property to arrange for multiple driver entry points to map to the same C function.
890 …the core to obtain the public key of a key pair. The core may call this function at any time to ob…
928 * `"init_random"` (entry point, optional): if this function is present, [the core calls it once](#r…
929 * `"add_entropy"` (entry point, optional): the core calls this function to [inject entropy](#entrop…
930 * `"get_random"` (entry point, mandatory): the core calls this function whenever it needs to [obtai…
964 The core calls this function to supply entropy to the driver. The driver must mix this entropy into…
966 …function at any time. For example, to enforce prediction resistance, the core can call `"add_entro…
979 …function family $(F_k)$ with an $E$-bit output where $E = 8 \cdot \mathtt{entropy_size}$ and $\mat…
1042 …el-element) specifies how to calculate the size of the key context as a function of the key type a…
1049 …function that returns the number of bytes that the driver needs in a key context for a key. This m…
1060 … function named in the `"size_function"` property, `key_type` is the key type and `key_bits` is th…
1129 * `"allocate_key"`: this function obtains an internal identifier for the key. This may be, for exam…
1130 * `"destroy_key"`: this function invalidates the internal identifier and destroys the associated ke…
1144 …function typically allocates an internal identifier for the key without modifying the state of the…
1231 …er parts of the state are taken into account. The driver must call this function after updating th…
1251 …function returns `PSA_SUCCESS` or `PSA_ERROR_BUFFER_TOO_SMALL`, it must fill `attributes` with the…
1343 …is no obligation for them to declare functions. The core knows what the function names and argumen…
1345 It should be ok for driver functions to be function-like macros or function pointers.
1361 ### Driver function interfaces
1363 #### Driver function parameter conventions
1375 …fter the entry point return. This is generally necessary because an API function does not own memo…
1396 …ulated from that. Both transparent drivers and opaque drivers provide a function to calculate the …