linux.git/drivers/crypto, branch v2.6.35-rc4

crypto: crypto4xx - Fix build breakage

2010-06-03T06:57:24+00:00

Fixes build error caused by the OF device_node
pointer being moved into struct device

Signed-off-by: Anatolij Gustschin 
Signed-off-by: Herbert Xu

n2_crypto: Plumb fallback ahash requests properly.

2010-05-26T00:37:15+00:00

Do this by putting the async fallback request at the end of an n2
specific ahash request context, then properly adjusting the request
private size in our ahash ->cra_init().

We also need to put the writable state bits into the n2 request
private instead of the n2 cra_ctx.

With help from Herbert Xu.

Signed-off-by: David S. Miller

n2_crypto: Fix MAU kmem_cache name.

2010-05-26T00:37:15+00:00

Both the CWQ and MAU caches unintentionally had that same name.

Signed-off-by: David S. Miller

n2_crypto: Fix build after of_device/of_platform_driver changes.

2010-05-26T00:37:08+00:00

Signed-off-by: David S. Miller

Merge remote branch 'origin' into secretlab/next-devicetree

2010-05-22T06:36:56+00:00

Merging in current state of Linus' tree to deal with merge conflicts and
build failures in vio.c after merge.

Conflicts:
	drivers/i2c/busses/i2c-cpm.c
	drivers/i2c/busses/i2c-mpc.c
	drivers/net/gianfar.c

Also fixed up one line in arch/powerpc/kernel/vio.c to use the
correct node pointer.

Signed-off-by: Grant Likely

of: Remove duplicate fields from of_platform_driver

2010-05-22T06:10:40+00:00

.name, .match_table and .owner are duplicated in both of_platform_driver
and device_driver.  This patch is a removes the extra copies from struct
of_platform_driver and converts all users to the device_driver members.

This patch is a pretty mechanical change.  The usage model doesn't change
and if any drivers have been missed, or if anything has been fixed up
incorrectly, then it will fail with a compile time error, and the fixup
will be trivial.  This patch looks big and scary because it touches so
many files, but it should be pretty safe.

Signed-off-by: Grant Likely 
Acked-by: Sean MacLennan

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 - second prepare step for adding ahash algorithms

2010-05-19T09:19:33+00:00

Used talitos_alg_template in talitos_crypto_alg
so that it will accommodate ahash algorithms.
Added some preparation code for ahash allocation and removal.
No actual algorithms yet.

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

crypto: talitos - prepare for adding ahash algorithms

2010-05-19T09:18:38+00:00

No functional changes.
Use a union in talitos_alg_template for the crypto_alg
so that we can add a member later for ahash_alg.

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