aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.vnet.ibm.com>2017-06-29 15:53:58 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>2017-10-15 20:08:14 -0500
commit77dbac105a99c705b830410bd991a5fcd6d1ff4f (patch)
treeb37d065d3b547c3e0480904161260ef0ec142c81 /doc
parent4466a6ec89bf39afeb98b92d03bbf7fc30c55afe (diff)
downloadskiboot-77dbac105a99c705b830410bd991a5fcd6d1ff4f.zip
skiboot-77dbac105a99c705b830410bd991a5fcd6d1ff4f.tar.gz
skiboot-77dbac105a99c705b830410bd991a5fcd6d1ff4f.tar.bz2
doc: clarify locking and async of OPAL_SENSOR_READ
Reported-by: Robert Lippert <rlippert@google.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/opal-api/opal-sensor-read-88.rst7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/opal-api/opal-sensor-read-88.rst b/doc/opal-api/opal-sensor-read-88.rst
index 932f572..6bfc414 100644
--- a/doc/opal-api/opal-sensor-read-88.rst
+++ b/doc/opal-api/opal-sensor-read-88.rst
@@ -11,6 +11,9 @@ 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.
+The OPAL API doesn't enforce alimit on the number of sensor calls that can
+be in flight.
+
Parameters
----------
@@ -32,7 +35,9 @@ OPAL_PARAMETER
OPAL_UNSUPPORTED
platform does not support reading sensors.
-In case of communication with the FSP on IBM systems:
+Some sensors may have to be read asynchronously (e.g. because OPAL must
+communicate with a service processor). One example is sensors provided
+by the FSP on IBM FSP systems.
OPAL_ASYNC_COMPLETION
a request was sent and an async completion will