[Skiboot] [PATCH] doc: clarify locking and async of OPAL_SENSOR_READ

Stewart Smith stewart at linux.vnet.ibm.com
Thu Jun 29 15:53:58 AEST 2017

Reported-by: Robert Lippert <rlippert at google.com>
Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>
 doc/opal-api/opal-sensor-read-88.rst | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/opal-api/opal-sensor-read-88.rst b/doc/opal-api/opal-sensor-read-88.rst
index 932f5726a1d9..6bfc41492bda 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.
@@ -32,7 +35,9 @@ OPAL_PARAMETER
   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.
   a request was sent and an async completion will

More information about the Skiboot mailing list