drivers/soc/litex/Kconfig
Source file repositories/reference/linux-study-clean/drivers/soc/litex/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/soc/litex/Kconfig- Extension
[no extension]- Size
- 457 bytes
- Lines
- 21
- 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
menu "Enable LiteX SoC Builder specific drivers"
config LITEX
bool
config LITEX_SOC_CONTROLLER
tristate "Enable LiteX SoC Controller driver"
depends on OF
depends on HAS_IOMEM
select LITEX
help
This option enables the SoC Controller Driver which verifies
LiteX CSR access and provides common litex_[read|write]*
accessors.
All drivers that use functions from litex.h must depend on
LITEX.
endmenu
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.