include/linux/phy.h

File Facts

System

Linux kernel

Corpus path

include/linux/phy.h

Extension

.h

Size

87931 bytes

Lines

2488

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/compiler.h
• linux/spinlock.h
• linux/ethtool.h
• linux/leds.h
• linux/linkmode.h
• linux/netlink.h
• linux/mdio.h
• linux/mii.h
• linux/mii_timestamper.h
• linux/module.h
• linux/timer.h
• linux/workqueue.h
• linux/mod_devicetable.h
• linux/u64_stats_sync.h
• linux/irqreturn.h
• linux/iopoll.h
• linux/refcount.h
• linux/atomic.h
• net/eee.h

Detected Declarations

• struct device
• struct kernel_hwtstamp_config
• struct phylink
• struct phy_port
• struct sfp_bus
• struct sfp_upstream_ops
• struct sk_buff
• struct mdio_bus_stats
• struct mii_bus
• struct phy_c45_device_ids
• struct macsec_context
• struct macsec_ops
• struct phy_oatc14_sqi_capability
• struct phy_device
• struct phy_tdr_config
• struct phy_plca_cfg
• struct phy_plca_status
• struct phy_led
• struct phy_mse_capability
• struct phy_mse_snapshot
• struct phy_driver
• enum phy_state
• enum link_inband_signalling
• enum phy_led_modes
• enum phy_mse_channel
• function phy_interface_zero
• function phy_interface_empty
• function phy_interface_copy
• function phy_interface_weight
• function phy_interface_and
• function phy_interface_or
• function phy_interface_set_rgmii
• function rgmii_clock
• function to
• function phy_id_compare_vendor
• function phy_id_compare_model
• function phydev_id_compare
• function phy_is_started
• function phy_driver_is_genphy
• function phy_disable_eee_mode
• function phy_can_wakeup
• function phy_read
• function __phy_read
• function phy_write
• function __phy_write
• function __phy_modify_changed
• function __phy_set_bits
• function __phy_clear_bits

Annotated Snippet

* replaces module_init() and module_exit().
 */
#define phy_module_driver(__phy_drivers, __count)			\
static int __init phy_module_init(void)					\
{									\
	return phy_drivers_register(__phy_drivers, __count, THIS_MODULE); \
}									\
module_init(phy_module_init);						\
static void __exit phy_module_exit(void)				\
{									\
	phy_drivers_unregister(__phy_drivers, __count);			\
}									\
module_exit(phy_module_exit)

#define module_phy_driver(__phy_drivers)				\
	phy_module_driver(__phy_drivers, ARRAY_SIZE(__phy_drivers))

#endif /* __PHY_H */

Annotation

• Immediate include surface: `linux/compiler.h`, `linux/spinlock.h`, `linux/ethtool.h`, `linux/leds.h`, `linux/linkmode.h`, `linux/netlink.h`, `linux/mdio.h`, `linux/mii.h`.
• Detected declarations: `struct device`, `struct kernel_hwtstamp_config`, `struct phylink`, `struct phy_port`, `struct sfp_bus`, `struct sfp_upstream_ops`, `struct sk_buff`, `struct mdio_bus_stats`, `struct mii_bus`, `struct phy_c45_device_ids`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: integration 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.