path: root/drivers/crypto/marvell/cesa.c
diff options
authorRomain Perier <romain.perier@free-electrons.com>2016-10-05 09:56:32 +0200
committerHerbert Xu <herbert@gondor.apana.org.au>2016-10-21 11:03:40 +0800
commit0c99620f0ac13a51f2f78cf62e6b551a09f8b1f1 (patch)
treeb007a7b203954934beff9ec9c597a9135062fc77 /drivers/crypto/marvell/cesa.c
parent1f696097ad000b02e25a33442046eae339b8b3c3 (diff)
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>
Diffstat (limited to 'drivers/crypto/marvell/cesa.c')
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/crypto/marvell/cesa.c b/drivers/crypto/marvell/cesa.c
index 37dadb2a4feb..6e7a5c77a00a 100644
--- a/drivers/crypto/marvell/cesa.c
+++ b/drivers/crypto/marvell/cesa.c
@@ -375,10 +375,6 @@ static int mv_cesa_dev_dma_init(struct mv_cesa_dev *cesa)
if (!dma->padding_pool)
return -ENOMEM;
- dma->iv_pool = dmam_pool_create("cesa_iv", dev, 16, 1, 0);
- if (!dma->iv_pool)
- return -ENOMEM;
cesa->dma = dma;
return 0;