Am335X Crypto Engine: OCF vs Linux user space Linux Async crypto API

Bin Zhou35352

Hi,

I saw SDK 05.05.00.00 uses OCF on top of crypto Engine. Kernel 3.2 already supports user space Linux Async crypto APIs via socket, why SDK does not use those native APIs but instead keeps using OCF? Is there any specific reason? Do you have any example using Linux user space Linux Async crypto API to access the driver?

Thanks,

Bin

over 13 years ago

0 gkturner over 13 years ago

TI__Intellectual 1250 points

Bin,

Using OCF has been the easiest way to connect the crypto driver to higher level apps like OpenSSL. There is one way to directly access the driver from user space using the tcrypt module that is part of Crypto API. This is documented in the WIki below for DM816, but it will also work in SDK 5.05.00.00.

http://processors.wiki.ti.com/index.php/Installing_AM389x_C6A816x_DM816x_Crypto_Support#The_tcrypt_quick_and_dirty_testing_tool

Regards,

Greg Turner

Processors

Processors forum

Am335X Crypto Engine: OCF vs Linux user space Linux Async crypto API