crypto: omap-des - Improve wording for CRYPTO_DEV_OMAP_DES in Kconfig
Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
parent
83094e5e9e
commit
97ee7ed394
|
@ -302,15 +302,15 @@ config CRYPTO_DEV_OMAP_AES
|
||||||
want to use the OMAP module for AES algorithms.
|
want to use the OMAP module for AES algorithms.
|
||||||
|
|
||||||
config CRYPTO_DEV_OMAP_DES
|
config CRYPTO_DEV_OMAP_DES
|
||||||
tristate "Support for OMAP DES3DES hw engine"
|
tristate "Support for OMAP DES/3DES hw engine"
|
||||||
depends on ARCH_OMAP2PLUS
|
depends on ARCH_OMAP2PLUS
|
||||||
select CRYPTO_DES
|
select CRYPTO_DES
|
||||||
select CRYPTO_BLKCIPHER
|
select CRYPTO_BLKCIPHER
|
||||||
help
|
help
|
||||||
OMAP processors have DES/3DES module accelerator. Select this if you
|
OMAP processors have DES/3DES module accelerator. Select this if you
|
||||||
want to use the OMAP module for DES and 3DES algorithms. Currently
|
want to use the OMAP module for DES and 3DES algorithms. Currently
|
||||||
the ECB and CBC modes of operation supported by the driver. Also
|
the ECB and CBC modes of operation are supported by the driver. Also
|
||||||
accesses made on unaligned boundaries are also supported.
|
accesses made on unaligned boundaries are supported.
|
||||||
|
|
||||||
config CRYPTO_DEV_PICOXCELL
|
config CRYPTO_DEV_PICOXCELL
|
||||||
tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
|
tristate "Support for picoXcell IPSEC and Layer2 crypto engines"
|
||||||
|
|
Loading…
Reference in a new issue