Lines Matching refs:caller

30 a caller or invoked together with a template to form multi-block ciphers
63 When using the synchronous API operation, the caller invokes a cipher
65 That means, the caller waits until the cipher operation completes.
73 signal its completion. Before invoking a cipher operation, the caller
75 signal the completion of the cipher operation. Furthermore, the caller
78 perform any special serialization operation to protect the caller's data
84 A cipher is referenced by the caller with a string. That string has the
107 crypto API. When a caller uses the string to refer to a cipher during
112 Now, a caller may have the need to refer to a specific cipher
116 common names. When using that unique name, a caller is therefore always
178 When allocating a cipher handle, the caller only specifies the cipher
192 The type flag specifies the type of the cipher algorithm. The caller
193 usually provides a 0 when the caller wants the default handling.
194 Otherwise, the caller may provide the following selections which match
225 asynchronous ciphers. Usually, a caller provides a 0 for the mask flag.
227 When the caller provides a mask and type specification, the caller
230 caller uses a cipher name that exists during its initialization call,
254 the caller may not use the AEAD cipher with a separate IV generator. In
255 this case, the caller must generate the IV.
274 caller or by other blocks using the API functions defined by the kernel
281 which component. The arrows point to the invoked block where the caller
400 The following call sequence is applicable when a caller triggers an HMAC
403 1. The AHASH API functions are invoked by the caller. The HMAC