arch/mips/lantiq/Kconfig
Source file repositories/reference/linux-study-clean/arch/mips/lantiq/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/lantiq/Kconfig- Extension
[no extension]- Size
- 935 bytes
- Lines
- 56
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: build/configuration rule
- Status
- atlas-only
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
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
if LANTIQ
config SOC_TYPE_XWAY
bool
select PINCTRL_XWAY
default n
choice
prompt "SoC Type"
default SOC_XWAY
config SOC_AMAZON_SE
bool "Amazon SE"
select SOC_TYPE_XWAY
select MFD_SYSCON
select MFD_CORE
config SOC_XWAY
bool "XWAY"
select SOC_TYPE_XWAY
select HAVE_PCI
select MFD_SYSCON
select MFD_CORE
config SOC_FALCON
bool "FALCON"
select PINCTRL_FALCON
endchoice
choice
prompt "Built-in device tree"
help
Legacy bootloaders do not pass a DTB pointer to the kernel, so
if a "wrapper" is not being used, the kernel will need to include
a device tree that matches the target board.
The builtin DTB will only be used if the firmware does not supply
a valid DTB.
config LANTIQ_DT_NONE
bool "None"
config DT_EASY50712
bool "Easy50712"
depends on SOC_XWAY
select BUILTIN_DTB
endchoice
config PCI_LANTIQ
bool "PCI Support"
depends on SOC_XWAY && PCI
endif
Annotation
- Atlas domain: Architecture Layer / arch/mips.
- 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.