drivers/net/ethernet/pensando/ionic/ionic_bus_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/pensando/ionic/ionic_bus_pci.c

Extension

.c

Size

12168 bytes

Lines

541

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/module.h
• linux/netdevice.h
• linux/etherdevice.h
• linux/pci.h
• ionic.h
• ionic_bus.h
• ionic_lif.h
• ionic_aux.h
• ionic_debugfs.h

Detected Declarations

• function ionic_bus_get_irq
• function ionic_bus_alloc_irq_vectors
• function ionic_bus_free_irq_vectors
• function ionic_map_bars
• function ionic_unmap_bars
• function ionic_bus_unmap_dbpage
• function ionic_vf_dealloc_locked
• function ionic_vf_dealloc
• function ionic_vf_alloc
• function ionic_sriov_configure
• function ionic_clear_pci
• function ionic_setup_one
• function ionic_probe
• function ionic_remove
• function ionic_reset_prepare
• function ionic_reset_done
• function ionic_pci_error_detected
• function ionic_pci_error_resume
• function ionic_bus_register_driver
• function ionic_bus_unregister_driver

Annotated Snippet

static struct pci_driver ionic_driver = {
	.name = IONIC_DRV_NAME,
	.id_table = ionic_id_table,
	.probe = ionic_probe,
	.remove = ionic_remove,
	.sriov_configure = ionic_sriov_configure,
	.err_handler = &ionic_err_handler
};

int ionic_bus_register_driver(void)
{
	return pci_register_driver(&ionic_driver);
}

void ionic_bus_unregister_driver(void)
{
	pci_unregister_driver(&ionic_driver);
}

Annotation

• Immediate include surface: `linux/module.h`, `linux/netdevice.h`, `linux/etherdevice.h`, `linux/pci.h`, `ionic.h`, `ionic_bus.h`, `ionic_lif.h`, `ionic_aux.h`.
• Detected declarations: `function ionic_bus_get_irq`, `function ionic_bus_alloc_irq_vectors`, `function ionic_bus_free_irq_vectors`, `function ionic_map_bars`, `function ionic_unmap_bars`, `function ionic_bus_unmap_dbpage`, `function ionic_vf_dealloc_locked`, `function ionic_vf_dealloc`, `function ionic_vf_alloc`, `function ionic_sriov_configure`.
• 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.