drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.h

Extension

.h

Size

5772 bytes

Lines

140

Domain

Driver Families

Bucket

drivers/net

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.h

Detected Declarations

• struct ixgbe_hw
• struct ixgbe_mbx_operations
• enum ixgbe_pfvf_api_rev

Annotated Snippet

struct ixgbe_mbx_operations {
	int (*init_params)(struct ixgbe_hw *hw);
	int (*read)(struct ixgbe_hw *hw, u32 *msg, u16 size, u16 vf_number);
	int (*write)(struct ixgbe_hw *hw, u32 *msg, u16 size, u16 vf_number);
	int (*read_posted)(struct ixgbe_hw *hw, u32 *msg, u16 size, u16 mbx_id);
	int (*write_posted)(struct ixgbe_hw *hw, u32 *msg, u16 size,
			    u16 mbx_id);
	int (*check_for_msg)(struct ixgbe_hw *hw, u16 vf_number);
	int (*check_for_ack)(struct ixgbe_hw *hw, u16 vf_number);
	int (*check_for_rst)(struct ixgbe_hw *hw, u16 vf_number);
};

extern const struct ixgbe_mbx_operations mbx_ops_generic;

#endif /* _IXGBE_MBX_H_ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct ixgbe_hw`, `struct ixgbe_mbx_operations`, `enum ixgbe_pfvf_api_rev`.
• Atlas domain: Driver Families / drivers/net.
• 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.