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>
35 #include "blk-crypto-internal.h"
234 * @profile: the crypto profile of the device the key will be used on
339 * __blk_crypto_cfg_supported() - Check whether the given crypto profile
340 * supports the given crypto configuration.
341 * @profile: the crypto profile to check
342 * @cfg: the crypto configuration to check for
360 * device that can be either a real device or the blk-crypto-fallback "device".
411 * @profile: The crypto profile
466 * blk_crypto_intersect_capabilities() - restrict supported crypto capabilities
468 * @parent: the crypto profile for the parent device
469 * @child: the crypto profile for the child device, or NULL
471 * This clears all crypto capabilities in @parent that aren't set in @child. If
474 * Only use this when setting up the crypto profile for a layered device, before
498 * the crypto capabilities that @reference does.
502 * Return: %true if @target supports all the crypto capabilities of @reference.
529 * blk_crypto_update_capabilities() - Update the capabilities of a crypto
530 * profile to match those of another crypto
532 * @dst: The crypto profile whose capabilities to update.
533 * @src: The crypto profile whose capabilities this function will update @dst's
536 * Blk-crypto requires that crypto capabilities that were
539 * shrink its advertised crypto capabilities without any explicit
541 * synchronization, @src must support all the crypto capabilities that
544 * Note also that as long as the crypto capabilities are being expanded, the
546 * for blk-crypto to see stale values - they only cause blk-crypto to
547 * believe that a crypto capability isn't supported when it actually is (which
548 * might result in blk-crypto-fallback being used if available, or the bio being