drivers/net/dsa/lantiq/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/dsa/lantiq/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/dsa/lantiq/Kconfig
Extension: [no extension]
Size: 899 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/net
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

config NET_DSA_LANTIQ_COMMON
	tristate
	select REGMAP

config NET_DSA_LANTIQ_GSWIP
	tristate "Lantiq / Intel GSWIP"
	depends on HAS_IOMEM
	select NET_DSA_TAG_GSWIP
	select NET_DSA_LANTIQ_COMMON
	help
	  This enables support for the Lantiq / Intel GSWIP 2.1 found in
	  the xrx200 / VR9 SoC.

config NET_DSA_MXL_GSW1XX
	tristate "MaxLinear GSW1xx Ethernet switch support"
	select NET_DSA_TAG_MXL_GSW1XX
	select NET_DSA_LANTIQ_COMMON
	select PHY_COMMON_PROPS
	help
	  This enables support for the Intel/MaxLinear GSW1xx family of 1GE
	  switches.
	    GSW120 4 port, 2 PHYs, RGMII & SGMII/2500Base-X
	    GSW125 4 port, 2 PHYs, RGMII & SGMII/2500Base-X, industrial temperature
	    GSW140 6 port, 4 PHYs, RGMII & SGMII/2500Base-X
	    GSW141 6 port, 4 PHYs, RGMII & SGMII
	    GSW145 6 port, 4 PHYs, RGMII & SGMII/2500Base-X, industrial temperature
	    GSW150 7 port, 5 PHYs, 1x GMII/RGMII, 1x RGMII

Annotation

Atlas domain: Driver Families / drivers/net.
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.