drivers/crypto/cavium/cpt/cptpf_main.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/cavium/cpt/cptpf_main.c

Extension

.c

Size

16925 bytes

Lines

670

Domain

Driver Families

Bucket

drivers/crypto

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h
• linux/firmware.h
• linux/interrupt.h
• linux/module.h
• linux/moduleparam.h
• linux/pci.h
• linux/printk.h
• cptpf.h

Detected Declarations

• struct ucode_header
• function cpt_disable_cores
• function cpt_enable_cores
• function cpt_configure_group
• function cpt_disable_mbox_interrupts
• function cpt_disable_ecc_interrupts
• function cpt_disable_exec_interrupts
• function cpt_disable_all_interrupts
• function cpt_enable_mbox_interrupts
• function cpt_load_microcode
• function do_cpt_init
• function cpt_ucode_load_fw
• function cpt_ucode_load
• function cpt_mbx0_intr_handler
• function cpt_reset
• function cpt_find_max_enabled_cores
• function cpt_check_bist_status
• function cpt_check_exe_bist_status
• function cpt_disable_all_cores
• function cpt_disable_all_cores
• function cpt_device_init
• function cpt_register_interrupts
• function cpt_unregister_interrupts
• function cpt_sriov_init
• function cpt_probe
• function cpt_remove
• function cpt_shutdown

Annotated Snippet

static struct pci_driver cpt_pci_driver = {
	.name = DRV_NAME,
	.id_table = cpt_id_table,
	.probe = cpt_probe,
	.remove = cpt_remove,
	.shutdown = cpt_shutdown,
};

module_pci_driver(cpt_pci_driver);

MODULE_AUTHOR("George Cherian <george.cherian@cavium.com>");
MODULE_DESCRIPTION("Cavium Thunder CPT Physical Function Driver");
MODULE_LICENSE("GPL v2");
MODULE_VERSION(DRV_VERSION);

Annotation

• Immediate include surface: `linux/device.h`, `linux/firmware.h`, `linux/interrupt.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/pci.h`, `linux/printk.h`, `cptpf.h`.
• Detected declarations: `struct ucode_header`, `function cpt_disable_cores`, `function cpt_enable_cores`, `function cpt_configure_group`, `function cpt_disable_mbox_interrupts`, `function cpt_disable_ecc_interrupts`, `function cpt_disable_exec_interrupts`, `function cpt_disable_all_interrupts`, `function cpt_enable_mbox_interrupts`, `function cpt_load_microcode`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: pattern implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.