drivers/thermal/st/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/thermal/st/Kconfig

Extension

[no extension]

Size

792 bytes

Lines

24

Domain

Driver Families

Bucket

drivers/thermal

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
#
# STMicroelectronics thermal drivers configuration
#

config ST_THERMAL
	tristate "Thermal sensors on STMicroelectronics STi series of SoCs"
	help
	  Support for thermal sensors on STMicroelectronics STi series of SoCs.

config ST_THERMAL_MEMMAP
	select ST_THERMAL
	tristate "STi series memory mapped access based thermal sensors"

config STM32_THERMAL
	tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs"
	depends on MACH_STM32MP157
	default y
	help
	  Support for thermal framework on STMicroelectronics STM32 series of
	  SoCs. This thermal driver allows to access to general thermal framework
	  functionalities and to access to SoC sensor functionalities. This
	  configuration is fully dependent of MACH_STM32MP157.

Annotation

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