From: "Mark A. Greer"
Convert the device data for the OMAP2 SHAM crypto IP from
explicit platform_data to hwmod.
CC: Paul Walmsley
Signed-off-by: Mark A. Greer
---
arch/arm/mach-omap2/clock2430_data.c | 1 +
arch/arm/mach-omap2/devices.c | 34 --
From: "Mark A. Greer"
Remove usage of the private OMAP DMA API.
The dmaengine API will be used instead.
CC: Russell King
CC: Dmitry Kasatkin
Signed-off-by: Mark A. Greer
---
drivers/crypto/omap-sham.c | 117 -
1 file changed, 117 deletions(-)
diff
From: "Mark A. Greer"
Convert the omap-sham crypto driver to use the
pm_runtime API instead of the clk API.
CC: Kevin Hilman
CC: Paul Walmsley
CC: Dmitry Kasatkin
Signed-off-by: Mark A. Greer
---
drivers/crypto/omap-sham.c | 28 +++-
1 file changed, 11 insertions(+),
From: "Mark A. Greer"
Add code to use the new dmaengine API alongside
the existing DMA code that uses the private
OMAP DMA API. The API to use is chosen by
defining or undefining 'OMAP_SHAM_DMA_PRIVATE'.
CC: Russell King
CC: Dmitry Kasatkin
Signed-off-by: Mark A. Greer
---
drivers/crypto/om
From: "Mark A. Greer"
Convert the device data for the OMAP3 SHAM2 (SHA1/MD5) crypto IP
from explicit platform_data to hwmod.
CC: Paul Walmsley
Signed-off-by: Mark A. Greer
---
arch/arm/mach-omap2/clock3xxx_data.c | 1 +
arch/arm/mach-omap2/devices.c | 42 ++
From: "Mark A. Greer"
Remove the error message that prints when there is no SHA IP
present to make it consistent with all the other IPs.
CC: Paul Walmsley
Signed-off-by: Mark A. Greer
---
arch/arm/mach-omap2/devices.c | 19 +++
1 file changed, 7 insertions(+), 12 deletions(-)
From: "Mark A. Greer"
The current OMAP2 SHAM support doesn't enable DMA
so add that support so it can use DMA just like OMAP3.
CC: Paul Walmsley
Signed-off-by: Mark A. Greer
---
arch/arm/mach-omap2/omap_hwmod_2xxx_interconnect_data.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c
From: "Mark A. Greer"
Changes since v2:
- Reworked pm_runtime calls to match where original clk_*
calls were so provide better PM (as per Kevin Hilman's
comments).
Changes since v1:
- Removed the check of CM_IDLEST to see if the module exists
and ins
Updates from IP release 0x320 to 0x400:
- add DMA support (previous IP revision use PDC)
- add DMA double input buffer support
- add SHA224 support
Update from IP release 0x400 to 0x410:
- add SHA384 and SHA512 support
Signed-off-by: Nicolas Royer
Acked-by: Nicolas Ferre
Acked-by: Eric Béna
Update from previous IP release (0x600):
- add DMA support (previous IP release use PDC)
Signed-off-by: Nicolas Royer
Acked-by: Nicolas Ferre
Acked-by: Eric Bénard
Tested-by: Eric Bénard
---
drivers/crypto/atmel-tdes-regs.h |2 +
drivers/crypto/atmel-tdes.c | 394 ++
Updates from previous IP release (0x120):
- add cfb64 support
- add DMA double input buffer support
Signed-off-by: Nicolas Royer
Acked-by: Nicolas Ferre
Acked-by: Eric Bénard
Tested-by: Eric Bénard
---
drivers/crypto/atmel-aes.c | 470 +---
1 files c
Only AES use DMA in AT91SAM9G45 (TDES and SHA use PDC).
However latest Atmel TDES and SHA IP releases use DMA instead of PDC.
--> Atmel TDES and SHA drivers need DMA platform data for those IP releases.
Goal of this patch is to use the same platform data structure for all Atmel
crypto periphera
Spare irq support introduced by commit "8fe82a5 ARM: at91: sparse irq support"
involves to add the NR_IRQS_LEGACY offset to irq number.
Signed-off-by: Nicolas Royer
Acked-by: Nicolas Ferre
Acked-by: Eric Bénard
Tested-by: Eric Bénard
Cc: sta...@vger.kernel.org # 3.6
---
arch/arm/mach-at91/at9
On Tue, Nov 06, 2012 at 10:42:42AM -0500, Jarod Wilson wrote:
> The value stored in last_data must be primed for FIPS 140-2 purposes. Upon
> first use, either on system startup or after an RNDCLEARPOOL ioctl, we
> need to take an initial random sample, store it internally in last_data,
> then pass
The value stored in last_data must be primed for FIPS 140-2 purposes. Upon
first use, either on system startup or after an RNDCLEARPOOL ioctl, we
need to take an initial random sample, store it internally in last_data,
then pass along the value after that to the requester, so that consistency
check
The value stored in last_data must be primed for FIPS 140-2 purposes. Upon
first use, either on system startup or after an RNDCLEARPOOL ioctl, we
need to take an initial random sample, store it internally in last_data,
then pass along the value after that to the requester, so that consistency
check
On Tue, Nov 06, 2012 at 07:05:23AM -0500, Neil Horman wrote:
> On Mon, Nov 05, 2012 at 04:00:10PM -0500, Jarod Wilson wrote:
> > The value stored in last_data must be primed for FIPS 140-2 purposes. Upon
> > first use, either on system startup or after an RNDCLEARPOOL ioctl, we
> > need to take an
On Mon, Nov 05, 2012 at 04:00:10PM -0500, Jarod Wilson wrote:
> The value stored in last_data must be primed for FIPS 140-2 purposes. Upon
> first use, either on system startup or after an RNDCLEARPOOL ioctl, we
> need to take an initial random sample, store it internally in last_data,
> then pass
18 matches
Mail list logo