<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/crypto/Kconfig, branch v3.15</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.15</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.15'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2014-02-26T21:56:57Z</updated>
<entry>
<title>crypto: tegra - remove driver</title>
<updated>2014-02-26T21:56:57Z</updated>
<author>
<name>Stephen Warren</name>
<email>swarren@nvidia.com</email>
</author>
<published>2014-02-18T21:42:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=645af2e43705d8c80c9606d5c5e83eda9a1a1a2e'/>
<id>urn:sha1:645af2e43705d8c80c9606d5c5e83eda9a1a1a2e</id>
<content type='text'>
This driver has never been hooked up in any board file, and cannot be
instantiated via device tree. I've been told that, at least on Tegra20,
the HW is slower at crypto than the main CPU. I have no test-case for
it. Hence, remove it.

Cc: Varun Wadekar &lt;vwadekar@nvidia.com&gt;
Signed-off-by: Stephen Warren &lt;swarren@nvidia.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: omap-des - Add config and build options</title>
<updated>2014-02-26T21:56:57Z</updated>
<author>
<name>Joel Fernandes</name>
<email>joelf@ti.com</email>
</author>
<published>2014-02-14T16:49:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=701d0f1940925d40f6b8a40f6c278d14be71402b'/>
<id>urn:sha1:701d0f1940925d40f6b8a40f6c278d14be71402b</id>
<content type='text'>
Add config and build options for the omap-des driver.

Signed-off-by: Joel Fernandes &lt;joelf@ti.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: mxs - Add Freescale MXS DCP driver</title>
<updated>2014-01-05T12:49:54Z</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2013-12-10T19:26:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=15b59e7c3733f90ff1f7dd66ad77ae1c90bcdff5'/>
<id>urn:sha1:15b59e7c3733f90ff1f7dd66ad77ae1c90bcdff5</id>
<content type='text'>
Add support for the MXS DCP block. The driver currently supports
SHA-1/SHA-256 hashing and AES-128 CBC/ECB modes. The non-standard
CRC32 is not yet supported.

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Cc: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Cc: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Cc: devicetree@vger.kernel.org
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: mxs - Remove the old DCP driver</title>
<updated>2014-01-05T12:49:52Z</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2013-12-10T19:26:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c493c04403769d833864ad5be2ff64dee7567ca7'/>
<id>urn:sha1:c493c04403769d833864ad5be2ff64dee7567ca7</id>
<content type='text'>
Remove the old DCP driver as it had multiple severe issues. The driver
will be replaced by a more robust implementation. Here is a short list
of problems with this driver:

1) It only supports AES_CBC
2) The driver was apparently never ran behind anyone working with MXS. ie.:
   -&gt; Restarting the DCP block is not done via mxs_reset_block()
   -&gt; The DT name is not "fsl,dcp" or "fsl,mxs-dcp" as other MXS drivers
3) Introduces new ad-hoc IOCTLs
4) The IRQ handler can't use usual completion() in the driver because that'd
   trigger "scheduling while atomic" oops, yes?

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Cc: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Cc: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: ccp - CCP Kconfig fixes</title>
<updated>2013-12-20T12:06:20Z</updated>
<author>
<name>Tom Lendacky</name>
<email>thomas.lendacky@amd.com</email>
</author>
<published>2013-12-10T16:38:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d5aa80952aba9071b50a74c8daf7feb1caa2fd8c'/>
<id>urn:sha1:d5aa80952aba9071b50a74c8daf7feb1caa2fd8c</id>
<content type='text'>
Update the Kconfig to include PCI on the 'depends on'
and add 'select HW_RANDOM' to insure the necessary PCI
and HW_RANDOM functions are available/included in the
build.

Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crytpo: ccp - CCP device driver build files</title>
<updated>2013-12-05T13:28:40Z</updated>
<author>
<name>Tom Lendacky</name>
<email>thomas.lendacky@amd.com</email>
</author>
<published>2013-11-12T17:46:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f114766088f352a47f57307ff927b815e0239644'/>
<id>urn:sha1:f114766088f352a47f57307ff927b815e0239644</id>
<content type='text'>
These files provide the ability to configure and build the
AMD CCP device driver and crypto API support.

Signed-off-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: omap-aes - Kconfig: Add build support for AM437x</title>
<updated>2013-08-21T11:28:06Z</updated>
<author>
<name>Joel Fernandes</name>
<email>joelf@ti.com</email>
</author>
<published>2013-08-18T02:42:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1bbf643705c3f85f3fa2325807afae260f755f9a'/>
<id>urn:sha1:1bbf643705c3f85f3fa2325807afae260f755f9a</id>
<content type='text'>
For AM437x SoC, ARCH_OMAP2 and ARCH_OMAP3 is not enabled in the defconfig. We
follow same thing as SHA driver, and add depends on ARCH_OMAP2PLUS so that the
config is selectable for AES driver on AM437x SoC builds.

Signed-off-by: Joel Fernandes &lt;joelf@ti.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: omap-sham - Add SHA384 and SHA512 Support</title>
<updated>2013-08-01T00:54:00Z</updated>
<author>
<name>Lokesh Vutla</name>
<email>lokeshvutla@ti.com</email>
</author>
<published>2013-07-26T06:59:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=eaef7e3f3f82923ea175ce4859908bb0d70072f3'/>
<id>urn:sha1:eaef7e3f3f82923ea175ce4859908bb0d70072f3</id>
<content type='text'>
Adding support for SHA348 and SHA512 in addition to MD5, SHA1, SHA224
SHA256 that the omap sha module supports.

In order to add the support
- Removed hard coded register offsets and passing offsets from pdata
- Updating Flag offsets so that they can be used for SHA256 and SHA512
- Adding the algo info.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: dcp - Added support for Freescale's DCP co-processor</title>
<updated>2013-05-28T07:43:03Z</updated>
<author>
<name>Tobias Rauter</name>
<email>tobiasrauter@gmail.com</email>
</author>
<published>2013-05-19T19:59:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=519d8b1a9d81be7e4ffad8aa6b0e3ea03984bb86'/>
<id>urn:sha1:519d8b1a9d81be7e4ffad8aa6b0e3ea03984bb86</id>
<content type='text'>
This patch enables the DCP crypto functionality on imx28.
Currently, only aes-128-cbc is supported.
Moreover, the dcpboot misc-device, which is used by Freescale's
SDK tools and uses a non-software-readable OTP-key, is added.

Changes of v2:
- ring buffer for hardware-descriptors
- use of ablkcipher walk
- OTP key encryption/decryption via misc-device
  (compatible to Freescale-SDK)
- overall cleanup

The DCP is also capable of sha1/sha256 but I won't be able to add
that anytime soon.
Tested with built-in runtime-self-test, tcrypt and openssl via
cryptodev 1.6 on imx28-evk and a custom built imx28-board.

Signed-off-by: Tobias Rauter &lt;tobias.rauter@gmail.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: sahara - remove dependency on EXPERIMENTAL</title>
<updated>2013-05-24T09:55:30Z</updated>
<author>
<name>Paul Bolle</name>
<email>pebolle@tiscali.nl</email>
</author>
<published>2013-05-12T11:57:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=74d24d838be0ee64c1085558238e5c51e1659817'/>
<id>urn:sha1:74d24d838be0ee64c1085558238e5c51e1659817</id>
<content type='text'>
The Kconfig symbol EXPERIMENTAL was removed in v3.9. So this dependency
makes it impossible to set CRYPTO_DEV_SAHARA. It's unlikely that this is
what is intended, so let's remove this dependency.

Signed-off-by: Paul Bolle &lt;pebolle@tiscali.nl&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
</feed>
