drivers/crypto/marvell/octeontx/otx_cptpf.h
Source file repositories/reference/linux-study-clean/drivers/crypto/marvell/octeontx/otx_cptpf.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/crypto/marvell/octeontx/otx_cptpf.h- Extension
.h- Size
- 999 bytes
- Lines
- 35
- 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/types.hlinux/device.hotx_cptpf_ucode.h
Detected Declarations
struct otx_cpt_device
Annotated Snippet
struct otx_cpt_device {
void __iomem *reg_base; /* Register start address */
struct pci_dev *pdev; /* Pci device handle */
struct otx_cpt_eng_grps eng_grps;/* Engine groups information */
struct list_head list;
u8 pf_type; /* PF type SE or AE */
u8 max_vfs; /* Maximum number of VFs supported by the CPT */
u8 vfs_enabled; /* Number of enabled VFs */
};
void otx_cpt_mbox_intr_handler(struct otx_cpt_device *cpt, int mbx);
void otx_cpt_disable_all_cores(struct otx_cpt_device *cpt);
#endif /* __OTX_CPTPF_H */
Annotation
- Immediate include surface: `linux/types.h`, `linux/device.h`, `otx_cptpf_ucode.h`.
- Detected declarations: `struct otx_cpt_device`.
- 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.