tests/functional/aarch64/test_aspeed: Disable kernel crypto self-tests in AST2700 boot tests
Disable the kernel crypto self-tests in the AST2700 functional tests by appending "cryptomgr.notests=1" to the U-Boot bootargs before booting the kernel. The ASPEED SDK enables crypto self-tests during kernel startup to validate the hardware crypto engine. However, the current QEMU implementation of the AST2700 HACE/crypto engine is still incomplete. As a result, the kernel crypto self-tests trigger multiple warnings during boot when running under QEMU. Typical examples observed in the kernel log include failures for several cipher modes such as DES/TDES/AES in ECB/CBC/CTR modes: alg: self-tests for ctr(des) using aspeed-ctr-des failed (rc=-22) alg: self-tests for ecb(des3_ede) using aspeed-ecb-tdes failed (rc=-22) alg: self-tests for cbc(aes) using aspeed-cbc-aes failed (rc=-22) ... To reduce noise in the functional test logs, the tests now append the following parameter to the kernel bootargs: cryptomgr.notests=1 This disables the kernel crypto self-tests when running the functional tests under QEMU. For validating the HACE implementation, we should instead rely on the dedicated QEMU unit tests located in: tests/qtest/ast2700-hace-test.c Once the QEMU implementation of the ASPEED HACE/crypto model has progressed further and supports the missing crypto modes, we can reassess whether enabling the kernel crypto self-tests again in the functional tests is appropriate. Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com> Reviewed-by: Cédric Le Goater <clg@redhat.com> Link: https://lore.kernel.org/qemu-devel/20260316081549.1279841-1-jamin_lin@aspeedtech.com Signed-off-by: Cédric Le Goater <clg@redhat.com>