diff mbox

[v2,12/13] sensor: add documentation for the OPAL_SENSOR_READ call

Message ID 1424442456-11979-13-git-send-email-clg@fr.ibm.com
State Changes Requested
Headers show

Commit Message

Cédric Le Goater Feb. 20, 2015, 2:27 p.m. UTC 
Signed-off-by: Cédric Le Goater <clg@fr.ibm.com>
---
 doc/opal-api/opal-sensor-read-88.txt |   32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 doc/opal-api/opal-sensor-read-88.txt
diff mbox

Patch

diff --git a/doc/opal-api/opal-sensor-read-88.txt b/doc/opal-api/opal-sensor-read-88.txt
new file mode 100644
index 000000000000..d0b1a08ca5c9
--- /dev/null
+++ b/doc/opal-api/opal-sensor-read-88.txt
@@ -0,0 +1,32 @@ 
+OPAL_SENSOR_READ
+----------------
+
+The OPAL sensor call reads a sensor data using a unique handler to
+identity the targeted sensor.
+
+
+This call can be asynchronous, when a message needs to be sent to a
+service processor for example.  In this case, the call will return
+OPAL_ASYNC_COMPLETION and the token parameter will be used to wait for
+the completion of the request.
+
+
+Parameters:
+	uint32_t sensor_handler
+	int	 token
+	uint32_t *sensor_data
+
+
+Return values:
+	OPAL_SUCCESS
+	OPAL_PARAMETER - invalid sensor handler
+
+in case of communication with the FSP on IBM systems
+
+	OPAL_ASYNC_COMPLETION - a request was sent and an async completion will
+		be triggered with the @token argument
+	OPAL_PARTIAL - the request completed but the data returned is invalid
+	OPAL_BUSY_EVENT - a previous request is still pending
+	OPAL_NO_MEM - allocation failed
+	OPAL_INTERNAL_ERROR - communication failure with the FSP
+	OPAL_HARDWARE - FSP is not available