On 2012-5-26 0:08, Phil Sutter wrote:
Hi, The following patch series adds support for the TDMA engine built into Marvell's Kirkwood-based SoCs, and enhances mv_cesa.c in order to use it for speeding up crypto operations. Kirkwood hardware contains a security accelerator, which can control DMA as well as crypto engines. It allows for operation with minimal software intervenience, which the following patches implement: using a chain of DMA descriptors, data input, configuration, engine startup and data output repeat fully automatically until the whole input data has been handled. The point for this being RFC is backwards-compatibility: earlier hardware (Orion) ships a (slightly) different DMA engine (IDMA) along with the same crypto engine, so in fact mv_cesa.c is in use on these platforms, too. But since I don't possess hardware of this kind, I am not able to make this code IDMA-compatible. Also, due to the quite massive reorganisation of code flow, I don't really see how to make TDMA support optional in mv_cesa.c. Greetings, Phil -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Could the source code from the manufacturers of hardwares using kirkwood be helpful? I saw the source code of ls-wvl from buffalo contains driver for CESA. And it deals with both IDMA and TDMA. If you need, I can send you the download link.
I also have to point out that CESA of some orion revisions has hardware flaws that needs to be addressed which currently doesn't. Information about those flaws can be found in 88F5182_Functional_Errata.pdf which is available on the net.
-- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
