[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180703070413.28756-3-andrew@aj.id.au>
Date: Tue, 3 Jul 2018 17:04:11 +1000
From: Andrew Jeffery <andrew@...id.au>
To: linux-kernel@...r.kernel.org
Cc: Andrew Jeffery <andrew@...id.au>, robh+dt@...nel.org,
mark.rutland@....com, joel@....id.au, gregkh@...uxfoundation.org,
Eugene.Cho@...l.com, a.amelkin@...ro.com, stewart@...ux.ibm.com,
benh@...nel.crashing.org, openbmc@...ts.ozlabs.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: [RFC PATCH 2/4] Documentation: ABI: Add sysfs-class-bmc documentation to testing
Signed-off-by: Andrew Jeffery <andrew@...id.au>
---
Documentation/ABI/testing/sysfs-class-bmc | 62 +++++++++++++++++++++++
1 file changed, 62 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-class-bmc
diff --git a/Documentation/ABI/testing/sysfs-class-bmc b/Documentation/ABI/testing/sysfs-class-bmc
new file mode 100644
index 000000000000..9d42106b89f9
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-bmc
@@ -0,0 +1,62 @@
+This document defines the sysfs attributes common to the bmc device class. See
+Documentation/devicetree/bindings/misc/bmc-misc-ctrl.txt for exhaustive list of
+field definitions.
+
+What: /sys/class/bmc/<field>/label
+Date: July, 2018
+KernelVersion: v4.19
+Contact: openbmc@...ts.ozlabs.org
+Description:
+ The name of the field of interest. Corresponds to the value of
+ <field> in the path
+Users: openbmc@...ts.ozlabs.org
+
+What: /sys/class/bmc/<field>/value
+Date: July, 2018
+KernelVersion: v4.19
+Contact: openbmc@...ts.ozlabs.org
+Description:
+ The value of the field of interest.
+
+ If the field is exposed from a read-modify-write register this
+ attribute will be RW, where writes will set the field to the
+ value written. Writing values that exceed the width of the
+ field will return an error.
+
+ If the field is exposed from a write-1-set/write-1-clear
+ register this attribute will be RO, and the attributes 'set'
+ and 'clear' will be present as write-only.
+Users: openbmc@...ts.ozlabs.org
+
+What: /sys/class/bmc/<field>/mask
+Date: July, 2018
+KernelVersion: v4.19
+Contact: openbmc@...ts.ozlabs.org
+Description:
+ The mask applied to the value read/written from the 'value'
+ attribute.
+Users: openbmc@...ts.ozlabs.org
+
+What: /sys/class/bmc/<field>/set
+Users: openbmc@...ts.ozlabs.org
+Date: July, 2018
+KernelVersion: v4.19
+Contact: openbmc@...ts.ozlabs.org
+Description:
+ For fields backed by write-1-set/write-1-clear registers,
+ set bits in the value written will be set in hardware. Zero
+ values are ignored. Writing values that exceed the width of the
+ mask value will return an error.
+Users: openbmc@...ts.ozlabs.org
+
+What: /sys/class/bmc/<field>/clear
+Users: openbmc@...ts.ozlabs.org
+Date: July, 2018
+KernelVersion: v4.19
+Contact: openbmc@...ts.ozlabs.org
+Description:
+ For fields backed by write-1-set/write-1-clear registers,
+ set bits in the value written will be cleared in hardware. Zero
+ values are ignored. Writing values that exceed the width of the
+ mask value will return an error.
+Users: openbmc@...ts.ozlabs.org
--
2.17.1
Powered by blists - more mailing lists