drivers/thermal/tegra/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/thermal/tegra/Kconfig
Extension: [no extension]
Size: 986 bytes
Lines: 29
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 "NVIDIA Tegra thermal drivers"
depends on ARCH_TEGRA || COMPILE_TEST

config TEGRA_SOCTHERM
	tristate "Tegra SOCTHERM thermal management"
	help
	  Enable this option for integrated thermal management support on NVIDIA
	  Tegra systems-on-chip. The driver supports four thermal zones
	  (CPU, GPU, MEM, PLLX). Cooling devices can be bound to the thermal
	  zones to manage temperatures. This option is also required for the
	  emergency thermal reset (thermtrip) feature to function.

config TEGRA_BPMP_THERMAL
	tristate "Tegra BPMP thermal sensing"
	depends on TEGRA_BPMP || COMPILE_TEST
	help
	  Enable this option for support for sensing system temperature of NVIDIA
	  Tegra systems-on-chip with the BPMP coprocessor (Tegra186).

config TEGRA30_TSENSOR
	tristate "Tegra30 Thermal Sensor"
	depends on ARCH_TEGRA_3x_SOC || COMPILE_TEST
	help
	  Enable this option to support thermal management of NVIDIA Tegra30
	  system-on-chip.

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.