drivers/thermal/spacemit/Kconfig

Source file repositories/reference/linux-study-clean/drivers/thermal/spacemit/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/thermal/spacemit/Kconfig
Extension: [no extension]
Size: 651 bytes
Lines: 20
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
menu "SpacemiT thermal drivers"
depends on ARCH_SPACEMIT || COMPILE_TEST

config SPACEMIT_K1_TSENSOR
	tristate "SpacemiT K1 thermal sensor driver"
	depends on THERMAL_OF
	help
	  This driver provides support for the thermal sensor
	  integrated in the SpacemiT K1 SoC.

	  The thermal sensor monitors temperatures for five thermal zones:
	  soc, package, gpu, cluster0, and cluster1. It supports reporting
	  temperature values and handling high/low threshold interrupts.

	  Say Y here if you want to enable thermal monitoring on SpacemiT K1.
	  If compiled as a module, it will be called k1_tsensor.

endmenu

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.