Hi Heinrich, On Fri, 14 May 2021 at 03:17, Heinrich Schuchardt <[email protected]> wrote: > > Commit a479f103dc1c ("hash: Allow for SHA512 hardware implementations") > defined function definitions for hardware accelerated SHA384 and SHA512. > If CONFIG_SHA_HW_ACCEL=y, these functions are used. > > We already have boards using CONFIG_SHA_HW_ACCEL=y but none implements the > new functions hw_sha384() and hw_sha512(). > > For implementing the EFI TCG2 protocol we need SHA384 and SHA512. The > missing hardware acceleration functions lead to build errors on boards like > peach-pi_defconfig. > > Introduce a new Kconfig symbol CONFIG_SHA512_HW_ACCEL to control if the > functions hw_sha384() and hw_sha512() shall be used to implement the SHA384 > and SHA512 algorithms. > > Fixes: a479f103dc1c ("hash: Allow for SHA512 hardware implementations") > Signed-off-by: Heinrich Schuchardt <[email protected]> > --- > This patch replaces > hash: revert Allow for SHA512 hardware implementations > https://lists.denx.de/pipermail/u-boot/2021-May/449648.html > https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/ > --- > common/hash.c | 8 ++++---- > lib/Kconfig | 21 ++++++++++++++++----- > 2 files changed, 20 insertions(+), 9 deletions(-)
This is good as a stopgap, thanks. Reviewed-by: Simon Glass <[email protected]>
