drivers/net/ethernet/microchip/sparx5/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/ethernet/microchip/sparx5/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/microchip/sparx5/Kconfig
Extension: [no extension]
Size: 859 bytes
Lines: 34
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 SPARX5_SWITCH
	tristate "Sparx5 switch driver"
	depends on NET_SWITCHDEV
	depends on HAS_IOMEM
	depends on OF
	depends on ARCH_SPARX5 || ARCH_LAN969X || COMPILE_TEST
	depends on PTP_1588_CLOCK_OPTIONAL
	depends on BRIDGE || BRIDGE=n
	select PHYLINK
	select PHY_SPARX5_SERDES
	select RESET_CONTROLLER
	select VCAP
	select FDMA
	help
	  This driver supports the Sparx5 network switch device.

config SPARX5_DCB
	bool "Data Center Bridging (DCB) support"
	depends on SPARX5_SWITCH && DCB
	default y
	help
	  Say Y here if you want to use Data Center Bridging (DCB) in the
	  driver. This can be used to assign priority to traffic, based on
	  DSCP and PCP.

	  If unsure, set to Y.

config LAN969X_SWITCH
	bool "Lan969x switch driver"
	depends on SPARX5_SWITCH
	select PAGE_POOL
	help
	  This driver supports the lan969x family of network switch devices.

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.