drivers/platform/x86/intel/int1092/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/x86/intel/int1092/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/x86/intel/int1092/Kconfig
Extension: [no extension]
Size: 836 bytes
Lines: 15
Domain: Driver Families
Bucket: drivers/platform
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

config INTEL_SAR_INT1092
	tristate "Intel Specific Absorption Rate Driver"
	depends on ACPI
	help
	  This driver helps to limit the exposure of human body to RF frequency by
	  providing information to userspace application that will inform the Intel
	  M.2 modem to regulate the RF power based on SAR data obtained from the
	  sensors captured in the BIOS. ACPI interface exposes this data from the BIOS
	  to SAR driver. The front end application in userspace will interact with SAR
	  driver to obtain information like the device mode, Antenna index, baseband index,
	  SAR table index and use available communication like MBIM interface to enable
	  data communication to modem for RF power regulation. Enable this config when
	  given platform needs to support "Dynamic SAR" configuration for a modem available
	  on the platform.

Annotation

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