[RFC] Generic crypto counters

Hi Herbert, I've noticed that the powerpc folks were able to sneak counters for their hardware crypto implementation into upstream [1]. Simple counters for the number of processed bytes per algorithm is something which I wanted to have for some time now. The reason is that its not obvious to

Re: RFC: support for MV_CESA with IDMA or TDMA

Hi, On Fri, Jun 15, 2012 at 09:40:28AM +0800, cloudy.linux wrote: I would like to have a try on those patches. But what version of kernel should I apply those patches on? Sorry for the caused confusion. I have applied those patches to linus' git, preceded by the three accepted ones of the

[PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

Hi Phil, thanks for providing these patches; it's great to finally see DMA support for CESA in the kernel. Additionally, the implementation seems to be fine regarding cache incoherencies (at least my test in [*] works). I have two patches for your patchset... - Fix for mv_init_engine error

[PATCH 1/2] mv_dma: fix mv_init_engine() error case

Fix wrongly placed free_irq in mv_init_engine() error recovery. In fact, we can remove the respective label, since request_irq() is the last thing the function does anyway. Signed-off-by: Simon Baatz gmbno...@gmail.com --- drivers/crypto/mv_dma.c |4 +--- 1 file changed, 1 insertion(+), 3

[PATCH 2/2] ARM: Orion: mv_dma: Add support for clk

mv_dma needs the crypto clock. Some orion platforms support gating of the clock. If the clock exists enable/disable it as appropriate. Signed-off-by: Simon Baatz gmbno...@gmail.com --- arch/arm/mach-kirkwood/common.c |1 + drivers/crypto/mv_dma.c | 14 ++ 2 files