[Skiboot] [RFC PATCH 22/23] doc/device-tree/ibm, opal: rename .txt to .rst
Stewart Smith
stewart at linux.vnet.ibm.com
Wed Jul 27 17:43:23 AEST 2016
Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>
---
doc/device-tree/ibm,opal/diagnostics.rst | 10 ++++
doc/device-tree/ibm,opal/diagnostics.txt | 10 ----
doc/device-tree/ibm,opal/firmware.rst | 30 ++++++++++
doc/device-tree/ibm,opal/firmware.txt | 30 ----------
doc/device-tree/ibm,opal/flash.rst | 35 ++++++++++++
doc/device-tree/ibm,opal/flash.txt | 35 ------------
doc/device-tree/ibm,opal/led.rst | 33 +++++++++++
doc/device-tree/ibm,opal/led.txt | 33 -----------
doc/device-tree/ibm,opal/oppanel.rst | 21 +++++++
doc/device-tree/ibm,opal/oppanel.txt | 21 -------
doc/device-tree/ibm,opal/power-mgt.rst | 96 ++++++++++++++++++++++++++++++++
doc/device-tree/ibm,opal/power-mgt.txt | 96 --------------------------------
doc/device-tree/ibm,opal/sensors.rst | 93 +++++++++++++++++++++++++++++++
doc/device-tree/ibm,opal/sensors.txt | 93 -------------------------------
14 files changed, 318 insertions(+), 318 deletions(-)
create mode 100644 doc/device-tree/ibm,opal/diagnostics.rst
delete mode 100644 doc/device-tree/ibm,opal/diagnostics.txt
create mode 100644 doc/device-tree/ibm,opal/firmware.rst
delete mode 100644 doc/device-tree/ibm,opal/firmware.txt
create mode 100644 doc/device-tree/ibm,opal/flash.rst
delete mode 100644 doc/device-tree/ibm,opal/flash.txt
create mode 100644 doc/device-tree/ibm,opal/led.rst
delete mode 100644 doc/device-tree/ibm,opal/led.txt
create mode 100644 doc/device-tree/ibm,opal/oppanel.rst
delete mode 100644 doc/device-tree/ibm,opal/oppanel.txt
create mode 100644 doc/device-tree/ibm,opal/power-mgt.rst
delete mode 100644 doc/device-tree/ibm,opal/power-mgt.txt
create mode 100644 doc/device-tree/ibm,opal/sensors.rst
delete mode 100644 doc/device-tree/ibm,opal/sensors.txt
diff --git a/doc/device-tree/ibm,opal/diagnostics.rst b/doc/device-tree/ibm,opal/diagnostics.rst
new file mode 100644
index 0000000..14da91c
--- /dev/null
+++ b/doc/device-tree/ibm,opal/diagnostics.rst
@@ -0,0 +1,10 @@
+
+ibm,opal/diagnostics device tree entries
+----------------------------------
+
+The diagnostics node under ibm,opal describes a userspace-to-firmware
+interface, supporting the runtime processor recovery diagnostics functions.
+
+The properties of a prd node are:
+
+ compatible = "ibm,opal-prd"
diff --git a/doc/device-tree/ibm,opal/diagnostics.txt b/doc/device-tree/ibm,opal/diagnostics.txt
deleted file mode 100644
index 14da91c..0000000
--- a/doc/device-tree/ibm,opal/diagnostics.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-
-ibm,opal/diagnostics device tree entries
-----------------------------------
-
-The diagnostics node under ibm,opal describes a userspace-to-firmware
-interface, supporting the runtime processor recovery diagnostics functions.
-
-The properties of a prd node are:
-
- compatible = "ibm,opal-prd"
diff --git a/doc/device-tree/ibm,opal/firmware.rst b/doc/device-tree/ibm,opal/firmware.rst
new file mode 100644
index 0000000..3376fba
--- /dev/null
+++ b/doc/device-tree/ibm,opal/firmware.rst
@@ -0,0 +1,30 @@
+System Firmware
+---------------
+
+The 'firmware' node under 'ibm,opal' lists system and OPAL firmware version.
+
+firmware {
+ symbol-map = <0x0 0x300ac650 0x0 0x1b3f5>;
+ compatible = "ibm,opal-firmware";
+ ml-version = [4d 4c 20 46 57 37 37 30 2e 32 30 20 46 57 37 37 30 2e 32 30 20 46 57 37 37 30 2e 32 30];
+ mi-version = <0x4d49205a 0x4c373730 0x5f303735 0x205a4c37 0x37305f30 0x3735205a 0x4c373730 0x5f303735>;
+ version = "skiboot-5.0-rc2";
+ phandle = <0x8e>;
+ linux,phandle = <0x8e>;
+};
+
+'compatible' property describes OPAL compatibility.
+
+'symbol-map' property describes OPAL symbol start address and size.
+
+'version' property describes OPAL version. Replaces 'git-id', so may
+not be present. On POWER9 and above, it is always present.
+
+'mi-version' property describes Microcode Image. Only on IBM FSP systems.
+Will (likely) not be present on POWER9 systems.
+
+'ml-version' property describes Microcode Level. Only on IBM FSP systems.
+Will (likely) not be present on POWER9 systems.
+
+MI/ML format:
+ <ML/MI> <T side version> <P side version> <boot side version>
diff --git a/doc/device-tree/ibm,opal/firmware.txt b/doc/device-tree/ibm,opal/firmware.txt
deleted file mode 100644
index 3376fba..0000000
--- a/doc/device-tree/ibm,opal/firmware.txt
+++ /dev/null
@@ -1,30 +0,0 @@
-System Firmware
----------------
-
-The 'firmware' node under 'ibm,opal' lists system and OPAL firmware version.
-
-firmware {
- symbol-map = <0x0 0x300ac650 0x0 0x1b3f5>;
- compatible = "ibm,opal-firmware";
- ml-version = [4d 4c 20 46 57 37 37 30 2e 32 30 20 46 57 37 37 30 2e 32 30 20 46 57 37 37 30 2e 32 30];
- mi-version = <0x4d49205a 0x4c373730 0x5f303735 0x205a4c37 0x37305f30 0x3735205a 0x4c373730 0x5f303735>;
- version = "skiboot-5.0-rc2";
- phandle = <0x8e>;
- linux,phandle = <0x8e>;
-};
-
-'compatible' property describes OPAL compatibility.
-
-'symbol-map' property describes OPAL symbol start address and size.
-
-'version' property describes OPAL version. Replaces 'git-id', so may
-not be present. On POWER9 and above, it is always present.
-
-'mi-version' property describes Microcode Image. Only on IBM FSP systems.
-Will (likely) not be present on POWER9 systems.
-
-'ml-version' property describes Microcode Level. Only on IBM FSP systems.
-Will (likely) not be present on POWER9 systems.
-
-MI/ML format:
- <ML/MI> <T side version> <P side version> <boot side version>
diff --git a/doc/device-tree/ibm,opal/flash.rst b/doc/device-tree/ibm,opal/flash.rst
new file mode 100644
index 0000000..872d623
--- /dev/null
+++ b/doc/device-tree/ibm,opal/flash.rst
@@ -0,0 +1,35 @@
+ibm,opal/flash device tree entries
+----------------------------------
+
+The flash@<n> nodes under ibm,opal describe flash devices that can be
+accessed through the OPAL_FLASH_{READ,ERASE,WRITE} interface.
+
+These interfaces take an 'id' parameter, which corresponds to the ibm,opal-id
+property of the node.
+
+The properties under a flash node are:
+
+ compatible = "ibm,opal-flash"
+
+ ibm,opal-id = <id>
+ - provides the index used for the OPAL_FLASH_ calls to reference this
+ flash device
+
+ reg = <0 size>
+ - the offset and size of the flash device
+
+ ibm,flash-block-size
+ - the read/write/erase block size for the flash interface. Calls
+ to read/write/erase must be aligned to the block size.
+
+ #address-cells = <1>
+ #size-cells = <1>
+ - flash devices are currently 32-bit addressable
+
+
+If valid partitions are found on the flash device, then partition@<offset>
+sub-nodes are added to the flash node. These match the Linux binding for
+flash partitions; the reg parameter contains the offset and size of the
+partition.
+
+
diff --git a/doc/device-tree/ibm,opal/flash.txt b/doc/device-tree/ibm,opal/flash.txt
deleted file mode 100644
index 872d623..0000000
--- a/doc/device-tree/ibm,opal/flash.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-ibm,opal/flash device tree entries
-----------------------------------
-
-The flash@<n> nodes under ibm,opal describe flash devices that can be
-accessed through the OPAL_FLASH_{READ,ERASE,WRITE} interface.
-
-These interfaces take an 'id' parameter, which corresponds to the ibm,opal-id
-property of the node.
-
-The properties under a flash node are:
-
- compatible = "ibm,opal-flash"
-
- ibm,opal-id = <id>
- - provides the index used for the OPAL_FLASH_ calls to reference this
- flash device
-
- reg = <0 size>
- - the offset and size of the flash device
-
- ibm,flash-block-size
- - the read/write/erase block size for the flash interface. Calls
- to read/write/erase must be aligned to the block size.
-
- #address-cells = <1>
- #size-cells = <1>
- - flash devices are currently 32-bit addressable
-
-
-If valid partitions are found on the flash device, then partition@<offset>
-sub-nodes are added to the flash node. These match the Linux binding for
-flash partitions; the reg parameter contains the offset and size of the
-partition.
-
-
diff --git a/doc/device-tree/ibm,opal/led.rst b/doc/device-tree/ibm,opal/led.rst
new file mode 100644
index 0000000..5e48b85
--- /dev/null
+++ b/doc/device-tree/ibm,opal/led.rst
@@ -0,0 +1,33 @@
+Service Indicators (LEDS)
+-------------------------
+
+The 'leds' node under 'ibm,opal' lists service indicators available in the
+system and their capabilities.
+
+leds {
+ compatible = "ibm,opal-v3-led";
+ phandle = <0x1000006b>;
+ linux,phandle = <0x1000006b>;
+ led-mode = "lightpath";
+
+ U78C9.001.RST0027-P1-C1 {
+ led-types = "identify", "fault";
+ phandle = <0x1000006f>;
+ linux,phandle = <0x1000006f>;
+ };
+ ...
+ ...
+};
+
+'compatible' property describes LEDs compatibility.
+
+'led-mode' property describes service indicator mode (lightpath/guidinglight).
+
+Each node under 'leds' node describes location code of FRU/Enclosure.
+
+The properties under each node:
+
+ led-types : Supported indicators (attention/identify/fault).
+
+These LEDs can be accessed through OPAL_LEDS_{GET/SET}_INDICATOR interfaces.
+Refer to doc/opal-api/opal-led-get-set-114-115.txt for interface details.
diff --git a/doc/device-tree/ibm,opal/led.txt b/doc/device-tree/ibm,opal/led.txt
deleted file mode 100644
index 5e48b85..0000000
--- a/doc/device-tree/ibm,opal/led.txt
+++ /dev/null
@@ -1,33 +0,0 @@
-Service Indicators (LEDS)
--------------------------
-
-The 'leds' node under 'ibm,opal' lists service indicators available in the
-system and their capabilities.
-
-leds {
- compatible = "ibm,opal-v3-led";
- phandle = <0x1000006b>;
- linux,phandle = <0x1000006b>;
- led-mode = "lightpath";
-
- U78C9.001.RST0027-P1-C1 {
- led-types = "identify", "fault";
- phandle = <0x1000006f>;
- linux,phandle = <0x1000006f>;
- };
- ...
- ...
-};
-
-'compatible' property describes LEDs compatibility.
-
-'led-mode' property describes service indicator mode (lightpath/guidinglight).
-
-Each node under 'leds' node describes location code of FRU/Enclosure.
-
-The properties under each node:
-
- led-types : Supported indicators (attention/identify/fault).
-
-These LEDs can be accessed through OPAL_LEDS_{GET/SET}_INDICATOR interfaces.
-Refer to doc/opal-api/opal-led-get-set-114-115.txt for interface details.
diff --git a/doc/device-tree/ibm,opal/oppanel.rst b/doc/device-tree/ibm,opal/oppanel.rst
new file mode 100644
index 0000000..74a4d09
--- /dev/null
+++ b/doc/device-tree/ibm,opal/oppanel.rst
@@ -0,0 +1,21 @@
+Operator Panel (oppanel)
+------------------------
+
+oppanel {
+ compatible = "ibm,opal-oppanel";
+ #lines = <0x2>;
+ #length = <0x10>;
+};
+
+The Operator Panel is a device for displaying small amounts of textual
+data to an administrator. On IBM POWER8 systems with an FSP, this is a
+small 16x2 LCD panel that can be viewed either from the Web UI of the FSP
+(known as ASM) or by physically going to the machine and looking at the
+panel.
+
+The operator panel does not have to be present.
+
+If it is, there are OPAL calls to read and write to it.
+
+The device tree entry is so that the host OS knows the size of the panel
+and can pass buffers of the appropriate size to the OPAL calls.
diff --git a/doc/device-tree/ibm,opal/oppanel.txt b/doc/device-tree/ibm,opal/oppanel.txt
deleted file mode 100644
index 74a4d09..0000000
--- a/doc/device-tree/ibm,opal/oppanel.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-Operator Panel (oppanel)
-------------------------
-
-oppanel {
- compatible = "ibm,opal-oppanel";
- #lines = <0x2>;
- #length = <0x10>;
-};
-
-The Operator Panel is a device for displaying small amounts of textual
-data to an administrator. On IBM POWER8 systems with an FSP, this is a
-small 16x2 LCD panel that can be viewed either from the Web UI of the FSP
-(known as ASM) or by physically going to the machine and looking at the
-panel.
-
-The operator panel does not have to be present.
-
-If it is, there are OPAL calls to read and write to it.
-
-The device tree entry is so that the host OS knows the size of the panel
-and can pass buffers of the appropriate size to the OPAL calls.
diff --git a/doc/device-tree/ibm,opal/power-mgt.rst b/doc/device-tree/ibm,opal/power-mgt.rst
new file mode 100644
index 0000000..ca3487d
--- /dev/null
+++ b/doc/device-tree/ibm,opal/power-mgt.rst
@@ -0,0 +1,96 @@
+ibm,opal/power-mgt device tree entries
+--------------------------------------
+
+All available CPU idle states are listed in ibm,cpu-idle-state-names
+
+For example:
+ibm,cpu-idle-state-names = "nap", "fastsleep_", "winkle";
+
+The idle states are characterized by latency and residency
+numbers which determine the breakeven point for entry into them. The
+latency is a measure of the exit overhead from the idle state and
+residency is the minimum amount of time that a CPU must be predicted
+to be idle so as to reap the powersavings from entering into that idle
+state.
+
+These numbers are made use of by the cpuidle governors in the kernel to
+arrive at the appropriate idle state that a CPU must enter into when there is
+no work to be done. The values in ibm,cpu-idle-state-latencies-ns are the
+the measured latency numbers for the idle states. The residency numbers have
+been arrived at experimentally after ensuring that the performance of latency
+sensitive workloads do not regress while allowing deeper idle states to be
+entered into during low load situations. The kernel is expected to use these
+values for optimal power efficiency.
+
+ibm,cpu-idle-state-residency-ns = <0x1 0x2 0x3>
+ibm,cpu-idle-state-latencies-ns = <0x1 0x2 0x3>
+
+
+ibm,cpu-idle-state-pmicr ibm,cpu-idle-state-pmicr-mask
+------------------------------------------------------
+In POWER8, idle states sleep and winkle have 2 modes- fast and deep. In fast
+mode, idle state puts the core into threshold voltage whereas deep mode
+completely turns off the core. Choosing fast vs deep mode for an idle state
+can be done either via PM_GP1 scom or by writing to PMICR special register.
+If using the PMICR path to choose fast/deep mode then ibm,cpu-idle-state-pmicr
+and ibm,cpu-idle-state-pmicr-mask properties expose relevant PMICR bits and
+values for corresponding idle states.
+
+
+ibm,cpu-idle-state-psscr ibm,cpu-idle-state-psscr-mask
+------------------------------------------------------
+In POWER ISA v3, there is a common instruction 'stop' to enter any idle state
+and SPR PSSCR is used to specify which idle state needs to be entered upon
+executing stop instruction. Properties ibm,cpu-idle-state-psscr and
+ibm,cpu-idle-state-psscr-mask expose the relevant PSSCR bits and values for
+corresponding idle states.
+
+
+ibm,cpu-idle-state-flags
+------------------------
+These flags are used to describe the characteristics of the idle states like
+the kind of core state loss caused. These flags are used by the kernel to
+save/restore appropriate context while using the idle states.
+
+
+ibm,pstate-ids
+--------------
+
+This property lists the available pstate identifiers, as signed 32-bit
+big-endian values. While the identifiers are somewhat arbitrary, these define
+the order of the pstates in other ibm,pstate-* properties.
+
+
+ibm,pstate-frequencies-mhz
+--------------------------
+
+This property lists the frequency, in MHz, of each of the pstates listed in the
+ibm,pstate-ids file. Each frequency is a 32-bit big-endian word.
+
+
+ibm,pstate-max ibm,pstate-min ibm,pstate-nominal
+------------------------------------------------
+
+These properties give the maximum, minimum and nominal pstate values, as an id
+specified in the ibm,pstate-ids file.
+
+
+ibm,pstate-vcss ibm,pstate-vdds
+-------------------------------
+
+These properties list a voltage-identifier of each of the pstates listed in
+ibm,pstate-ids for the Vcs and Vdd values used for that pstate. Each VID is a
+single byte.
+
+ibm,pstate-ultra-turbo ibm,pstate-turbo
+---------------------------------------
+
+These properties are added when ultra-turbo(WOF) is enabled. These properties
+give the max turbo and max ultra-turbo pstate.
+
+ibm,pstate-core-max
+-------------------
+
+This property is added when ultra_turbo(WOF) is enabled. This property gives
+the list of max pstate for each 'n' number of active cores in the chip.
+
diff --git a/doc/device-tree/ibm,opal/power-mgt.txt b/doc/device-tree/ibm,opal/power-mgt.txt
deleted file mode 100644
index ca3487d..0000000
--- a/doc/device-tree/ibm,opal/power-mgt.txt
+++ /dev/null
@@ -1,96 +0,0 @@
-ibm,opal/power-mgt device tree entries
---------------------------------------
-
-All available CPU idle states are listed in ibm,cpu-idle-state-names
-
-For example:
-ibm,cpu-idle-state-names = "nap", "fastsleep_", "winkle";
-
-The idle states are characterized by latency and residency
-numbers which determine the breakeven point for entry into them. The
-latency is a measure of the exit overhead from the idle state and
-residency is the minimum amount of time that a CPU must be predicted
-to be idle so as to reap the powersavings from entering into that idle
-state.
-
-These numbers are made use of by the cpuidle governors in the kernel to
-arrive at the appropriate idle state that a CPU must enter into when there is
-no work to be done. The values in ibm,cpu-idle-state-latencies-ns are the
-the measured latency numbers for the idle states. The residency numbers have
-been arrived at experimentally after ensuring that the performance of latency
-sensitive workloads do not regress while allowing deeper idle states to be
-entered into during low load situations. The kernel is expected to use these
-values for optimal power efficiency.
-
-ibm,cpu-idle-state-residency-ns = <0x1 0x2 0x3>
-ibm,cpu-idle-state-latencies-ns = <0x1 0x2 0x3>
-
-
-ibm,cpu-idle-state-pmicr ibm,cpu-idle-state-pmicr-mask
-------------------------------------------------------
-In POWER8, idle states sleep and winkle have 2 modes- fast and deep. In fast
-mode, idle state puts the core into threshold voltage whereas deep mode
-completely turns off the core. Choosing fast vs deep mode for an idle state
-can be done either via PM_GP1 scom or by writing to PMICR special register.
-If using the PMICR path to choose fast/deep mode then ibm,cpu-idle-state-pmicr
-and ibm,cpu-idle-state-pmicr-mask properties expose relevant PMICR bits and
-values for corresponding idle states.
-
-
-ibm,cpu-idle-state-psscr ibm,cpu-idle-state-psscr-mask
-------------------------------------------------------
-In POWER ISA v3, there is a common instruction 'stop' to enter any idle state
-and SPR PSSCR is used to specify which idle state needs to be entered upon
-executing stop instruction. Properties ibm,cpu-idle-state-psscr and
-ibm,cpu-idle-state-psscr-mask expose the relevant PSSCR bits and values for
-corresponding idle states.
-
-
-ibm,cpu-idle-state-flags
-------------------------
-These flags are used to describe the characteristics of the idle states like
-the kind of core state loss caused. These flags are used by the kernel to
-save/restore appropriate context while using the idle states.
-
-
-ibm,pstate-ids
---------------
-
-This property lists the available pstate identifiers, as signed 32-bit
-big-endian values. While the identifiers are somewhat arbitrary, these define
-the order of the pstates in other ibm,pstate-* properties.
-
-
-ibm,pstate-frequencies-mhz
---------------------------
-
-This property lists the frequency, in MHz, of each of the pstates listed in the
-ibm,pstate-ids file. Each frequency is a 32-bit big-endian word.
-
-
-ibm,pstate-max ibm,pstate-min ibm,pstate-nominal
-------------------------------------------------
-
-These properties give the maximum, minimum and nominal pstate values, as an id
-specified in the ibm,pstate-ids file.
-
-
-ibm,pstate-vcss ibm,pstate-vdds
--------------------------------
-
-These properties list a voltage-identifier of each of the pstates listed in
-ibm,pstate-ids for the Vcs and Vdd values used for that pstate. Each VID is a
-single byte.
-
-ibm,pstate-ultra-turbo ibm,pstate-turbo
----------------------------------------
-
-These properties are added when ultra-turbo(WOF) is enabled. These properties
-give the max turbo and max ultra-turbo pstate.
-
-ibm,pstate-core-max
--------------------
-
-This property is added when ultra_turbo(WOF) is enabled. This property gives
-the list of max pstate for each 'n' number of active cores in the chip.
-
diff --git a/doc/device-tree/ibm,opal/sensors.rst b/doc/device-tree/ibm,opal/sensors.rst
new file mode 100644
index 0000000..80a6d81
--- /dev/null
+++ b/doc/device-tree/ibm,opal/sensors.rst
@@ -0,0 +1,93 @@
+ibm,opal/sensors/ device tree nodes
+--------------------------------------
+
+All sensors of a POWER8 system are made available to the OS in the
+ibm,opal/sensors/ directory. Each sensor is identified with a node
+which name follows this pattern :
+
+ <resource class name>@<resource identifier>/
+
+For example :
+
+ core-temp at 20/
+
+Each node has a minimum set of properties describing the sensor :
+
+ - a "compatible" property which should be "ibm,opal-sensor"
+
+ - a "sensor-type" property, which can be "temp", "fan", "power".
+ More will be added when new resources are supported. This type
+ is used "as is" by the Linux driver to map sensors in the sysfs
+ interface of the hwmon framework of Linux.
+
+ - a "sensor-data" property giving a unique handler for the
+ OPAL_SENSOR_READ call to be used by Linux to get the value of
+ a sensor attribute. A sensor handler has the following encoding :
+
+ | Attr. | Res. | Resource |
+ | Number | Class | Id |
+ |--------|--------|----------------|
+
+ - a "sensor-status" property giving the state of the sensor. The
+ status bits have the slightly meanings depending on the resource
+ type but testing against 0x6 should raise an alarm.
+
+ - an optional "label" property
+
+
+Each node can have some extra properties depending on the resource
+they represent. See the tree below for more information.
+
+ibm,opal/sensors/ {
+
+ /*
+ * Core temperatures (DTS) nodes.
+ *
+ * We use the PIR of the core as a resource identifier.
+ */
+ core-temp at 20 {
+ compatible = "ibm,opal-sensor";
+ name = "core-temp";
+ sensor-type = "temp";
+
+ /* Status bits :
+ *
+ * 0x0003 FATAL
+ * 0x0002 CRITICAL
+ * 0x0001 WARNING
+ */
+ sensor-data = <0x00800020>;
+
+ /*
+ * These are extra properties to help Linux output.
+ */
+ ibm,pir = <0x20>;
+ label = "Core";
+ };
+
+ /*
+ * Centaur temperatures (DTS) nodes. Open Power only.
+ *
+ * We use the PIR of the core as a resource identifier.
+ */
+ mem-temp at 1 {
+ compatible = "ibm,opal-sensor";
+ name = "mem-temp";
+ sensor-type = "temp";
+
+ /* Status bits :
+ *
+ * 0x0003 FATAL
+ * 0x0002 CRITICAL
+ * 0x0001 WARNING
+ */
+ sensor-data = <0x00810001>;
+
+ /*
+ * These are extra properties to help Linux output.
+ */
+ ibm,chip-id = <0x80000001>;
+ label = "Centaur";
+ };
+
+};
diff --git a/doc/device-tree/ibm,opal/sensors.txt b/doc/device-tree/ibm,opal/sensors.txt
deleted file mode 100644
index 80a6d81..0000000
--- a/doc/device-tree/ibm,opal/sensors.txt
+++ /dev/null
@@ -1,93 +0,0 @@
-ibm,opal/sensors/ device tree nodes
---------------------------------------
-
-All sensors of a POWER8 system are made available to the OS in the
-ibm,opal/sensors/ directory. Each sensor is identified with a node
-which name follows this pattern :
-
- <resource class name>@<resource identifier>/
-
-For example :
-
- core-temp at 20/
-
-Each node has a minimum set of properties describing the sensor :
-
- - a "compatible" property which should be "ibm,opal-sensor"
-
- - a "sensor-type" property, which can be "temp", "fan", "power".
- More will be added when new resources are supported. This type
- is used "as is" by the Linux driver to map sensors in the sysfs
- interface of the hwmon framework of Linux.
-
- - a "sensor-data" property giving a unique handler for the
- OPAL_SENSOR_READ call to be used by Linux to get the value of
- a sensor attribute. A sensor handler has the following encoding :
-
- | Attr. | Res. | Resource |
- | Number | Class | Id |
- |--------|--------|----------------|
-
- - a "sensor-status" property giving the state of the sensor. The
- status bits have the slightly meanings depending on the resource
- type but testing against 0x6 should raise an alarm.
-
- - an optional "label" property
-
-
-Each node can have some extra properties depending on the resource
-they represent. See the tree below for more information.
-
-ibm,opal/sensors/ {
-
- /*
- * Core temperatures (DTS) nodes.
- *
- * We use the PIR of the core as a resource identifier.
- */
- core-temp at 20 {
- compatible = "ibm,opal-sensor";
- name = "core-temp";
- sensor-type = "temp";
-
- /* Status bits :
- *
- * 0x0003 FATAL
- * 0x0002 CRITICAL
- * 0x0001 WARNING
- */
- sensor-data = <0x00800020>;
-
- /*
- * These are extra properties to help Linux output.
- */
- ibm,pir = <0x20>;
- label = "Core";
- };
-
- /*
- * Centaur temperatures (DTS) nodes. Open Power only.
- *
- * We use the PIR of the core as a resource identifier.
- */
- mem-temp at 1 {
- compatible = "ibm,opal-sensor";
- name = "mem-temp";
- sensor-type = "temp";
-
- /* Status bits :
- *
- * 0x0003 FATAL
- * 0x0002 CRITICAL
- * 0x0001 WARNING
- */
- sensor-data = <0x00810001>;
-
- /*
- * These are extra properties to help Linux output.
- */
- ibm,chip-id = <0x80000001>;
- label = "Centaur";
- };
-
-};
--
2.7.4
More information about the Skiboot
mailing list