summaryrefslogtreecommitdiffstats
path: root/README.iio.md
diff options
context:
space:
mode:
authorBrad Bishop <bradleyb@fuzziesquirrel.com>2017-08-29 13:23:37 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2017-08-31 08:47:01 -0400
commit3eca2520e459cc17be62c20400c385d15a72bff9 (patch)
treee3688cb30a4a17b8659057bed4f64377b25e4637 /README.iio.md
parent116419500fba6ab97b3b9895cd771fd253231ecb (diff)
downloadphosphor-hwmon-3eca2520e459cc17be62c20400c385d15a72bff9.tar.gz
phosphor-hwmon-3eca2520e459cc17be62c20400c385d15a72bff9.zip
Docs: Add IIO device limitation information
Add an IIO devices README to ward off the typical questions about IIO. Change-Id: If126daf1ddf550d9d7bf475b4d68ae2566f72c74 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'README.iio.md')
-rw-r--r--README.iio.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/README.iio.md b/README.iio.md
new file mode 100644
index 0000000..c1b3f7b
--- /dev/null
+++ b/README.iio.md
@@ -0,0 +1,14 @@
+Phosphor OpenBMC and IIO devices
+
+Phosphor OpenBMC currently does not provide an IIO device to DBUS bridge in the
+same way that hwmon devices are bridged by the phosphor-hwmon-readd application.
+
+Until a daemon can be written, the hwmon-iio bridge driver can be used with
+the phosphor-hwmon-readd application, with the limitation that only a single
+iio channel can be configured per iio-hwmon platform instance. Typically
+device trees are setup with all the iio-channels under a single iio-hwmon
+platform device - doing this will result in undefined behavior from
+phosphor-hwmon-readd.
+
+If a true IIO bridging daemon becomes available in the future, phosphor-hwmon-readd
+will not support hwmon-iio bridge devices in any capacity.
OpenPOWER on IntegriCloud