mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-22 20:23:57 +08:00
c9f21cb638
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> |
||
|---|---|---|
| .. | ||
| ccp-crypto-aes-cmac.c | ||
| ccp-crypto-aes-xts.c | ||
| ccp-crypto-aes.c | ||
| ccp-crypto-main.c | ||
| ccp-crypto-sha.c | ||
| ccp-crypto.h | ||
| ccp-dev.c | ||
| ccp-dev.h | ||
| ccp-ops.c | ||
| ccp-pci.c | ||
| ccp-platform.c | ||
| Kconfig | ||
| Makefile | ||