drivers/net/ethernet/amazon/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/amazon/Kconfig

Extension

[no extension]

Size

864 bytes

Lines

32

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

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
#
# Amazon network device configuration
#

config NET_VENDOR_AMAZON
	bool "Amazon Devices"
	default y
	help
	  If you have a network (Ethernet) device belonging to this class, say Y.

	  Note that the answer to this question doesn't directly affect the
	  kernel: saying N will just cause the configurator to skip all
	  the questions about Amazon devices. If you say Y, you will be asked
	  for your specific device in the following questions.

if NET_VENDOR_AMAZON

config ENA_ETHERNET
	tristate "Elastic Network Adapter (ENA) support"
	depends on PCI_MSI && !CPU_BIG_ENDIAN
	depends on PTP_1588_CLOCK_OPTIONAL
	select DIMLIB
	select NET_DEVLINK
	help
	  This driver supports Elastic Network Adapter (ENA)"

	  To compile this driver as a module, choose M here.
	  The module will be called ena.

endif #NET_VENDOR_AMAZON

Annotation

• Atlas domain: Driver Families / drivers/net.
• Implementation status: atlas-only.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.