drivers/net/ethernet/cavium/thunder/thunder_bgx.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/cavium/thunder/thunder_bgx.c

Extension

.c

Size

45436 bytes

Lines

1737

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.
• 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/acpi.h
• linux/module.h
• linux/interrupt.h
• linux/pci.h
• linux/netdevice.h
• linux/etherdevice.h
• linux/phy.h
• linux/of.h
• linux/of_mdio.h
• linux/of_net.h
• nic_reg.h
• nic.h
• thunder_bgx.h

Detected Declarations

• struct dmac_map
• struct lmac
• struct bgx
• enum MCAST_MODE
• function bgx_reg_read
• function bgx_reg_write
• function bgx_reg_modify
• function bgx_poll_reg
• function set_max_bgx_per_node
• function bgx_get_map
• function bgx_get_lmac_count
• function bgx_get_lmac_link_state
• function bgx_set_lmac_mac
• function bgx_flush_dmac_cam_filter
• function bgx_lmac_remove_filters
• function bgx_lmac_save_filter
• function bgx_set_dmac_cam_filter_mac
• function bgx_set_dmac_cam_filter
• function bgx_set_xcast_mode
• function bgx_reset_xcast_mode
• function bgx_lmac_rx_tx_enable
• function bgx_config_timestamping
• function bgx_lmac_get_pfc
• function bgx_lmac_set_pfc
• function bgx_sgmii_change_link_state
• function bgx_lmac_handler
• function bgx_get_rx_stats
• function bgx_get_tx_stats
• function bgx_lmac_internal_loopback
• function bgx_lmac_sgmii_init
• function bgx_lmac_xaui_init
• function bgx_xaui_check_link
• function bgx_poll_for_sgmii_link
• function bgx_poll_for_link
• function phy_interface_mode
• function bgx_lmac_enable
• function bgx_lmac_disable
• function bgx_init_hw
• function bgx_get_lane2sds_cfg
• function bgx_print_qlm_mode
• function lmac_set_lane2sds
• function lmac_set_training
• function bgx_set_lmac_config
• function bgx_get_qlm_mode
• function acpi_get_mac_address
• function bgx_acpi_register_phy
• function bgx_acpi_match_id
• function bgx_init_acpi_phy

Annotated Snippet

static struct pci_driver bgx_driver = {
	.name = DRV_NAME,
	.id_table = bgx_id_table,
	.probe = bgx_probe,
	.remove = bgx_remove,
};

static int __init bgx_init_module(void)
{
	pr_info("%s, ver %s\n", DRV_NAME, DRV_VERSION);

	return pci_register_driver(&bgx_driver);
}

static void __exit bgx_cleanup_module(void)
{
	pci_unregister_driver(&bgx_driver);
}

module_init(bgx_init_module);
module_exit(bgx_cleanup_module);

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/module.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/netdevice.h`, `linux/etherdevice.h`, `linux/phy.h`, `linux/of.h`.
• Detected declarations: `struct dmac_map`, `struct lmac`, `struct bgx`, `enum MCAST_MODE`, `function bgx_reg_read`, `function bgx_reg_write`, `function bgx_reg_modify`, `function bgx_poll_reg`, `function set_max_bgx_per_node`, `function bgx_get_map`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern implementation candidate.
• 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.