Lines Matching full:driver

99 Sessions are used to cache cryptographic information in a particular driver
132 the driver to establish the session.
134 hardware driver should be used (1) or not (0).
180 by the device driver processing the request.
199 essence, SID acts as an index in the session cache of the driver).
249 session migration (move a session from one driver to another, because
331 the driver used to perform the operation, whereas for decryption
381 .Sh DRIVER-SIDE API
393 function to acquire a driver identifier, specifying the
397 For each algorithm the driver supports, it must then call
399 The first argument is the driver identifier.
404 driver-provided functions that the framework may call to establish new
405 cryptographic context with the driver, free already established
409 The two arguments are the driver and algorithm identifiers, respectively.
416 all algorithms registered for a driver will be unregistered in one go
417 and the driver will be disabled (no new sessions will be allocated on
418 that driver, and any existing sessions will be migrated to other
420 The same will be done if all algorithms associated with a driver are
423 The calling convention for the three driver-supplied routines is:
432 contains the driver identifier obtained via
434 On successfully returning, it should contain a driver-specific session
442 driver identifier and the driver-specific session identifier).
504 operation must be available by the same driver.
507 The framework also needs a mechanism for determining which driver is