Revision c9f21cb6388898bfe69886d001316dae7ecc9a4b authored by Tom Lendacky on 05 September 2014, 15:31:09 UTC, committed by Herbert Xu on 24 September 2014, 06:23:34 UTC
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>
1 parent 413e557
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 151 bytes |
| Kconfig | -rw-r--r-- | 3.0 KB |
| Makefile | -rw-r--r-- | 2.3 KB |
| gen_init_cpio.c | -rw-r--r-- | 12.7 KB |
| initramfs_data.S | -rw-r--r-- | 1.3 KB |
Computing file changes ...
