linux-toradex.git/drivers/crypto/talitos.h, branch v4.0-rc2

crypto: talitos - add sha224, sha384 and sha512 to existing AEAD algorithms

2012-07-11T03:08:29+00:00

With this, now all combinations of
CBC: AES, 3DES-EDE
with
HMAC: SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
are supported.

Signed-off-by: Horia Geanta 
Signed-off-by: Herbert Xu

crypto: talitos - export the talitos_submit function

2012-07-11T03:08:29+00:00

This patch exports the talitos_submit function so that on
need basis same can be used by other entities.

Signed-off-by: Sandeep Malik 
Signed-off-by: Kim Phillips 
Signed-off-by: Horia Geanta 
Signed-off-by: Herbert Xu

crypto: talitos - move talitos structures to header file

2012-07-11T03:08:29+00:00

This patch moves the talitos structure definitions from c file to its
header file so that the same can be shared on need basis.

Signed-off-by: Sandeep Malik 
Signed-off-by: Kim Phillips 
Signed-off-by: Horia Geanta 
Signed-off-by: Herbert Xu

crypto: talitos - support for channel remap and 2nd IRQ

2011-11-21T08:21:51+00:00

Some later SEC v3.x are equipped with a second IRQ line.
By correctly assigning IRQ affinity, this feature can be
used to increase performance on dual core parts, like the
MPC8572E and P2020E.

The existence of the 2nd IRQ is determined from the device
node's interrupt property.  If present, the driver remaps
two of four channels, which in turn makes those channels
trigger their interrupts on the 2nd line instead of the first.
To handle single- and dual-IRQ combinations efficiently,
talitos gets two new interrupt handlers and back-half workers.

[includes a fix to MCR_LO's address.]

Signed-off-by: Kim Phillips 
Signed-off-by: Herbert Xu

crypto: talitos - prepare driver for channel remap support

2011-11-21T08:21:50+00:00

Add a reg member to the channel struct and use it to
access channels.

Signed-off-by: Kim Phillips 
Signed-off-by: Herbert Xu

crypto: talitos - add support for sha224

2010-05-19T09:21:53+00:00

SEC h/w versions 2.1 and above support sha224 via explicit instruction.

Performing sha224 ahashes on earlier versions is still possible because
they support sha256 (sha224 is sha256 with different initial constants
and a different truncation length).  We do this by overriding hardware
context self-initialization, and perform it manually in s/w instead.

Thanks to Lee for his fixes for correct execution on actual sec2.0 h/w.

Signed-off-by: Kim Phillips 
Signed-off by: Lee Nipper 
Signed-off-by: Herbert Xu

crypto: talitos - add hash algorithms

2010-05-19T09:20:36+00:00

Add the following alorithms to talitos:
    md5,
    sha1,
    sha256,
    sha384,
    sha512.
These are all type ahash.

Signed-off-by: Lee Nipper 
Acked-By: Kim Phillips 
Signed-off-by: Herbert Xu

crypto: talitos - add support for 36 bit addressing

2009-08-13T01:51:51+00:00

Enabling extended addressing in the h/w requires we always assign the
extended address component (eptr) of the talitos h/w pointer.  This is
for e500 based platforms with large memories.

Signed-off-by: Kim Phillips 
Signed-off-by: Herbert Xu

crypto: remove uses of __constant_{endian} helpers

2008-12-25T00:02:03+00:00

Base versions handle constant folding just fine.

Signed-off-by: Harvey Harrison 
Signed-off-by: Herbert Xu

crypto: talitos - Perform auth check in h/w if on sec 2.1 and above

2008-12-25T00:01:12+00:00

SEC version 2.1 and above adds the capability to do the IPSec ICV
memcmp in h/w. Results of the cmp are written back in the descriptor
header, along with the done status.  A new callback is added that
checks these ICCR bits instead of performing the memcmp on the core,
and is enabled by h/w capability.

Signed-off-by: Kim Phillips 

After testing on different parts, another condition was added
before using h/w auth check because different
SEC revisions require different handling.

The SEC 3.0 allows a more flexible link table where
the auth data can span separate link table entries.
The SEC 2.4/2.1 does not support this case.
So a test was added in the decrypt routine
for a fragmented case; the h/w auth check is disallowed for
revisions not having the extent in the link table;
in this case the hw auth check is done by software.

A portion of a previous change for SEC 3.0 link table handling
was removed since it became dead code with the hw auth check supported.

This seems to be the best compromise for using hw auth check
on supporting SEC revisions; it keeps the link table logic
simpler for the fragmented cases.

Signed-off-by: Lee Nipper 
Signed-off-by: Herbert Xu