3 files changed, 52 insertions, 1 deletions

diff --git a/Documentation/ABI/stable/sysfs-class-backlight b/Documentation/ABI/stable/sysfs-class-backlight
index 4d637e1c4ff7..70302f370e7e 100644
--- a/Documentation/ABI/stable/sysfs-class-backlight
+++ b/Documentation/ABI/stable/sysfs-class-backlight
@@ -34,3 +34,23 @@ Contact:	Richard Purdie <rpurdie@rpsys.net>
 Description:
                 Maximum brightness for <backlight>.
 Users:          HAL
+
+What:           /sys/class/backlight/<backlight>/type
+Date:           September 2010
+KernelVersion:  2.6.37
+Contact:        Matthew Garrett <mjg@redhat.com>
+Description:
+                The type of interface controlled by <backlight>.
+                "firmware": The driver uses a standard firmware interface
+                "platform": The driver uses a platform-specific interface
+                "raw": The driver controls hardware registers directly
+
+                In the general case, when multiple backlight
+                interfaces are available for a single device, firmware
+                control should be preferred to platform control should
+                be preferred to raw control. Using a firmware
+                interface reduces the probability of confusion with
+                the hardware and the OS independently updating the
+                backlight state. Platform interfaces are mostly a
+                holdover from pre-standardisation of firmware
+                interfaces.
diff --git a/Documentation/ABI/testing/configfs-spear-pcie-gadget b/Documentation/ABI/testing/configfs-spear-pcie-gadget
new file mode 100644
index 000000000000..875988146a63
--- /dev/null
+++ b/Documentation/ABI/testing/configfs-spear-pcie-gadget
@@ -0,0 +1,31 @@
+What:           /config/pcie-gadget
+Date:           Feb 2011
+KernelVersion:  2.6.37
+Contact:        Pratyush Anand <pratyush.anand@st.com>
+Description:
+
+        Interface is used to configure selected dual mode PCIe controller
+        as device and then program its various registers to configure it
+        as a particular device type.
+        This interfaces can be used to show spear's PCIe device capability.
+
+        Nodes are only visible when configfs is mounted. To mount configfs
+        in /config directory use:
+        # mount -t configfs none /config/
+
+        For nth PCIe Device Controller
+        /config/pcie-gadget.n/
+                link ... used to enable ltssm and read its status.
+                int_type ...used to configure and read type of supported
+                        interrupt
+                no_of_msi ... used to configure number of MSI vector needed and
+                        to read no of MSI granted.
+                inta ... write 1 to assert INTA and 0 to de-assert.
+                send_msi ... write MSI vector to be sent.
+                vendor_id ... used to write and read vendor id (hex)
+                device_id ... used to write and read device id (hex)
+                bar0_size ... used to write and read bar0_size
+                bar0_address ... used to write and read bar0 mapped area in hex.
+                bar0_rw_offset ... used to write and read offset of bar0 where
+                        bar0_data will be written or read.
+                bar0_data ... used to write and read data at bar0_rw_offset.
diff --git a/Documentation/ABI/testing/sysfs-bus-rbd b/Documentation/ABI/testing/sysfs-bus-rbd
index 90a87e2a572b..fa72ccb2282e 100644
--- a/Documentation/ABI/testing/sysfs-bus-rbd
+++ b/Documentation/ABI/testing/sysfs-bus-rbd
@@ -1,6 +1,6 @@
 What:           /sys/bus/rbd/
 Date:           November 2010
-Contact:        Yehuda Sadeh <yehuda@hq.newdream.net>,
+Contact:        Yehuda Sadeh <yehuda@newdream.net>,
                 Sage Weil <sage@newdream.net>
 Description: