drivers/soc/vt8500/Kconfig
Source file repositories/reference/linux-study-clean/drivers/soc/vt8500/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/soc/vt8500/Kconfig- Extension
[no extension]- Size
- 526 bytes
- Lines
- 20
- Domain
- Driver Families
- Bucket
- drivers/soc
- 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
if ARCH_VT8500 || COMPILE_TEST
menu "VIA/WonderMedia SoC drivers"
config WMT_SOCINFO
bool "VIA/WonderMedia SoC Information driver"
default ARCH_VT8500
select SOC_BUS
help
Say yes to support decoding of VIA/WonderMedia system configuration
register information. This currently includes just the chip ID register
which helps identify the exact hardware revision of the SoC the kernel
is running on (to know if any revision-specific quirks are required)
endmenu
endif
Annotation
- Atlas domain: Driver Families / drivers/soc.
- 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.