drivers/staging/most/Kconfig
Source file repositories/reference/linux-study-clean/drivers/staging/most/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/most/Kconfig- Extension
[no extension]- Size
- 689 bytes
- Lines
- 28
- Domain
- Driver Families
- Bucket
- drivers/staging
- 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
menuconfig MOST_COMPONENTS
tristate "MOST support"
depends on HAS_DMA && CONFIGFS_FS && MOST
default n
help
Say Y here if you want to enable MOST support.
This driver needs at least one additional component to enable the
desired access from userspace (e.g. character devices) and one that
matches the network controller's hardware interface (e.g. USB).
To compile this driver as a module, choose M here: the
module will be called most_core.
If in doubt, say N here.
if MOST_COMPONENTS
source "drivers/staging/most/net/Kconfig"
source "drivers/staging/most/video/Kconfig"
source "drivers/staging/most/dim2/Kconfig"
endif
Annotation
- Atlas domain: Driver Families / drivers/staging.
- 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.