Lines Matching full:driver
86 submitted to sessions associated with the driver.
95 methods are defined in the method table for the device driver attached to
98 specifies the size of a driver-specific per-session structure allocated by
101 is a bitmask of properties about the driver.
117 returns an opaque driver id.
120 unregisters a driver from the cryptographic framework.
130 is invoked by the cryptographic framework on each active driver to
131 determine the best driver to use for the session.
134 If a driver does not support requests described by
137 If the driver does support requests described by
147 The driver processes requests via a co-processor.
149 The driver processes requests on the host CPU using optimized instructions
152 The driver processes requests on the host CPU.
157 Once the framework has chosen a driver for a session,
160 method to initialize driver-specific session state.
162 the framework allocates a per-session driver-specific data structure.
178 is invoked to release any driver-specific state when a session is
180 The per-session driver-specific data structure is explicitly zeroed
182 If a driver requires no additional tear-down steps, it can leave
198 driver releases pending requests via
200 Any requests submitted to sessions belonging to the driver will also
205 If a driver encounters errors while processing a request,
215 if there are additional requests queued for this driver.
216 The driver can use this as a hint to batch completion interrupts.
220 returns a pointer to the driver-specific per-session data structure
258 A driver calls
267 If a driver defers a request by returning
271 the framework will queue all requests for the driver until the driver calls
275 if a driver returns
285 indicates which types of requests the driver is able to handle again:
288 indicates that the driver is able to handle symmetric requests passed to
320 returns a driver identifier on success or -1 on error.