drivers/net/wireless/mediatek/mt76/mt7915/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/wireless/mediatek/mt76/mt7915/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/wireless/mediatek/mt76/mt7915/Kconfig
Extension: [no extension]
Size: 791 bytes
Lines: 26
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: BSD-3-Clause-Clear
config MT7915E
	tristate "MediaTek MT7915E (PCIe) support"
	select MT76_CONNAC_LIB
	select WANT_DEV_COREDUMP
	depends on MAC80211
	depends on PCI
	select RELAY
	help
	  This adds support for MT7915-based PCIe wireless devices,
	  which support concurrent dual-band operation at both 5GHz
	  and 2.4GHz IEEE 802.11ax 4x4:4SS 1024-QAM, 160MHz channels,
	  OFDMA, spatial reuse and dual carrier modulation.

	  To compile this driver as a module, choose M here.

config MT798X_WMAC
	bool "MT798x (SoC) WMAC support"
	depends on MT7915E
	depends on ARCH_MEDIATEK || COMPILE_TEST
	select REGMAP
	help
	  This adds support for the built-in WMAC on MT7981 and MT7986 SoC device
	  which has the same feature set as a MT7915, but enables 6E
	  support.

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.