summaryrefslogtreecommitdiff
path: root/drivers/crypto/s5p-sss.c
diff options
context:
space:
mode:
authorMark A. Greer <mgreer@animalcreek.com>2013-01-08 22:57:47 +0400
committerHerbert Xu <herbert@gondor.apana.org.au>2013-01-20 03:16:44 +0400
commitf9fb69e73c774a6490a13128381af9ba468d3a6e (patch)
treecc6c267aea1557f7aeb0b7ba7cc377f5262d86b2 /drivers/crypto/s5p-sss.c
parent0d35583a13ad29af06375678daa2e11772ec9267 (diff)
downloadlinux-f9fb69e73c774a6490a13128381af9ba468d3a6e.tar.xz
crypto: omap-aes - Add CTR algorithm Support
The OMAP3 and OMAP4/AM33xx versions of the AES crypto module support the CTR algorithm in addition to ECB and CBC that the OMAP2 version of the module supports. So, OMAP2 and OMAP3 share a common register set but OMAP3 supports CTR while OMAP2 doesn't. OMAP4/AM33XX uses a different register set from OMAP2/OMAP3 and also supports CTR. To add this support, use the platform_data introduced in an ealier commit to hold the list of algorithms supported by the current module. The probe routine will use that list to register the correct algorithms. Note: The code being integrated is from the TI AM33xx SDK and was written by Greg Turner <gkmturner@gmail.com> and Herman Schuurman (current email unknown) while at TI. CC: Greg Turner <gkmturner@gmail.com> CC: Dmitry Kasatkin <dmitry.kasatkin@intel.com> Signed-off-by: Mark A. Greer <mgreer@animalcreek.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/s5p-sss.c')
0 files changed, 0 insertions, 0 deletions