drivers/crypto/cavium/cpt/cptpf_mbox.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/cavium/cpt/cptpf_mbox.c

Extension

.c

Size

4482 bytes

Lines

161

Domain

Driver Families

Bucket

drivers/crypto

Inferred role

Driver Families: implementation source

Status

source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• cptpf.h

Detected Declarations

• function Copyright
• function cpt_mbox_send_ack
• function cpt_clear_mbox_intr
• function cpt_cfg_qlen_for_vf
• function cpt_cfg_vq_priority
• function cpt_bind_vq_to_grp
• function cpt_handle_mbox_intr
• function cpt_mbox_intr_handler

Annotated Snippet

if (intr & (1ULL << vf)) {
			dev_dbg(&cpt->pdev->dev, "Intr from VF %d\n", vf);
			cpt_handle_mbox_intr(cpt, vf);
			cpt_clear_mbox_intr(cpt, vf);
		}
	}
}

Annotation

• Immediate include surface: `linux/module.h`, `cptpf.h`.
• Detected declarations: `function Copyright`, `function cpt_mbox_send_ack`, `function cpt_clear_mbox_intr`, `function cpt_cfg_qlen_for_vf`, `function cpt_cfg_vq_priority`, `function cpt_bind_vq_to_grp`, `function cpt_handle_mbox_intr`, `function cpt_mbox_intr_handler`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: source 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.