drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c- Extension
.c- Size
- 38773 bytes
- Lines
- 1399
- 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/clk-provider.hlinux/pci.hlinux/dmi.hlinux/platform_data/x86/intel_pmc_ipc.hasm/cpuid/api.hdwmac-intel.hdwmac4.hstmmac.hstmmac_ptp.h
Detected Declarations
struct pmc_serdes_regsstruct pmc_serdes_reg_infostruct intel_priv_datastruct stmmac_pci_func_datastruct stmmac_pci_dmi_datastruct stmmac_pci_infofunction stmmac_pci_find_phy_addrfunction serdes_status_pollfunction intel_serdes_powerupfunction intel_serdes_powerdownfunction tgl_get_interfacesfunction intel_mgbe_ptp_clk_freq_configfunction get_arttimefunction stmmac_cross_ts_isrfunction intel_crosststampfunction stmmac_cross_ts_isrfunction intel_mgbe_pse_crossts_adjfunction intel_tsn_lane_is_availablefunction intel_set_reg_accessfunction intel_mac_finishfunction common_default_datafunction intel_mgbe_common_datafunction ehl_common_datafunction ehl_sgmii_datafunction ehl_rgmii_datafunction ehl_pse0_common_datafunction ehl_pse0_rgmii1g_datafunction ehl_pse0_sgmii1g_datafunction ehl_pse1_common_datafunction ehl_pse1_rgmii1g_datafunction ehl_pse1_sgmii1g_datafunction tgl_common_datafunction tgl_sgmii_phy0_datafunction tgl_sgmii_phy1_datafunction adls_sgmii_phy0_datafunction adls_sgmii_phy1_datafunction adln_common_datafunction adln_sgmii_phy0_datafunction quark_default_datafunction stmmac_config_single_msifunction stmmac_config_multi_msifunction intel_eth_pci_suspendfunction intel_eth_pci_resumefunction intel_eth_pci_probefunction intel_eth_pci_remove
Annotated Snippet
static struct pci_driver intel_eth_pci_driver = {
.name = "intel-eth-pci",
.id_table = intel_eth_pci_id_table,
.probe = intel_eth_pci_probe,
.remove = intel_eth_pci_remove,
.driver = {
.pm = &stmmac_simple_pm_ops,
},
};
module_pci_driver(intel_eth_pci_driver);
MODULE_DESCRIPTION("INTEL 10/100/1000 Ethernet PCI driver");
MODULE_AUTHOR("Voon Weifeng <weifeng.voon@intel.com>");
MODULE_LICENSE("GPL v2");
Annotation
- Immediate include surface: `linux/clk-provider.h`, `linux/pci.h`, `linux/dmi.h`, `linux/platform_data/x86/intel_pmc_ipc.h`, `asm/cpuid/api.h`, `dwmac-intel.h`, `dwmac4.h`, `stmmac.h`.
- Detected declarations: `struct pmc_serdes_regs`, `struct pmc_serdes_reg_info`, `struct intel_priv_data`, `struct stmmac_pci_func_data`, `struct stmmac_pci_dmi_data`, `struct stmmac_pci_info`, `function stmmac_pci_find_phy_addr`, `function serdes_status_poll`, `function intel_serdes_powerup`, `function intel_serdes_powerdown`.
- 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.