Thread (10 messages) 10 messages, 4 authors, 2010-08-14

[RFC 9/9] crypto: Add Samsung crypto engine driver

From: Maurus Cuelenaere <hidden>
Date: 2010-08-13 11:18:00
Also in: linux-crypto, linux-samsung-soc

 Op 13-08-10 00:32, David Miller schreef:
From: Maurus Cuelenaere <redacted>
Date: Thu, 12 Aug 2010 13:47:24 +0200
quoted
The main issues still remain (DMA not working at all and FIFO not
working for some (T)DES transfers). Additionally, I couldn't get
tcrypt to test the s3c-sss driver for some reason, it always picked
the standard AES/TDES/DES driver (even though s3c-sss has a higher
priority and succeeded the self-test).
I forget the details of your driver, but were your encryption algorithms
implemented async?
Yes, all are async (also the not-yet-working hash algorithms).
tcrypt can validate async crypto algorithms, but cannot performance
test them just yet.  I can performance test async hash algorithms,
for which I added the code for a few months ago.
Hmm ok, I suppose implementing support for performance testing async crypto
algorithms isn't trivial?

-- 
Maurus Cuelenaere
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help