<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/crypto/tegra-aes.h, branch v3.17</title>
<subtitle>Linux Kernel (branches are rebased on master from time to time)</subtitle>
<id>https://sre.ring0.de/linux/atom?h=v3.17</id>
<link rel='self' href='https://sre.ring0.de/linux/atom?h=v3.17'/>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/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://sre.ring0.de/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: driver for Tegra AES hardware</title>
<updated>2012-01-13T05:38:37Z</updated>
<author>
<name>Varun Wadekar</name>
<email>vwadekar@nvidia.com</email>
</author>
<published>2012-01-13T05:38:37Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=f1df57d02a0f83e764b4dc9187f58665d70f190e'/>
<id>urn:sha1:f1df57d02a0f83e764b4dc9187f58665d70f190e</id>
<content type='text'>
driver supports ecb/cbc/ofb/ansi_x9.31rng modes,
128, 192 and 256-bit key sizes

Signed-off-by: Varun Wadekar &lt;vwadekar@nvidia.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
</feed>
