drivers/net/ethernet/marvell/octeontx2/af/cgx.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/marvell/octeontx2/af/cgx.c

Extension

.c

Size

52172 bytes

Lines

2068

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/acpi.h
• linux/module.h
• linux/interrupt.h
• linux/pci.h
• linux/netdevice.h
• linux/etherdevice.h
• linux/ethtool.h
• linux/phy.h
• linux/of.h
• linux/of_mdio.h
• linux/of_net.h
• cgx.h
• rvu.h
• lmac_common.h

Detected Declarations

• function is_dev_rpm
• function is_lmac_valid
• function get_sequence_id_of_lmac
• function for_each_set_bit
• function cgx_get_fifo_len
• function cgx_write
• function cgx_read
• function cgx_get_cgxcnt_max
• function cgx_get_lmac_cnt
• function list_for_each_entry
• function cgx_lmac_write
• function cgx_lmac_read
• function cgx_get_cgxid
• function cgx_lmac_get_p2x
• function cgx_get_nix_resetbit
• function cgx_get_link_info
• function cgx_lmac_addr_set
• function cgx_read_dmac_ctrl
• function cgx_read_dmac_entry
• function cgx_lmac_addr_add
• function cgx_lmac_addr_reset
• function cgx_lmac_addr_update
• function cgx_lmac_addr_del
• function cgx_lmac_addr_max_entries_get
• function cgx_lmac_addr_get
• function cgx_set_pkind
• function cgx_get_lmac_type
• function cgx_get_lmac_fifo_len
• function cgx_lmac_internal_loopback
• function cgx_lmac_promisc_config
• function cgx_lmac_get_pause_frm_status
• function cgx_lmac_enadis_rx_pause_fwding
• function cgx_get_rx_stats
• function cgx_get_tx_stats
• function cgx_features_get
• function cgx_stats_reset
• function cgx_set_fec_stats_count
• function cgx_get_fec_stats
• function cgx_lmac_rx_tx_enable
• function cgx_lmac_tx_enable
• function cgx_lmac_enadis_pause_frm
• function cgx_lmac_pause_frm_config
• function verify_lmac_fc_cfg
• function cgx_lmac_pfc_config
• function cgx_lmac_get_pfc_frm_cfg
• function cgx_lmac_ptp_config
• function cgx_fwi_cmd_send
• function msecs_to_jiffies

Annotated Snippet

struct pci_driver cgx_driver = {
	.name = DRV_NAME,
	.id_table = cgx_id_table,
	.probe = cgx_probe,
	.remove = cgx_remove,
};

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/module.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/netdevice.h`, `linux/etherdevice.h`, `linux/ethtool.h`, `linux/phy.h`.
• Detected declarations: `function is_dev_rpm`, `function is_lmac_valid`, `function get_sequence_id_of_lmac`, `function for_each_set_bit`, `function cgx_get_fifo_len`, `function cgx_write`, `function cgx_read`, `function cgx_get_cgxcnt_max`, `function cgx_get_lmac_cnt`, `function list_for_each_entry`.
• 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.