Documentation/devicetree/bindings/peci/peci-controller.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/peci/peci-controller.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/peci/peci-controller.yaml- Extension
.yaml- Size
- 772 bytes
- Lines
- 34
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
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 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/peci/peci-controller.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Generic for PECI
maintainers:
- Iwona Winiarska <iwona.winiarska@intel.com>
description:
PECI (Platform Environment Control Interface) is an interface that provides a
communication channel from Intel processors and chipset components to external
monitoring or control devices.
properties:
$nodename:
pattern: "^peci-controller(@.*)?$"
cmd-timeout-ms:
description:
Command timeout in units of ms.
additionalProperties: true
examples:
- |
peci-controller@1e78b000 {
reg = <0x1e78b000 0x100>;
cmd-timeout-ms = <500>;
};
...
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- 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.