10 files changed, 175 insertions, 12 deletions

diff --git a/Documentation/ABI/stable/vdso b/Documentation/ABI/stable/vdso
index 8a1cbb594497..7cdfc28cc2c6 100644
--- a/Documentation/ABI/stable/vdso
+++ b/Documentation/ABI/stable/vdso
@@ -24,4 +24,4 @@ though.
 
 (As of this writing, this ABI documentation as been confirmed for x86_64.
  The maintainers of the other vDSO-using architectures should confirm
- that it is correct for their architecture.)
\ No newline at end of file
+ that it is correct for their architecture.)
diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram
index c8b3b48ec62c..ec93fe33baa6 100644
--- a/Documentation/ABI/testing/sysfs-block-zram
+++ b/Documentation/ABI/testing/sysfs-block-zram
@@ -96,4 +96,4 @@ Description:
                 overhead, allocated for this disk. So, allocator space
                 efficiency can be calculated using compr_data_size and this
                 statistic.
-                Unit: bytes
\ No newline at end of file
+                Unit: bytes
diff --git a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
index cb830df8777c..70d00dfa443d 100644
--- a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
+++ b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
@@ -40,4 +40,4 @@ Description:	Controls the decimal places on the device.
                 the value of 10 ** n. Assume this field has
                 the value k and has 1 or more decimal places set,
                 to set the mth place (where m is not already set),
-                change this fields value to k + 10 ** m.
\ No newline at end of file
+                change this fields value to k + 10 ** m.
diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
index 4a9c545bda4b..33e648808117 100644
--- a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
+++ b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
@@ -53,4 +53,4 @@ Description:
                 Documentation/ABI/stable/sysfs-class-backlight.
                 It can be enabled by writing the value stored in
                 /sys/class/backlight/<backlight>/max_brightness to
-                /sys/class/backlight/<backlight>/brightness.
\ No newline at end of file
+                /sys/class/backlight/<backlight>/brightness.
diff --git a/Documentation/ABI/testing/sysfs-class-mtd b/Documentation/ABI/testing/sysfs-class-mtd
index db1ad7e34fc3..938ef71e2035 100644
--- a/Documentation/ABI/testing/sysfs-class-mtd
+++ b/Documentation/ABI/testing/sysfs-class-mtd
@@ -142,13 +142,14 @@ KernelVersion:	3.4
 Contact:        linux-mtd@lists.infradead.org
 Description:
                 This allows the user to examine and adjust the criteria by which
-                mtd returns -EUCLEAN from mtd_read().  If the maximum number of
-                bit errors that were corrected on any single region comprising
-                an ecc step (as reported by the driver) equals or exceeds this
-                value, -EUCLEAN is returned.  Otherwise, absent an error, 0 is
-                returned.  Higher layers (e.g., UBI) use this return code as an
-                indication that an erase block may be degrading and should be
-                scrutinized as a candidate for being marked as bad.
+                mtd returns -EUCLEAN from mtd_read() and mtd_read_oob().  If the
+                maximum number of bit errors that were corrected on any single
+                region comprising an ecc step (as reported by the driver) equals
+                or exceeds this value, -EUCLEAN is returned.  Otherwise, absent
+                an error, 0 is returned.  Higher layers (e.g., UBI) use this
+                return code as an indication that an erase block may be
+                degrading and should be scrutinized as a candidate for being
+                marked as bad.
 
                 The initial value may be specified by the flash device driver.
                 If not, then the default value is ecc_strength.
@@ -167,7 +168,7 @@ Description:
                 block degradation, but high enough to avoid the consequences of
                 a persistent return value of -EUCLEAN on devices where sticky
                 bitflips occur.  Note that if bitflip_threshold exceeds
-                ecc_strength, -EUCLEAN is never returned by mtd_read().
+                ecc_strength, -EUCLEAN is never returned by the read operations.
                 Conversely, if bitflip_threshold is zero, -EUCLEAN is always
                 returned, absent a hard error.
 
diff --git a/Documentation/ABI/testing/sysfs-devices-system-xen_cpu b/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
new file mode 100644
index 000000000000..9ca02fb2d498
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
@@ -0,0 +1,20 @@
+What:           /sys/devices/system/xen_cpu/
+Date:           May 2012
+Contact:        Liu, Jinsong <jinsong.liu@intel.com>
+Description:
+                A collection of global/individual Xen physical cpu attributes
+
+                Individual physical cpu attributes are contained in
+                subdirectories named by the Xen's logical cpu number, e.g.:
+                /sys/devices/system/xen_cpu/xen_cpu#/
+
+
+What:           /sys/devices/system/xen_cpu/xen_cpu#/online
+Date:           May 2012
+Contact:        Liu, Jinsong <jinsong.liu@intel.com>
+Description:
+                Interface to online/offline Xen physical cpus
+
+                When running under Xen platform, it provide user interface
+                to online/offline physical cpus, except cpu0 due to several
+                logic restrictions and assumptions.
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd b/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
new file mode 100644
index 000000000000..57b92cbdceae
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
@@ -0,0 +1,38 @@
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_to_select
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be
+                is being controlled by press_speed.
+                Values are 0 or 1.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.
+                Values are 0 or 1.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    For details regarding this setting please refer to http://www.pc.ibm.com/ww/healthycomputing/trkpntb.html
+                Values are 0 or 1.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/select_right
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate
+                a left or right mouse button click.
+                Values are 0 or 1.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    This file contains the trackpoint sensitivity.
+                Values are decimal integers from 1 (lowest sensitivity) to 255 (highest sensitivity).
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_speed
+Date:           July 2011
+Contact:        linux-input@vger.kernel.org
+Description:    This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.
+                Values are decimal integers from 1 (slowest) to 255 (fastest).
+
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu b/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
new file mode 100644
index 000000000000..b42922cf6b1f
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
@@ -0,0 +1,77 @@
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    The mouse can store 5 profiles which can be switched by the
+                press of a button. A profile is split into general settings and
+                button settings. buttons holds informations about button layout.
+                When written, this file lets one write the respective profile
+                buttons to the mouse. The data has to be 47 bytes long.
+                The mouse will reject invalid data.
+                Which profile to write is determined by the profile number
+                contained in the data.
+                Before reading this file, control has to be written to select
+                which profile to read.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When written, this file lets one select which data from which
+                profile will be read next. The data has to be 3 bytes long.
+                This file is writeonly.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/general
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    The mouse can store 5 profiles which can be switched by the
+                press of a button. A profile is split into general settings and
+                button settings. profile holds informations like resolution, sensitivity
+                and light effects.
+                When written, this file lets one write the respective profile
+                settings back to the mouse. The data has to be 43 bytes long.
+                The mouse will reject invalid data.
+                Which profile to write is determined by the profile number
+                contained in the data.
+                This file is writeonly.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When read, this file returns general data like firmware version.
+                The data is 8 bytes long.
+                This file is readonly.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When written, this file lets one store macros with max 500
+                keystrokes for a specific button for a specific profile.
+                Button and profile numbers are included in written data.
+                The data has to be 2083 bytes long.
+                Before reading this file, control has to be written to select
+                which profile and key to read.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
+Date:           Mai 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    The mouse can store 5 profiles which can be switched by the
+                press of a button. profile holds number of actual profile.
+                This value is persistent, so its value determines the profile
+                that's active when the mouse is powered on next time.
+                When written, the mouse activates the set profile immediately.
+                The data has to be 3 bytes long.
+                The mouse will reject invalid data.
+Users:          http://roccat.sourceforge.net
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/sensor
+Date:           July 2012
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    The mouse has a Avago ADNS-3090 sensor.
+                This file allows reading and writing of the mouse sensors registers.
+                The data has to be 4 bytes long.
+Users:          http://roccat.sourceforge.net
+
diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
new file mode 100644
index 000000000000..9b31556cfdda
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
@@ -0,0 +1,14 @@
+What:           /sys/kernel/iommu_groups/
+Date:           May 2012
+KernelVersion:  v3.5
+Contact:        Alex Williamson <alex.williamson@redhat.com>
+Description:    /sys/kernel/iommu_groups/ contains a number of sub-
+                directories, each representing an IOMMU group.  The
+                name of the sub-directory matches the iommu_group_id()
+                for the group, which is an integer value.  Within each
+                subdirectory is another directory named "devices" with
+                links to the sysfs devices contained in this group.
+                The group directory also optionally contains a "name"
+                file if the IOMMU driver has chosen to register a more
+                common name for the group.
+Users:
diff --git a/Documentation/ABI/testing/sysfs-power b/Documentation/ABI/testing/sysfs-power
index 31725ffeeb3a..217772615d02 100644
--- a/Documentation/ABI/testing/sysfs-power
+++ b/Documentation/ABI/testing/sysfs-power
@@ -231,3 +231,16 @@ Description:
                 Reads from this file return a string consisting of the names of
                 wakeup sources created with the help of /sys/power/wake_lock
                 that are inactive at the moment, separated with spaces.
+
+What:           /sys/power/pm_print_times
+Date:           May 2012
+Contact:        Sameer Nanda <snanda@chromium.org>
+Description:
+                The /sys/power/pm_print_times file allows user space to
+                control whether the time taken by devices to suspend and
+                resume is printed.  These prints are useful for hunting down
+                devices that take too long to suspend or resume.
+
+                Writing a "1" enables this printing while writing a "0"
+                disables it.  The default value is "0".  Reading from this file
+                will display the current value.