drivers/s390/crypto/pkey_cca.c
Source file repositories/reference/linux-study-clean/drivers/s390/crypto/pkey_cca.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/s390/crypto/pkey_cca.c- Extension
.c- Size
- 16888 bytes
- Lines
- 635
- Domain
- Driver Families
- Bucket
- drivers/s390
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/init.hlinux/module.hlinux/cpufeature.hzcrypt_ccamisc.hpkey_base.h
Detected Declarations
function is_cca_keyfunction is_cca_keytypefunction cca_apqns4keyfunction cca_apqns4typefunction cca_key2protkeyfunction keyfunction keyfunction cca_verifykeyfunction cca_slowpath_key2protkeyfunction pkey_cca_initfunction pkey_cca_exitmodule init pkey_cca_init
Annotated Snippet
module_init(pkey_cca_init);
module_exit(pkey_cca_exit);Annotation
- Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/cpufeature.h`, `zcrypt_ccamisc.h`, `pkey_base.h`.
- Detected declarations: `function is_cca_key`, `function is_cca_keytype`, `function cca_apqns4key`, `function cca_apqns4type`, `function cca_key2protkey`, `function key`, `function key`, `function cca_verifykey`, `function cca_slowpath_key2protkey`, `function pkey_cca_init`.
- Atlas domain: Driver Families / drivers/s390.
- Implementation status: integration implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.