caam

[mk01]

this makes caam to work again.
tested openssl/cryptodev

[linux4kix]

Are these just the most recent patches from FSL from 3.10.31 or have you
made changes? You need to keep FSL patches separate from your own in order
to retain history and proper ownership.

On Wed, Sep 24, 2014 at 7:16 AM, Matus Kral notifications@github.com
wrote:

this makes caam to work again.

tested openssl/cryptodev

You can merge this Pull Request by running

git pull https://github.com/mk01/linux-linaro-stable-mx6 caam

Or view, comment on, or merge it at:

#19
Commit Summary

• crypto/caam sources from 3.10.31
• added devices needed by crypto/caam drivers

File Changes

• M arch/arm/boot/dts/imx6qdl.dtsi
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-0
  (16)
• M drivers/crypto/caam/Kconfig
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-1
  (75)
• M drivers/crypto/caam/Makefile
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-2
  (10)
• M drivers/crypto/caam/caamalg.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-3
  (514)
• M drivers/crypto/caam/caamhash.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-4
  (533)
• M drivers/crypto/caam/caamrng.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-5
  (100)
• M drivers/crypto/caam/compat.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-6
  (6)
• M drivers/crypto/caam/ctrl.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-7
  (631)
• M drivers/crypto/caam/desc.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-8
  (100)
• M drivers/crypto/caam/desc_constr.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-9
  (82)
• M drivers/crypto/caam/intern.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-10
  (43)
• M drivers/crypto/caam/jr.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-11
  (425)
• M drivers/crypto/caam/jr.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-12
  (10)
• M drivers/crypto/caam/key_gen.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-13
  (12)
• M drivers/crypto/caam/pdb.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-14
  (1)
• M drivers/crypto/caam/regs.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-15
  (299)
• M drivers/crypto/caam/secvio.c
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-16
  (2)
• M drivers/crypto/caam/sg_sw_sec4.h
  https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19/files#diff-17
  (52)

Patch Links:

• https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19.patch
• https://github.com/linux4kix/linux-linaro-stable-mx6/pull/19.diff

—
Reply to this email directly or view it on GitHub
#19.

[mk01]

@linux4kix

no patches used. I wasn't tracking history of crypto/caam folder at that time. the first commit takes sources from 3.10.30 and replaces in 3.14.

second commit (dtb adaptations) is most likely inspired by 3.10.30 and adapted. I see the commit in 3.10.30 (merge from 3.0.35) so if you are asking whether it is the same, answer is no.
but it neither mean that the same 3.0.35 applied to code before my commit would work or not... I don't know.

If you wish I can locally revert, cherry pick the same as you before and diff the result (unfortunately don't have the test environment anymore to run full scale test cases as before (with deployed cryptodev and patched openssl.