[PATCH v7 0/3] crypto: ux500 crypto and hash driver

Changed config to depend on correct ARCH, also removed an unnecessary if statement check in the hash driver. This adds a driver for the ST-Ericsson ux500 crypto hardware module. It supports AES, DES and 3DES, the driver implements support for AES-ECB,CBC and CTR. Patches are also available at:

[PATCH v7 3/3] mach-ux500: Crypto: core support for CRYP/HASH module.

This adds the required platform data and calls to enable the CRYP/HASH driver. Acked-by: Linus Walleij linus.wall...@linaro.org Signed-off-by: Andreas Westin andreas.wes...@stericsson.com --- arch/arm/mach-ux500/board-mop500.c | 48

[PATCH v7 0/3] crypto: ux500 crypto and hash driver

Resending, something seems to have gone wrong the first time. Changed config to depend on correct ARCH, also removed an unnecessary if statement check in the hash driver. This adds a driver for the ST-Ericsson ux500 crypto hardware module. It supports AES, DES and 3DES, the driver implements

[PATCH v7 3/3] mach-ux500: Crypto: core support for CRYP/HASH module.

This adds the required platform data and calls to enable the CRYP/HASH driver. Acked-by: Linus Walleij linus.wall...@linaro.org Signed-off-by: Andreas Westin andreas.wes...@stericsson.com --- arch/arm/mach-ux500/board-mop500.c | 48

Re: [PATCH v3 03/17] powerpc: Add PFO support to the VIO bus

Hrm... I don't like that much: + if (op-timeout) + deadline = jiffies + msecs_to_jiffies(op-timeout); + + while (true) { + hret = plpar_hcall_norets(H_COP, op-flags, + vdev-resource_id, + op-in,

Re: [PATCH v3 03/17] powerpc: Add PFO support to the VIO bus

Else, what about ceding the processor ? Or at the very least reducing the thread priority for a bit ? Shouldn't we also enforce to always have a timeout ? IE. Something like 30s or so if nothing specified to avoid having the kernel just hard lock... In general I don't like that sort of