u-boot.git/drivers/crypto, branch v2016.09

crypto/fsl: Update blob cmd to accept 64bit addresses

2016-08-02T16:45:39+00:00

Update blob cmd to accept 64bit source, key modifier and destination
addresses. Also correct output result print format for fsl specific
implementation of blob cmd.

Signed-off-by: Sumit Garg 
Reviewed-by: York Sun

DM: crypto/fsl: Enable rsa DM driver usage before relocation

2016-07-26T16:01:21+00:00

Enable rsa signature verification in SPL framework before relocation for
verification of main u-boot.

Reviewed-by: Aneesh Bansal 
Signed-off-by: Sumit Garg 
Reviewed-by: Simon Glass 
Reviewed-by: York Sun

powerpc/mpc85xx: SECURE BOOT- Enable chain of trust in SPL

2016-07-21T18:09:23+00:00

As part of Chain of Trust for Secure boot, the SPL U-Boot will validate
the next level U-boot image. Add a new function spl_validate_uboot to
perform the validation.

Enable hardware crypto operations in SPL using SEC block.
In case of Secure Boot, PAMU is not bypassed. For allowing SEC block
access to CPC configured as SRAM, configure PAMU.

Reviewed-by: Ruchika Gupta 
Signed-off-by: Aneesh Bansal 
Signed-off-by: Sumit Garg 
Reviewed-by: Simon Glass 
Reviewed-by: York Sun

Various, unrelated tree-wide typo fixes.

2016-07-16T13:43:12+00:00

    Fix a number of typos, including:

     * "compatble" -> "compatible"
     * "eanbeld" -> "enabled"
     * "envrionment" -> "environment"
     * "FTD" -> "FDT" (for "flattened device tree")
     * "ommitted" -> "omitted"
     * "overriden" -> "overridden"
     * "partiton" -> "partition"
     * "propogate" -> "propagate"
     * "resourse" -> "resource"
     * "rest in piece" -> "rest in peace"
     * "suport" -> "support"
     * "varible" -> "variable"

Signed-off-by: Robert P. J. Day

verified-boot: Minimal support for booting U-Boot proper from SPL

2016-06-12T17:14:58+00:00

This allows a board to configure verified boot within the SPL using
a FIT or FIT with external data. It also allows the SPL to perform
signature verification without needing relocation.

The board configuration will need to add the following feature defines:
CONFIG_SPL_CRYPTO_SUPPORT
CONFIG_SPL_HASH_SUPPORT
CONFIG_SPL_SHA256

In this example, SHA256 is the only selected hashing algorithm.

And the following booleans:
CONFIG_SPL=y
CONFIG_SPL_DM=y
CONFIG_SPL_LOAD_FIT=y
CONFIG_SPL_FIT=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_SPL_OF_LIBFDT=y
CONFIG_SPL_FIT_SIGNATURE=y

Signed-off-by: Teddy Reed 
Acked-by: Simon Glass 
Acked-by: Andreas Dannenberg 
Acked-by: Sumit Garg

crypto/fsl: add support for multiple SEC engines initialization

2016-05-18T15:51:46+00:00

For SoCs that contain multiple SEC engines, each of them needs
to be initialized (by means of initializing among others the
random number generator).

Signed-off-by: Alex Porosanu 
Reviewed-by: York Sun

armv8: LS2080A: Consolidate LS2080A and LS2085A

2016-04-06T17:26:46+00:00

LS2080A is the primary SoC, and LS2085A is a personality with AIOP
and DPAA DDR. The RDB and QDS boards support both personality. By
detecting the SVR at runtime, a single image per board can support
both SoCs. It gives users flexibility to swtich SoC without the need
to reprogram the board.

Signed-off-by: York Sun 
CC: Prabhakar Kushwaha 
Reviewed-by: Prabhakar Kushwaha

crypto/fsl: Make CAAM transactions cacheable

2016-03-29T15:46:22+00:00

This commit solves CAAM coherency issue on ls2080. When caches are
enabled and CAAM's DMA's AXI transcations are not made cacheable,
Core reads/writes data from/to caches and CAAM does from main memory.
This forces data flushes to synchronize various data structures. But
even if any data in proximity of these structures is read by core,
these structures again are fetched in caches.

To avoid this problem, either all the data that CAAM accesses can be
made cache line aligned or CAAM transcations can be made cacheable.

So, this commit makes CAAM transcations as write back with write and
read allocate.

Signed-off-by: Saksham Jain 
Reviewed-by: York Sun

crypto/fsl: Correct 64-bit write when MMU disabled

2016-03-29T15:46:22+00:00

When MMU is disabled, 64-bit write must be aligned at 64-bit
boundary. Becaue the memory location is not guaranteed to be 64-bit
aligned, the 64-bit write needs to be split into two 32-bit writes
to avoid the alignment exception.

Signed-off-by: Aneesh Bansal 
Signed-off-by: Saksham Jain 
Reviewed-by: York Sun

drivers/crypto/fsl: define structures for PDB

2016-03-21T19:42:11+00:00

Structures are defined for PDB (Protocol Data Blcks) for various
operations. These structure will be used to add PDB data while
creating the PDB descriptors.

Signed-off-by: Ruchika Gupta 
Signed-off-by: Aneesh Bansal 
CC: Ulises Cardenas 
Reviewed-by: York Sun