summaryrefslogtreecommitdiff
path: root/payloads/libpayload/vboot/Kconfig
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2024-01-05 10:40:43 -0800
committerJulius Werner <jwerner@chromium.org>2024-02-24 02:02:34 +0000
commit366ceeef0f07d3962ee6e6a0f3151a7f438c97ed (patch)
tree759b0461f6ecdcb046d14f1bdce340ecf1e85008 /payloads/libpayload/vboot/Kconfig
parentc57b902f9ba65cdaaceec262e7abf5b240a51d26 (diff)
vboot: Enable new arm64 SIMD crypto acceleration
This patch passes the correct flag to vboot to enable SIMD crypto acceleration on arm64 devices. This uses a core part of the ISA and should thus be supported on all arm64 SoCs -- so we normally always want it enabled, but there should still be a Kconfig in case a SoC wants to use the hwcrypto interface for its own (off-CPU) crypto acceleration engine instead. (You could also disable it to save a small amount of code size at the cost of speed, if necessary.) Change-Id: I3820bd6b7505202b7edb6768385ce5deb18777a4 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/80710 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Yu-Ping Wu <yupingso@google.com>
Diffstat (limited to 'payloads/libpayload/vboot/Kconfig')
-rw-r--r--payloads/libpayload/vboot/Kconfig12
1 files changed, 12 insertions, 0 deletions
diff --git a/payloads/libpayload/vboot/Kconfig b/payloads/libpayload/vboot/Kconfig
index 23d61f4e5e..6d71a7ca50 100644
--- a/payloads/libpayload/vboot/Kconfig
+++ b/payloads/libpayload/vboot/Kconfig
@@ -49,4 +49,16 @@ config VBOOT_SHA_ARMV8_CE
help
This option enables SHA256 implementation using ARMv8 Crypto Extension.
+config VBOOT_ARM64_RSA_ACCELERATION
+ bool "Use arm64 SIMD instructions to accelerate RSA signature verification"
+ default y
+ depends on ARCH_ARM64
+ help
+ Use arm64 SIMD instructions (NEON) to parallelize two multiplications
+ in the modulus exponentiation algorithm, which speeds up RSA signature
+ verification in vboot. This is supported on all arm64 CPUs so you'd
+ generally always want this enabled, unless your SoC is overriding
+ vboot's hwcrypto API with its own crypto accelerator IP instead (or
+ you're trying really hard to save on code size).
+
endif