drivers/net/ethernet/marvell/prestera/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/ethernet/marvell/prestera/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/marvell/prestera/Kconfig
Extension: [no extension]
Size: 775 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

# SPDX-License-Identifier: GPL-2.0-only
#
# Marvell Prestera drivers configuration
#

config PRESTERA
	tristate "Marvell Prestera Switch ASICs support"
	depends on NET_SWITCHDEV && VLAN_8021Q
	depends on BRIDGE || BRIDGE=n
	select NET_DEVLINK
	select PHYLINK
	help
	  This driver supports Marvell Prestera Switch ASICs family.

	  To compile this driver as a module, choose M here: the
	  module will be called prestera.

config PRESTERA_PCI
	tristate "PCI interface driver for Marvell Prestera Switch ASICs family"
	depends on PCI && HAS_IOMEM && PRESTERA
	default PRESTERA
	help
	  This is implementation of PCI interface support for Marvell Prestera
	  Switch ASICs family.

	  To compile this driver as a module, choose M here: the
	  module will be called prestera_pci.

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.