arch/arm/mach-zte/Kconfig

Source file repositories/reference/linux-study-clean/arch/arm/mach-zte/Kconfig

File Facts

System: Linux kernel
Corpus path: arch/arm/mach-zte/Kconfig
Extension: [no extension]
Size: 793 bytes
Lines: 30
Domain: Architecture Layer
Bucket: arch/arm
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-only
menuconfig ARCH_ZTE
	bool "ZTE zx family"
	depends on ARCH_MULTI_V7
	help
	  Support for ZTE zx-based family of processors.

if ARCH_ZTE

config SOC_ZX297520V3
	bool "zx297520v3 SoC"
	default y
	select ARM_GIC_V3
	# This board does not have PSCI firmware, but ARM_GIC_V3 depends on
	# ARM_PSCI_FW being enabled.
	select ARM_PSCI_FW
	select ARM_AMBA
	select HAVE_ARM_ARCH_TIMER
	select PM_GENERIC_DOMAINS if PM
	help
	  Support for ZTE zx297520v3 SoC. It is a single core SoC used in cheap
	  LTE to WiFi routers. These devices can be identified by the occurrence
	  of the string "zx297520v3" in the boot output and /proc/cpuinfo of
	  their stock firmware.

	  Please read Documentation/arch/arm/zte/zx297520v3.rst on how to boot
	  the kernel.

endif

Annotation

Atlas domain: Architecture Layer / arch/arm.
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.