Documentation/devicetree/bindings/hwmon/ibm,opal-sensor.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/hwmon/ibm,opal-sensor.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/hwmon/ibm,opal-sensor.yaml- Extension
.yaml- Size
- 852 bytes
- Lines
- 38
- 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/hwmon/ibm,opal-sensor.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: IBM POWERNV platform sensors
maintainers:
- Javier Carrasco <javier.carrasco.cruz@gmail.com>
properties:
compatible:
enum:
- ibm,opal-sensor-cooling-fan
- ibm,opal-sensor-amb-temp
- ibm,opal-sensor-power-supply
- ibm,opal-sensor-power
sensor-id:
description:
An opaque id provided by the firmware to the kernel, identifies a
given sensor and its attribute data.
$ref: /schemas/types.yaml#/definitions/uint32
required:
- compatible
- sensor-id
additionalProperties: false
examples:
- |
sensor {
compatible = "ibm,opal-sensor-cooling-fan";
sensor-id = <0x7052107>;
};
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.