Romain Perier 0c99620f0a crypto: marvell - Use an unique pool to copy results of requests ... So far, we used a dedicated dma pool to copy the result of outer IV for cipher requests. Instead of using a dma pool per outer data, we prefer use the op dma pool that contains all part of the request from the SRAM. Then, the outer data that is likely to be used by the 'complete' operation, is copied later. In this way, any type of result can be retrieved by DMA for cipher or ahash requests. Signed-off-by: Romain Perier <romain.perier@free-electrons.com> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>		2016-10-21 11:03:40 +08:00
..
cesa.c	crypto: marvell - Use an unique pool to copy results of requests	2016-10-21 11:03:40 +08:00
cesa.h	crypto: marvell - Use an unique pool to copy results of requests	2016-10-21 11:03:40 +08:00
cipher.c	crypto: marvell - Use an unique pool to copy results of requests	2016-10-21 11:03:40 +08:00
hash.c	crypto: marvell - Don't hardcode block size in mv_cesa_ahash_cache_req	2016-08-09 18:47:31 +08:00
Makefile	crypto: marvell/cesa - add TDMA support	2015-06-19 22:18:03 +08:00
tdma.c	crypto: marvell - Use an unique pool to copy results of requests	2016-10-21 11:03:40 +08:00