summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPatrick Venture <venture@google.com>2017-05-22 12:52:26 -0700
committerPatrick Venture <venture@google.com>2017-05-23 09:12:40 -0700
commitb91c244f419f543bdaa31611f92cbee7a34f5fc6 (patch)
tree7cda36dc194b6df74cd5e521da8ef7fd2fd1c872
parent0772bd824bb7477ab65e7c6343d624c5f59d8109 (diff)
downloadopenbmc-docs-b91c244f419f543bdaa31611f92cbee7a34f5fc6.tar.gz
openbmc-docs-b91c244f419f543bdaa31611f92cbee7a34f5fc6.zip
Update sensor configuration documentation.
Change-Id: If2fcbb26670065a769d1463e4080f36093622e64 Signed-off-by: Patrick Venture <venture@google.com>
-rw-r--r--sensor-architecture.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/sensor-architecture.md b/sensor-architecture.md
index 9c139b7..980f979 100644
--- a/sensor-architecture.md
+++ b/sensor-architecture.md
@@ -189,6 +189,15 @@ WARNHI_temp2=80000
With that level of system information, the sensor infrastructure code can
provide all needed D-Bus properties.
+Optionally you can provide an interval value in microseconds for a sensor
+configuration file:
+
+```
+INTERVAL=1000000
+```
+
+This configures how often the sensors listed in this configuration should be
+read.
#### My sensors are defined in an MRW ####
OpenPOWER on IntegriCloud