drivers/peci/Kconfig
Source file repositories/reference/linux-study-clean/drivers/peci/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/peci/Kconfig- Extension
[no extension]- Size
- 1124 bytes
- Lines
- 37
- Domain
- Driver Families
- Bucket
- drivers/peci
- 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
menuconfig PECI
tristate "PECI support"
help
The Platform Environment Control Interface (PECI) is an interface
that provides a communication channel to Intel processors and
chipset components from external monitoring or control devices.
If you are building a Baseboard Management Controller (BMC) kernel
for Intel platform say Y here and also to the specific driver for
your adapter(s) below. If unsure say N.
This support is also available as a module. If so, the module
will be called peci.
if PECI
config PECI_CPU
tristate "PECI CPU"
select AUXILIARY_BUS
help
This option enables peci-cpu driver for Intel processors. It is
responsible for creating auxiliary devices that can subsequently
be used by other drivers in order to perform various
functionalities such as e.g. temperature monitoring.
Additional drivers must be enabled in order to use the functionality
of the device.
This driver can also be built as a module. If so, the module
will be called peci-cpu.
source "drivers/peci/controller/Kconfig"
endif # PECI
Annotation
- Atlas domain: Driver Families / drivers/peci.
- 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.