| commit | c5697462ae94693764e468b701c616bbbd6f951c | |
| author | Josh Boyer <jwboyer@linux.vnet.ibm.com> | |
| Mon, 27 Jun 2011 07:39:07 +0000 (27 15:39 +0800) | ||
| committer | Herbert Xu <herbert@gondor.apana.org.au> | |
| Wed, 29 Jun 2011 23:44:05 +0000 (30 07:44 +0800) | ||
| tree | 806796e0e6052c4fddc56e5511d75b2bfd03e9bd | treesnapshot (tar.gz zip) |
| parent | 23457bc9566be64f33afdc159aadd42712673e0b | commitdiff |
crypto: crypto4xx - Perform read/modify/write on device control register
The Security function on the AMCC SoCs has multiple engines within a
single MMIO range. The crypto driver currently enables the 3DES
functionality by doing a blind write to the device control register.
This can unintentionally disable other functions like the PKA or TRNG
when the driver is loaded.
Perform a read/modify/write to enable the 3DES function instead.
Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
The Security function on the AMCC SoCs has multiple engines within a
single MMIO range. The crypto driver currently enables the 3DES
functionality by doing a blind write to the device control register.
This can unintentionally disable other functions like the PKA or TRNG
when the driver is loaded.
Perform a read/modify/write to enable the 3DES function instead.
Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
| drivers/crypto/amcc/crypto4xx_core.c | diffblobblamehistory |