linux-toradex.git/Documentation/devicetree/bindings/crypto, branch v3.4.75

crypto: picoxcell - support for device tree matching

2011-08-10T11:00:26+00:00

Allow the crypto engines to be matched from device tree bindings.

Cc: devicetree-discuss@lists.ozlabs.org
Cc: Herbert Xu 
Signed-off-by: Jamie Iles 
Signed-off-by: Herbert Xu

dt: bindings: move SEC node under new crypto/

2011-07-07T19:51:19+00:00

Since technically it's not powerpc arch-specific.  Also rename it sec2
to differentiate it from its incompatible successor, the SEC 4.

Signed-off-by: Kim Phillips 
Signed-off-by: Grant Likely

crypto: caam - de-CHIP-ify device tree compatibles

2011-03-27T02:45:18+00:00

- all the integration parameters have been captured by the binding.
- the block name really uniquely identifies this hardware.

Some advocate putting SoC names everywhere in case software needs
to work around some chip-specific bug, but more precise SoC
information already exists in SVR, and board information already
exists in the top-level device tree node.

Note that sometimes the SoC name is a worse identifier than the
block version, as the block version can change between revisions
of the same SoC.

As a matter of historical reference, neither SEC versions 2.x
nor 3.x (driven by talitos) ever needed CHIP references.

Signed-off-by: Kim Phillips 
Cc: Kumar Gala 
Cc: Scott Wood 
Acked-off-by: Grant Likely 
Signed-off-by: Herbert Xu

crypto: caam - standardize device tree naming convention to utilize '-vX.Y'

2011-03-27T02:45:17+00:00

Help clarify that the number trailing in compatible nomenclature
is the version number of the device, i.e., change:

"fsl,p4080-sec4.0", "fsl,sec4.0";

to:

"fsl,p4080-sec-v4.0", "fsl,sec-v4.0";

Signed-off-by: Kim Phillips 
Cc: Kumar Gala 
Cc: Steve Cornelius 
Signed-off-by: Herbert Xu

crypto: caam - Add support for the Freescale SEC4/CAAM

2011-03-27T02:45:16+00:00

The SEC4 supercedes the SEC2.x/3.x as Freescale's
Integrated Security Engine.  Its programming model is
incompatible with all prior versions of the SEC (talitos).

The SEC4 is also known as the Cryptographic Accelerator
and Assurance Module (CAAM); this driver is named caam.

This initial submission does not include support for Data Path
mode operation - AEAD descriptors are submitted via the job
ring interface, while the Queue Interface (QI) is enabled
for use by others.  Only AEAD algorithms are implemented
at this time, for use with IPsec.

Many thanks to the Freescale STC team for their contributions
to this driver.

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