drivers/soc/sophgo/Kconfig
Source file repositories/reference/linux-study-clean/drivers/soc/sophgo/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/soc/sophgo/Kconfig- Extension
[no extension]- Size
- 984 bytes
- Lines
- 35
- 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
#
# Sophgo SoC drivers
#
if ARCH_SOPHGO || COMPILE_TEST
menu "Sophgo SoC drivers"
config SOPHGO_CV1800_RTCSYS
tristate "Sophgo CV1800 RTC MFD"
select MFD_CORE
help
If you say yes here you get support the RTC MFD driver for Sophgo
CV1800 series SoC. The RTC module comprises a 32kHz oscillator,
Power-on-Reset (PoR) sub-module, HW state machine to control chip
power-on, power-off and reset. Furthermore, the 8051 subsystem is
located within RTCSYS including associated SRAM block.
This driver can also be built as a module. If so, the module will be
called cv1800-rtcsys.
config SOPHGO_SG2044_TOPSYS
tristate "Sophgo SG2044 TOP syscon driver"
select MFD_CORE
help
This is the core driver for the Sophgo SG2044 TOP system
controller device. This driver provide PLL clock device
for the SoC.
This driver can also be built as a module. If so, the module
will be called sg2044-topsys.
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.