Lines Matching full:crypto

7  * DOC: blk-crypto profiles
11  * as the way that drivers for inline encryption hardware expose their crypto
14  * construct a crypto profile, then associate it with the disk's request_queue.
25 #define pr_fmt(fmt) "blk-crypto: " fmt
27 #include <linux/blk-crypto-profile.h>
226  * @profile: the crypto profile of the device the key will be used on
337  * __blk_crypto_cfg_supported() - Check whether the given crypto profile
338  *				  supports the given crypto configuration.
339  * @profile: the crypto profile to check
340  * @cfg: the crypto configuration to check for
358  * @profile: the crypto profile of the device
413  * @profile: The crypto profile
467  * blk_crypto_intersect_capabilities() - restrict supported crypto capabilities
469  * @parent: the crypto profile for the parent device
470  * @child: the crypto profile for the child device, or NULL
472  * This clears all crypto capabilities in @parent that aren't set in @child.  If
475  * Only use this when setting up the crypto profile for a layered device, before
499  *				   the crypto capabilities that @reference does.
503  * Return: %true if @target supports all the crypto capabilities of @reference.
530  * blk_crypto_update_capabilities() - Update the capabilities of a crypto
531  *				      profile to match those of another crypto
533  * @dst: The crypto profile whose capabilities to update.
534  * @src: The crypto profile whose capabilities this function will update @dst's
537  * Blk-crypto requires that crypto capabilities that were
540  * shrink its advertised crypto capabilities without any explicit
542  * synchronization, @src must support all the crypto capabilities that
545  * Note also that as long as the crypto capabilities are being expanded, the
547  * for blk-crypto to see stale values - they only cause blk-crypto to
548  * believe that a crypto capability isn't supported when it actually is (which
549  * might result in blk-crypto-fallback being used if available, or the bio being