crypto: omap-aes - fix context handling for multiple cores
authorTero Kristo <t-kristo@ti.com>
Wed, 24 May 2017 07:35:23 +0000 (10:35 +0300)
committerHerbert Xu <herbert@gondor.apana.org.au>
Sat, 10 Jun 2017 04:04:13 +0000 (12:04 +0800)
commit619ce700583f0f193bfb1487ca393b8ad2141a9a
treee6049068815cb1fa4aa6421cc8a811b8ea493481
parentf09b348c1ac56b61fceb12808b4003109188f1d2
crypto: omap-aes - fix context handling for multiple cores

AES can have multiple HW accelerator cores in the system, in which case
each core has its own crypto engine in use. Currently, the used hardware
device is stored under the omap_aes_ctx struct, which is global for
the algorithm itself, causing conflicts when used with multiple cores.
Fix this by moving the used HW device under reqctx, which is stored
per-request basis.

Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/crypto/omap-aes.c