summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPatrick Venture <venture@google.com>2017-12-20 09:08:29 -0800
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-01-30 18:51:17 +0000
commit862ac59a52945ada1a6e641ab625dc18ec614192 (patch)
treefd742c9a790f1d2279e3f3a9e4818c2ee41d62c6
parent6eec723e39e84d0c980ae3db8dba0bbd051151a3 (diff)
downloadphosphor-dbus-interfaces-862ac59a52945ada1a6e641ab625dc18ec614192.zip
phosphor-dbus-interfaces-862ac59a52945ada1a6e641ab625dc18ec614192.tar.gz
Add Control.FanPwm interface
The following reference indicates that pwm[n], when available are consistently implemented. Therefore, it's a valid approach. https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface I'd like to use this interface with phosphor-hwmon to control our fans in a similar fashion to RPM-driven control via a target. Change-Id: Ic1d9363d616e650ba7d5162f424700d6768cdf1f Signed-off-by: Patrick Venture <venture@google.com>
-rw-r--r--xyz/openbmc_project/Control/FanPwm.interface.yaml16
1 files changed, 16 insertions, 0 deletions
diff --git a/xyz/openbmc_project/Control/FanPwm.interface.yaml b/xyz/openbmc_project/Control/FanPwm.interface.yaml
new file mode 100644
index 0000000..0c711db
--- /dev/null
+++ b/xyz/openbmc_project/Control/FanPwm.interface.yaml
@@ -0,0 +1,16 @@
+description: >
+ Implement to provide fan pwm control. The method of control is hardware
+ dependent and objects implementing Control.FanPwm must be instantiated
+ within the sensors/fan_tach namespace.
+
+ Any service implementing Control.FanPwm on one or more objects must
+ implement xyz.openbmc_project.Sensors.Value on the object and
+ org.freedesktop.DBus.ObjectManager on the sensors namespace root.
+
+ All Control.FanPwm properties are read-write.
+
+properties:
+ - name: Target
+ type: uint64
+ description: >
+ The fan pwm target value. 0 - 255
OpenPOWER on IntegriCloud