-
- Downloads
crypto: caam - convert top level drivers to libraries
Currently we allow top level code, i.e. that which sits between the low level (HW-specific) drivers and crypto API, to be built as several drivers: caamalg, caamhash, caam_pkc, caamrng, caamalg_qi. There is no advantage in this, more it interferes with adding support for deferred probing (there are no corresponding devices and thus no bus). Convert these drivers and call init() / exit() manually at the right time. Move algorithms initialization at JR probe / remove time: -the first probed JR registers the crypto algs -the last removed JR unregisters the crypto algs Note: caam_qi_init() is called before JR platform devices creation (of_populate_bus()), such that QI interface is initialized when the caam/qi algorithms are registered in the JR driver (by calling caam_qi_algapi_init(). While here, fix the Kconfig entries under CRYPTO_DEV_FSL_CAAM_JR to be aligned. Signed-off-by:Horia Geantă <horia.geanta@nxp.com> Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au>
Showing
- drivers/crypto/caam/Kconfig 17 additions, 29 deletionsdrivers/crypto/caam/Kconfig
- drivers/crypto/caam/Makefile 9 additions, 9 deletionsdrivers/crypto/caam/Makefile
- drivers/crypto/caam/caamalg.c 3 additions, 40 deletionsdrivers/crypto/caam/caamalg.c
- drivers/crypto/caam/caamalg_qi.c 4 additions, 41 deletionsdrivers/crypto/caam/caamalg_qi.c
- drivers/crypto/caam/caamhash.c 5 additions, 43 deletionsdrivers/crypto/caam/caamhash.c
- drivers/crypto/caam/caampkc.c 5 additions, 45 deletionsdrivers/crypto/caam/caampkc.c
- drivers/crypto/caam/caamrng.c 7 additions, 47 deletionsdrivers/crypto/caam/caamrng.c
- drivers/crypto/caam/ctrl.c 25 additions, 20 deletionsdrivers/crypto/caam/ctrl.c
- drivers/crypto/caam/intern.h 90 additions, 3 deletionsdrivers/crypto/caam/intern.h
- drivers/crypto/caam/jr.c 43 additions, 0 deletionsdrivers/crypto/caam/jr.c
Loading
Please register or sign in to comment