diff options
author | Corentin Labbe <clabbe@baylibre.com> | 2022-03-04 07:36:48 +0000 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2022-03-09 15:12:31 +1200 |
commit | 7a70d9a1cf112c0bdb42800d264d48f34089e3e8 (patch) | |
tree | b0310066678caae62e0f5c063a86e196323bcfa5 /drivers/crypto/Kconfig | |
parent | ee6584bf3c680e20464e20bf28066d1ce685f7d3 (diff) | |
download | linux-stable-7a70d9a1cf112c0bdb42800d264d48f34089e3e8.tar.gz linux-stable-7a70d9a1cf112c0bdb42800d264d48f34089e3e8.tar.bz2 linux-stable-7a70d9a1cf112c0bdb42800d264d48f34089e3e8.zip |
crypto: xilinx: prevent probing on non-xilinx hardware
The zynqmp-sha driver is always loaded and register its algorithm even on
platform which do not have the proper hardware.
This lead to a stacktrace due to zynqmp-sha3-384 failing its crypto
self tests.
So check if hardware is present via the firmware API call get_version.
While at it, simplify the platform_driver by using module_platform_driver()
Furthermore the driver should depend on ZYNQMP_FIRMWARE since it cannot
work without it.
Fixes: 7ecc3e34474b ("crypto: xilinx - Add Xilinx SHA3 driver")
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/Kconfig')
-rw-r--r-- | drivers/crypto/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig index bf4e55e730aa..597559ec2057 100644 --- a/drivers/crypto/Kconfig +++ b/drivers/crypto/Kconfig @@ -810,7 +810,7 @@ config CRYPTO_DEV_ZYNQMP_AES config CRYPTO_DEV_ZYNQMP_SHA3 bool "Support for Xilinx ZynqMP SHA3 hardware accelerator" - depends on ARCH_ZYNQMP + depends on ZYNQMP_FIRMWARE select CRYPTO_SHA3 help Xilinx ZynqMP has SHA3 engine used for secure hash calculation. |