AMD Secure Processor and Cryptographic Coprocessor (CCP/PSP/SEV)
The on-die security and crypto offload block built into AMD CPUs and APUs since the mid-2010s, covering the Cryptographic Coprocessor that accelerates AES, SHA, and RSA, and the Platform Security Processor that backs SEV and SEV-SNP memory encryption for confidential VMs on EPYC and Ryzen parts.
recommendation
It should stay in the kernel because the hardware ships in every current AMD EPYC and Ryzen processor and underpins SEV and Infinity Guard confidential-computing features that cloud providers actively deploy. Upstream activity is healthy, with patches still landing in linux-crypto in late 2025 and fixes flowing into stable, and AMD continues to market these capabilities on shipping EPYC 4004/8004/9004/9005 parts.
repository signals
sources
- lore.kernel.org
Recent upstream maintenance still touches drivers/crypto/ccp/ccp-dev.c in linux-crypto; not a dormant orphaned driver.
- lore.kernel.org
drivers/crypto/ccp/sp-dev.c was still being carried in stable releases in March 2026, indicating ongoing support rather than removal.
- amd.com
AMD was still marketing EPYC 4004/4005/700x/8004/9004/9005 security features including SEV/Infinity Guard, implying current-generation hardware still using the PSP/SEV stack.
- amd.com
AMD still markets SEV-based confidential computing for current EPYC deployments, supporting continued real-world use of the PSP/SEV side of this driver family.
codex reasoning notes (technical)
Tool evidence: `exec_command` read drivers/crypto/ccp/Kconfig, which identifies this directory as the AMD Secure Processor / CCP / PSP / SEV driver stack. `lore_activity` on ccp-dev.c found linux-crypto patch traffic in 2025; `lore_activity` on sp-dev.c found 2026 stable uptake. A `lore_file_timeline` query on the directory path returned no hits, which appears to be a path-index blind spot rather than inactivity. `web.search_query` found current AMD Infinity Guard and confidential-computing product pages showing the hardware family is still sold and actively deployed. No replacement driver or removal thread was found in the evidence gathered, so removal/deprecation is not justified.