drivers/crypto/intel/qat/qat_common/adf_module.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/intel/qat/qat_common/adf_module.c

Extension

.c

Size

1243 bytes

Lines

64

Domain

Driver Families

Bucket

drivers/crypto

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.

Dependency Surface

• crypto/algapi.h
• linux/errno.h
• linux/module.h
• adf_common_drv.h

Detected Declarations

• function adf_register_module
• function adf_unregister_module
• module init adf_register_module

Annotated Snippet

module_init(adf_register_module);
module_exit(adf_unregister_module);
MODULE_LICENSE("Dual BSD/GPL");
MODULE_AUTHOR("Intel");
MODULE_DESCRIPTION("Intel(R) QuickAssist Technology");
MODULE_ALIAS_CRYPTO("intel_qat");
MODULE_IMPORT_NS("CRYPTO_INTERNAL");

Annotation

• Immediate include surface: `crypto/algapi.h`, `linux/errno.h`, `linux/module.h`, `adf_common_drv.h`.
• Detected declarations: `function adf_register_module`, `function adf_unregister_module`, `module init adf_register_module`.
• Atlas domain: Driver Families / drivers/crypto.
• 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.