drivers/firmware/smccc/Kconfig

Source file repositories/reference/linux-study-clean/drivers/firmware/smccc/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/firmware/smccc/Kconfig
Extension: [no extension]
Size: 810 bytes
Lines: 26
Domain: Driver Families
Bucket: drivers/firmware
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
config HAVE_ARM_SMCCC
	bool
	help
	  Include support for the Secure Monitor Call (SMC) and Hypervisor
	  Call (HVC) instructions on Armv7 and above architectures.

config HAVE_ARM_SMCCC_DISCOVERY
	bool
	depends on ARM_PSCI_FW
	default y
	help
	 SMCCC v1.0 lacked discoverability and hence PSCI v1.0 was updated
	 to add SMCCC discovery mechanism though the PSCI firmware
	 implementation of PSCI_FEATURES(SMCCC_VERSION) which returns
	 success on firmware compliant to SMCCC v1.1 and above.

config ARM_SMCCC_SOC_ID
	bool "SoC bus device for the ARM SMCCC SOC_ID"
	depends on HAVE_ARM_SMCCC_DISCOVERY
	default y
	select SOC_BUS
	help
	  Include support for the SoC bus on the ARM SMCCC firmware based
	  platforms providing some sysfs information about the SoC variant.

Annotation

Atlas domain: Driver Families / drivers/firmware.
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.