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 |
|---|---|---|
| Kconfig | -rw-r--r-- | 62.5 KB |
| Makefile | -rw-r--r-- | 1.1 KB |
| calibrate.c | -rw-r--r-- | 8.5 KB |
| do_mounts.c | -rw-r--r-- | 14.3 KB |
| do_mounts.h | -rw-r--r-- | 1.4 KB |
| do_mounts_initrd.c | -rw-r--r-- | 3.4 KB |
| do_mounts_md.c | -rw-r--r-- | 8.2 KB |
| do_mounts_rd.c | -rw-r--r-- | 8.7 KB |
| init_task.c | -rw-r--r-- | 728 bytes |
| initramfs.c | -rw-r--r-- | 13.7 KB |
| main.c | -rw-r--r-- | 24.7 KB |
| noinitramfs.c | -rw-r--r-- | 1.5 KB |
| version.c | -rw-r--r-- | 1.2 KB |
Computing file changes ...
