user/sven/linux.git/include/linux/ccp.h, branch v4.4.2Linux Kernel
https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.4.22014-09-24T06:23:34Zcrypto: ccp - Check for CCP before registering crypto algs2014-09-24T06:23:34ZTom Lendackythomas.lendacky@amd.com2014-09-05T15:31:09Zurn:sha1:c9f21cb6388898bfe69886d001316dae7ecc9a4b
If the ccp is built as a built-in module, then ccp-crypto (whether
built as a module or a built-in module) will be able to load and
it will register its crypto algorithms. If the system does not have
a CCP this will result in -ENODEV being returned whenever a command
is attempted to be queued by the registered crypto algorithms.
Add an API, ccp_present(), that checks for the presence of a CCP
on the system. The ccp-crypto module can use this to determine if it
should register it's crypto alogorithms.
Cc: stable@vger.kernel.org
Reported-by: Scot Doyle <lkml14@scotdoyle.com>
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Tested-by: Scot Doyle <lkml14@scotdoyle.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto: ccp - Move HMAC calculation down to ccp ops file2014-02-09T01:59:23ZTom Lendackythomas.lendacky@amd.com2014-01-24T22:18:02Zurn:sha1:c11baa02c5d6ea06362fa61da070af34b7706c83
Move the support to perform an HMAC calculation into
the CCP operations file. This eliminates the need to
perform a synchronous SHA operation used to calculate
the HMAC.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto: ccp - CCP device enabled/disabled changes2014-01-15T03:33:40ZTom Lendackythomas.lendacky@amd.com2014-01-06T19:34:29Zurn:sha1:db34cf9122319d6fed59bd3ba26fa099a8ece432
The CCP cannot be hot-plugged so it will either be there
or it won't. Do not allow the driver to stay loaded if the
CCP does not successfully initialize.
Provide stub routines in the ccp.h file that return -ENODEV
if the CCP has not been configured in the build.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto: ccp - Change data length declarations to u642014-01-15T03:33:39ZTom Lendackythomas.lendacky@amd.com2014-01-06T19:34:17Zurn:sha1:81a59f000e1d4a60a03081a1fc64aee46d6f0c3e
When performing a hash operation if the amount of data buffered and a
request at or near the maximum data length is received then the length
calcuation could wrap causing an error in executing the hash operation.
Fix this by using a u64 type for the input and output data lengths in
all CCP operations.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto: ccp - CCP device driver and interface support2013-12-05T13:28:37ZTom Lendackythomas.lendacky@amd.com2013-11-12T17:46:16Zurn:sha1:63b945091a070d8d4275dc0f7699ba22cd5f9435
These routines provide the device driver support for the AMD
Cryptographic Coprocessor (CCP).
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>