Documentation/devicetree/bindings/powerpc/opal/sensor-groups.txt
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/powerpc/opal/sensor-groups.txt
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/powerpc/opal/sensor-groups.txt- Extension
.txt- Size
- 830 bytes
- Lines
- 28
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- 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
IBM OPAL Sensor Groups Binding
-------------------------------
Node: /ibm,opal/sensor-groups
Description: Contains sensor groups available in the Powernv P9
servers. Each child node indicates a sensor group.
- compatible : Should be "ibm,opal-sensor-group"
Each child node contains below properties:
- type : String to indicate the type of sensor-group
- sensor-group-id: Abstract unique identifier provided by firmware of
type <u32> which is used for sensor-group
operations like clearing the min/max history of all
sensors belonging to the group.
- ibm,chip-id : Chip ID
- sensors : Phandle array of child nodes of /ibm,opal/sensor/
belonging to this group
- ops : Array of opal-call numbers indicating available operations on
sensor groups like clearing min/max, enabling/disabling sensor
group.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.