crypto: marvell - Use an unique pool to copy results of requests
authorRomain Perier <romain.perier@free-electrons.com>
Wed, 5 Oct 2016 07:56:32 +0000 (09:56 +0200)
committerHerbert Xu <herbert@gondor.apana.org.au>
Fri, 21 Oct 2016 03:03:40 +0000 (11:03 +0800)
commit0c99620f0ac13a51f2f78cf62e6b551a09f8b1f1
treeb007a7b203954934beff9ec9c597a9135062fc77
parent1f696097ad000b02e25a33442046eae339b8b3c3
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>
drivers/crypto/marvell/cesa.c
drivers/crypto/marvell/cesa.h
drivers/crypto/marvell/cipher.c
drivers/crypto/marvell/tdma.c