drivers/net/ethernet/intel/iavf/iavf_types.h
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/intel/iavf/iavf_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/intel/iavf/iavf_types.h- Extension
.h- Size
- 827 bytes
- Lines
- 35
- 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
iavf_types.hlinux/avf/virtchnl.hlinux/ptp_clock_kernel.h
Detected Declarations
struct iavf_ptp_aq_cmdstruct iavf_ptp
Annotated Snippet
struct iavf_ptp_aq_cmd {
struct list_head list;
enum virtchnl_ops v_opcode:16;
u16 msglen;
u8 msg[] __counted_by(msglen);
};
struct iavf_ptp {
wait_queue_head_t phc_time_waitqueue;
struct virtchnl_ptp_caps hw_caps;
struct ptp_clock_info info;
struct ptp_clock *clock;
struct list_head aq_cmds;
u64 cached_phc_time;
unsigned long cached_phc_updated;
/* Lock protecting access to the AQ command list */
struct mutex aq_cmd_lock;
struct kernel_hwtstamp_config hwtstamp_config;
bool phc_time_ready:1;
};
#endif /* _IAVF_TYPES_H_ */
Annotation
- Immediate include surface: `iavf_types.h`, `linux/avf/virtchnl.h`, `linux/ptp_clock_kernel.h`.
- Detected declarations: `struct iavf_ptp_aq_cmd`, `struct iavf_ptp`.
- 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.