drivers/net/dsa/netc/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/dsa/netc/Kconfig
Extension: [no extension]
Size: 560 bytes
Lines: 17
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

# SPDX-License-Identifier: GPL-2.0-only
config NET_DSA_NETC_SWITCH
	tristate "NXP NETC Ethernet switch support"
	depends on ARM64 || COMPILE_TEST
	depends on NET_DSA && PCI
	depends on NET_VENDOR_FREESCALE
	select NET_DSA_TAG_NETC
	select FSL_ENETC_MDIO
	select NXP_NTMP
	select NXP_NETC_LIB
	help
	  This driver supports the NXP NETC Ethernet switch, which is embedded
	  as a PCIe function of the NXP NETC IP. But note that this driver is
	  only available for NETC v4.3 and later versions.

	  If compiled as module (M), the module name is nxp-netc-switch.

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.