arch/mips/bcm63xx/Kconfig

Source file repositories/reference/linux-study-clean/arch/mips/bcm63xx/Kconfig

File Facts

System: Linux kernel
Corpus path: arch/mips/bcm63xx/Kconfig
Extension: [no extension]
Size: 893 bytes
Lines: 46
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
menu "CPU support"
	depends on BCM63XX

config BCM63XX_CPU_3368
	bool "support 3368 CPU"
	select SYS_HAS_CPU_BMIPS4350
	select HAVE_PCI

config BCM63XX_CPU_6328
	bool "support 6328 CPU"
	select SYS_HAS_CPU_BMIPS4350
	select HAVE_PCI

config BCM63XX_CPU_6338
	bool "support 6338 CPU"
	select SYS_HAS_CPU_BMIPS32_3300
	select HAVE_PCI

config BCM63XX_CPU_6345
	bool "support 6345 CPU"
	select SYS_HAS_CPU_BMIPS32_3300

config BCM63XX_CPU_6348
	bool "support 6348 CPU"
	select SYS_HAS_CPU_BMIPS32_3300
	select HAVE_PCI

config BCM63XX_CPU_6358
	bool "support 6358 CPU"
	select SYS_HAS_CPU_BMIPS4350
	select HAVE_PCI

config BCM63XX_CPU_6362
	bool "support 6362 CPU"
	select SYS_HAS_CPU_BMIPS4350
	select HAVE_PCI

config BCM63XX_CPU_6368
	bool "support 6368 CPU"
	select SYS_HAS_CPU_BMIPS4350
	select HAVE_PCI
endmenu

source "arch/mips/bcm63xx/boards/Kconfig"

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.