> Subject: RE: [EXT] Re: [PATCH v2 0/4] Add Support for Marvell OcteonTX > Cryptographic > > > On Fri, 20 Mar 2020 at 06:47, Srujana Challa <schalla@xxxxxxxxxxx> wrote: > > > > > > > On Fri, Mar 13, 2020 at 05:17:04PM +0530, Srujana Challa wrote: > > > > > The following series adds support for Marvell Cryptographic Accelerarion > > > > > Unit (CPT) on OcteonTX CN83XX SoC. > > > > > > > > > > Changes since v1: > > > > > * Replaced CRYPTO_BLKCIPHER with CRYPTO_SKCIPHER in Kconfig. > > > > > > > > > > Srujana Challa (4): > > > > > drivers: crypto: create common Kconfig and Makefile for Marvell > > > > > drivers: crypto: add support for OCTEON TX CPT engine > > > > > drivers: crypto: add the Virtual Function driver for CPT > > > > > crypto: marvell: enable OcteonTX cpt options for build > > > > > > > > There's no mention of testing. Did you try > > > > CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y? > > > > > > > Yes, the crypto self-tests are passed. > > > > *which* selftests are passed? Please confirm that they all passed with > > that kconfig option set > Apologies. I have overlooked the config option, I thought it was > CONFIG_CRYPTO_MANAGER_DISABLE_TESTS, all crypto self-tests are passed > with this option disabled. I have started verifying with > CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y, I am getting few errors for > unsupported input lengths, will submit the patch with fixes. We confirmed that the failures are with unsupported lengths on our hardware, for some lengths we can resolve the issue by having validation checks in the driver but for some unsupported cases "testmgr.c" is excepting always success, I am still unsure how to fix/prevent these kind of failures. Can anyone please kindly help me out how to proceed on this issue. Thanks for your help.
