drivers/net/ethernet/alibaba/eea/eea_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/alibaba/eea/eea_pci.c

Extension

.c

Size

17194 bytes

Lines

745

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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

• linux/io-64-nonatomic-lo-hi.h
• linux/iopoll.h
• eea_net.h
• eea_pci.h

Detected Declarations

• struct eea_pci_cfg
• struct eea_pci_device
• function eea_pci_domain_nr
• function eea_pci_bdf
• function eea_pci_io_set_status
• function eea_pci_io_get_status
• function eea_add_status
• function eea_device_reset
• function eea_pci_set_aq_up
• function eea_negotiate
• function eea_pci_release_resource
• function eea_pci_setup
• function eea_pci_active_aq
• function eea_pci_free_irq
• function eea_pci_request_irq
• function eea_ha_handle_reset
• function eea_ha_handle_work
• function eea_pci_ha_handle
• function eea_pci_free_ha_irq
• function eea_pci_ha_init
• function eea_pci_device_ts
• function eea_init_device
• function __eea_pci_probe
• function __eea_pci_remove
• function eea_pci_probe
• function eea_pci_remove
• function eea_pci_shutdown
• function eea_pci_init
• function eea_pci_exit
• module init eea_pci_init

Annotated Snippet

static struct pci_driver eea_pci_driver = {
	.name            = "alibaba_eea",
	.id_table        = eea_pci_id_table,
	.probe           = eea_pci_probe,
	.remove          = eea_pci_remove,
	.shutdown        = eea_pci_shutdown,
	.sriov_configure = pci_sriov_configure_simple,
};

static __init int eea_pci_init(void)
{
	return pci_register_driver(&eea_pci_driver);
}

static __exit void eea_pci_exit(void)
{
	pci_unregister_driver(&eea_pci_driver);
}

module_init(eea_pci_init);
module_exit(eea_pci_exit);

MODULE_DESCRIPTION("Driver for Alibaba Elastic Ethernet Adapter");
MODULE_AUTHOR("Xuan Zhuo <xuanzhuo@linux.alibaba.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/io-64-nonatomic-lo-hi.h`, `linux/iopoll.h`, `eea_net.h`, `eea_pci.h`.
• Detected declarations: `struct eea_pci_cfg`, `struct eea_pci_device`, `function eea_pci_domain_nr`, `function eea_pci_bdf`, `function eea_pci_io_set_status`, `function eea_pci_io_get_status`, `function eea_add_status`, `function eea_device_reset`, `function eea_pci_set_aq_up`, `function eea_negotiate`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.