Lines Matching refs:blk_crypto_profile

94 We also introduce ``struct blk_crypto_profile`` to contain all generic inline
96 blk_crypto_profile serves as the way that drivers for inline encryption hardware
99 wants to support inline encryption will construct a blk_crypto_profile, then
102 The blk_crypto_profile also manages the hardware's keyslots, when applicable.
107 Specifically, for each keyslot, the block layer (via the blk_crypto_profile)
166 blk-crypto-fallback also defines its own blk_crypto_profile and has its own
238 blk_crypto_profile in the request_queue of its device.  To do this, it first
243 blk_crypto_profile, e.g. ``modes_supported`` and ``max_dun_bytes_supported``.
246 blk_crypto_profile to tell upper layers how to control the inline encryption
251 Once the driver registers a blk_crypto_profile with a request_queue, I/O
254 the blk_crypto_profile, so drivers don't need to worry about handling
256 blk_crypto_profile, then all I/O requests that have an encryption context will
261 field of the blk_crypto_profile to point to the ``struct device`` that will be
276 encryption need to create their own blk_crypto_profile for their request_queue,
306 (by setting the blk_crypto_profile in the request_queue of the device to NULL).
479   ``struct blk_crypto_profile``.  This allows device drivers to declare that