drivers/crypto/marvell/octeontx2/otx2_cptpf_main.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/marvell/octeontx2/otx2_cptpf_main.c

Extension

.c

Size

23560 bytes

Lines

887

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/firmware.h
• linux/sysfs.h
• otx2_cpt_hw_types.h
• otx2_cpt_common.h
• otx2_cpt_devlink.h
• otx2_cptpf_ucode.h
• otx2_cptpf.h
• cn10k_cpt.h
• rvu_reg.h

Detected Declarations

• function cptpf_enable_vfpf_mbox_intr
• function cptpf_disable_vfpf_mbox_intr
• function cptpf_enable_vf_flr_me_intrs
• function cptpf_disable_vf_flr_me_intrs
• function cptpf_flr_wq_handler
• function cptpf_vf_flr_intr
• function cptpf_vf_me_intr
• function cptpf_unregister_vfpf_intr
• function cptpf_register_vfpf_intr
• function cptpf_flr_wq_destroy
• function cptpf_flr_wq_init
• function cptpf_vfpf_mbox_init
• function cptpf_vfpf_mbox_destroy
• function cptpf_disable_afpf_mbox_intr
• function cptpf_register_afpf_mbox_intr
• function cptpf_afpf_mbox_init
• function cptpf_afpf_mbox_destroy
• function sso_pf_func_ovrd_show
• function sso_pf_func_ovrd_store
• function kvf_limits_show
• function kvf_limits_store
• function cpt_is_pf_usable
• function cptpf_get_rid
• function cptpf_check_block_implemented
• function cptpf_device_init
• function cptpf_sriov_disable
• function cptpf_sriov_enable
• function otx2_cptpf_sriov_configure
• function otx2_cptpf_probe
• function otx2_cptpf_remove

Annotated Snippet

static struct pci_driver otx2_cpt_pci_driver = {
	.name = OTX2_CPT_DRV_NAME,
	.id_table = otx2_cpt_id_table,
	.probe = otx2_cptpf_probe,
	.remove = otx2_cptpf_remove,
	.sriov_configure = otx2_cptpf_sriov_configure
};

module_pci_driver(otx2_cpt_pci_driver);

MODULE_IMPORT_NS("CRYPTO_DEV_OCTEONTX2_CPT");

MODULE_AUTHOR("Marvell");
MODULE_DESCRIPTION(OTX2_CPT_DRV_STRING);
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/firmware.h`, `linux/sysfs.h`, `otx2_cpt_hw_types.h`, `otx2_cpt_common.h`, `otx2_cpt_devlink.h`, `otx2_cptpf_ucode.h`, `otx2_cptpf.h`, `cn10k_cpt.h`.
• Detected declarations: `function cptpf_enable_vfpf_mbox_intr`, `function cptpf_disable_vfpf_mbox_intr`, `function cptpf_enable_vf_flr_me_intrs`, `function cptpf_disable_vf_flr_me_intrs`, `function cptpf_flr_wq_handler`, `function cptpf_vf_flr_intr`, `function cptpf_vf_me_intr`, `function cptpf_unregister_vfpf_intr`, `function cptpf_register_vfpf_intr`, `function cptpf_flr_wq_destroy`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.