Searched full:occ (Results 1 – 14 of 14) sorted by relevance
| /Documentation/devicetree/bindings/fsi/ |
| D | ibm,p9-occ.yaml | 4 $id: http://devicetree.org/schemas/fsi/ibm,p9-occ.yaml#
7 title: IBM FSI-attached On-Chip Controller (OCC)
13 The POWER processor On-Chip Controller (OCC) helps manage power and
20 - ibm,p9-occ
21 - ibm,p10-occ
25 $ref: /schemas/hwmon/ibm,occ-hwmon.yaml
34 occ {
35 compatible = "ibm,p9-occ";
38 compatible = "ibm,p9-occ-hwmon";
|
| D | ibm,p9-sbefifo.yaml | 27 occ:
29 $ref: ibm,p9-occ.yaml#
43 occ {
44 compatible = "ibm,p9-occ";
|
| /Documentation/hwmon/ |
| D | occ.rst | 1 Kernel driver occ-hwmon
14 This driver supports hardware monitoring for the On-Chip Controller (OCC)
15 embedded on POWER processors. The OCC is a device that collects and aggregates
16 sensor data from the processor and the system. The OCC can provide the raw
20 manually if an "ibm,p8-occ-hwmon" compatible device is found under the
23 The P9 version of this driver is a client driver of the FSI-based OCC driver.
24 It will be probed automatically by the FSI-based OCC driver.
32 The OCC sensor ID is an integer that represents the unique identifier of the
33 sensor with respect to the OCC. For example, a temperature sensor for the third
37 Some entries are only present with certain OCC sensor versions or only on
[all …]
|
| D | ibmpowernv.rst | 45 each OCC. Using this attribute each OCC can be asked to
58 each OCC. Using this attribute each OCC can be asked to
69 each OCC. Using this attribute each OCC can be asked to
80 each OCC. Using this attribute each OCC can be asked to
|
| D | index.rst | 185 occ
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ibm,occ-hwmon.yaml | 4 $id: http://devicetree.org/schemas/hwmon/ibm,occ-hwmon.yaml#
7 title: IBM On-Chip Controller (OCC) accessed from a service processor
13 The POWER processor On-Chip Controller (OCC) helps manage power and
15 controller can query the OCC for it's power and thermal data to report
21 - ibm,p9-occ-hwmon
22 - ibm,p10-occ-hwmon
25 description: This property describes whether or not the OCC should
37 compatible = "ibm,p10-occ-hwmon";
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-platform-devices-occ-hwmon | 1 What: /sys/bus/platform/devices/occ-hwmon.X/ffdc
9 from the first error is saved, until it's cleared upon read. The OCC hwmon driver, running on
|
| D | sysfs-firmware-opal-psr | 18 which is used by OCC for power-capping.
|
| D | sysfs-firmware-opal-sensor-groups | 21 and maximum value of the sensor cached by OCC.
|
| D | sysfs-devices-system-cpu | 459 frequency is throttled due to 'OCC Reset'.
463 the reasons provided by OCC firmware for throttling the frequency.
|
| /Documentation/networking/devlink/ |
| D | devlink-resource.rst | 51 name linear size 98304 occ 0 unit entry size_min 0 size_max 147456 size_gran 128
71 … name linear size 98304 size_new 147456 occ 0 unit entry size_min 0 size_max 147456 size_gran 128
|
| /Documentation/netlink/specs/ |
| D | devlink.yaml | 282 name: sb-occ-cur
285 name: sb-occ-max
470 name: resource-occ
1098 name: resource-occ
1509 name: sb-occ-snapshot
1525 name: sb-occ-max-clear
|
| /Documentation/arch/powerpc/ |
| D | imc.rst | 21 The Nest PMU counters are handled by a Nest IMC microcode which runs in the OCC
|
| /Documentation/devicetree/bindings/ |
| D | trivial-devices.yaml | 121 - ibm,p8-occ-hwmon
|