drivers/crypto/cavium/cpt/cpt_common.h

File Facts

System

Linux kernel

Corpus path

drivers/crypto/cavium/cpt/cpt_common.h

Extension

.h

Size

5969 bytes

Lines

154

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

• asm/byteorder.h
• linux/delay.h
• linux/pci.h
• cpt_hw_types.h

Detected Declarations

• struct cpt_mbox
• enum vftype
• enum cpt_mbox_opcode
• function cpt_write_csr64
• function cpt_read_csr64

Annotated Snippet

struct cpt_mbox {
	u64 msg; /* Message type MBOX[0] */
	u64 data;/* Data         MBOX[1] */
};

/* Register read/write APIs */
static inline void cpt_write_csr64(u8 __iomem *hw_addr, u64 offset,
				   u64 val)
{
	writeq(val, hw_addr + offset);
}

static inline u64 cpt_read_csr64(u8 __iomem *hw_addr, u64 offset)
{
	return readq(hw_addr + offset);
}
#endif /* __CPT_COMMON_H */

Annotation

• Immediate include surface: `asm/byteorder.h`, `linux/delay.h`, `linux/pci.h`, `cpt_hw_types.h`.
• Detected declarations: `struct cpt_mbox`, `enum vftype`, `enum cpt_mbox_opcode`, `function cpt_write_csr64`, `function cpt_read_csr64`.
• 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.