drivers/net/wireless/purelifi/plfxlc/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/wireless/purelifi/plfxlc/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/wireless/purelifi/plfxlc/Kconfig
Extension: [no extension]
Size: 570 bytes
Lines: 15
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 PLFXLC
	tristate "pureLiFi X, XL, XC device support"
	depends on CFG80211 && MAC80211 && USB
	help
	   This option adds support for pureLiFi LiFi USB wireless
	   adapters. The pureLiFi X, XL, XC USB devices are based on
	   802.11 OFDM PHY but uses light as the transmission medium.
	   The driver supports common 802.11 encryption/authentication
	   methods including Open, WPA, WPA2-Personal and
	   WPA2-Enterprise (802.1X).

	   To compile this driver as a module, choose m here. The module will
	   be called plfxlc.

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.