drivers/net/ethernet/intel/idpf/idpf_main.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/intel/idpf/idpf_main.c

Extension

.c

Size

10299 bytes

Lines

393

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• idpf.h
• idpf_devids.h
• idpf_lan_vf_regs.h
• idpf_virtchnl.h

Detected Declarations

• function idpf_get_device_type
• function idpf_dev_init
• function idpf_remove
• function idpf_shutdown
• function idpf_cfg_hw
• function idpf_probe

Annotated Snippet

static struct pci_driver idpf_driver = {
	.name			= KBUILD_MODNAME,
	.id_table		= idpf_pci_tbl,
	.probe			= idpf_probe,
	.sriov_configure	= idpf_sriov_configure,
	.remove			= idpf_remove,
	.shutdown		= idpf_shutdown,
};
module_pci_driver(idpf_driver);

Annotation

• Immediate include surface: `idpf.h`, `idpf_devids.h`, `idpf_lan_vf_regs.h`, `idpf_virtchnl.h`.
• Detected declarations: `function idpf_get_device_type`, `function idpf_dev_init`, `function idpf_remove`, `function idpf_shutdown`, `function idpf_cfg_hw`, `function idpf_probe`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern 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.