drivers/phy/microchip/Kconfig

Source file repositories/reference/linux-study-clean/drivers/phy/microchip/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/phy/microchip/Kconfig
Extension: [no extension]
Size: 611 bytes
Lines: 23
Domain: Driver Families
Bucket: drivers/phy
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
# Phy drivers for Microchip devices
#

config PHY_SPARX5_SERDES
	tristate "Microchip Sparx5 SerDes PHY driver"
	select GENERIC_PHY
	depends on ARCH_SPARX5 || ARCH_LAN969X || COMPILE_TEST
	depends on OF
	depends on HAS_IOMEM
	help
	  Enable this for support of the 10G/25G SerDes on Microchip Sparx5.

config PHY_LAN966X_SERDES
	tristate "SerDes PHY driver for Microchip LAN966X"
	select GENERIC_PHY
	depends on SOC_LAN966 || MCHP_LAN966X_PCI || COMPILE_TEST
	depends on OF
	depends on MFD_SYSCON
	help
	  Enable this for supporting SerDes muxing with Microchip LAN966X

Annotation

Atlas domain: Driver Families / drivers/phy.
Implementation status: atlas-only.

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.