summaryrefslogtreecommitdiff
path: root/drivers/crypto/caam/Kconfig
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-05-13 17:57:01 +0300
committerJarkko Sakkinen <jarkko@kernel.org>2022-05-23 18:47:50 +0300
commit7a0e7d5265f58eab5983f6560817d4fe9943743b (patch)
treeffea767113f5ac62367d676fc752fd0ecc7f5d5f /drivers/crypto/caam/Kconfig
parentfcd7c26901c83681532c6daac599e53d4df11738 (diff)
downloadlinux-7a0e7d5265f58eab5983f6560817d4fe9943743b.tar.xz
crypto: caam - determine whether CAAM supports blob encap/decap
Depending on SoC variant, a CAAM may be available, but with some futures fused out. The LS1028A (non-E) SoC is one such SoC and while it indicates BLOB support, BLOB operations will ultimately fail, because there is no AES support. Add a new blob_present member to reflect whether both BLOB support and the AES support it depends on is available. These will be used in a follow-up commit to allow blob driver initialization to error out on SoCs without the necessary hardware support instead of failing at runtime with a cryptic caam_jr 8020000.jr: 20000b0f: CCB: desc idx 11: : Invalid CHA selected. Co-developed-by: Michael Walle <michael@walle.cc> Signed-off-by: Michael Walle <michael@walle.cc> Tested-by: Michael Walle <michael@walle.cc> # on ls1028a (non-E and E) Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Reviewed-by: Pankaj Gupta <pankaj.gupta@nxp.com> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Diffstat (limited to 'drivers/crypto/caam/Kconfig')
0 files changed, 0 insertions, 0 deletions