drivers/net/ethernet/marvell/octeon_ep_vf/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/marvell/octeon_ep_vf/Kconfig
Extension: [no extension]
Size: 595 bytes
Lines: 20
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's Octeon PCI Endpoint NIC VF Driver Configuration
#

config OCTEON_EP_VF
	tristate "Marvell Octeon PCI Endpoint NIC VF Driver"
	depends on 64BIT
	depends on PCI
	help
	  This driver supports the networking functionality of Marvell's
	  Octeon PCI Endpoint NIC VF.

	  To know the list of devices supported by this driver, refer to the
	  documentation in
	  <file:Documentation/networking/device_drivers/ethernet/marvell/octeon_ep_vf.rst>.

	  To compile this driver as a module, choose M here.
	  The name of the module will be octeon_ep_vf.

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.