drivers/firmware/samsung/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/firmware/samsung/Kconfig

Extension

[no extension]

Size

599 bytes

Lines

15

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 EXYNOS_ACPM_PROTOCOL
	tristate "Exynos Alive Clock and Power Manager (ACPM) Message Protocol"
	depends on ARCH_EXYNOS || COMPILE_TEST
	depends on MAILBOX
	help
	  Alive Clock and Power Manager (ACPM) Message Protocol is defined for
	  the purpose of communication between the ACPM firmware and masters
	  (AP, AOC, ...). ACPM firmware operates on the Active Power Management
	  (APM) module that handles overall power activities.

	  This protocol driver provides interface for all the client drivers
	  making use of the features offered by the APM.

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.