drivers/net/wireless/quantenna/qtnfmac/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/quantenna/qtnfmac/Kconfig

Extension

[no extension]

Size

596 bytes

Lines

22

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 QTNFMAC
	tristate
	depends on QTNFMAC_PCIE
	default m if QTNFMAC_PCIE=m
	default y if QTNFMAC_PCIE=y

config QTNFMAC_PCIE
	tristate "Quantenna QSR1000/QSR2000/QSR10g PCIe support"
	default n
	depends on PCI && CFG80211
	select QTNFMAC
	select FW_LOADER
	select CRC32
	help
	  This option adds support for wireless adapters based on Quantenna
	  802.11ac QSR10g (aka Pearl) and QSR1000/QSR2000 (aka Topaz)
	  FullMAC chipsets running over PCIe.

	  If you choose to build it as a module, two modules will be built:
	  qtnfmac.ko and qtnfmac_pcie.ko.

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.