5 files changed, 326 insertions, 0 deletions

diff --git a/Documentation/ABI/testing/sysfs-ata b/Documentation/ABI/testing/sysfs-ata
new file mode 100644
index 000000000000..0a932155cbba
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-ata
@@ -0,0 +1,99 @@
+What:           /sys/class/ata_...
+Date:           August 2008
+Contact:        Gwendal Grignou<gwendal@google.com>
+Description:
+
+Provide a place in sysfs for storing the ATA topology of the system.  This allows
+retrieving various information about ATA objects.
+
+Files under /sys/class/ata_port
+-------------------------------
+
+        For each port, a directory ataX is created where X is the ata_port_id of
+        the port. The device parent is the ata host device.
+
+idle_irq (read)
+
+        Number of IRQ received by the port while idle [some ata HBA only].
+
+nr_pmp_links (read)
+
+        If a SATA Port Multiplier (PM) is connected, number of link behind it.
+
+Files under /sys/class/ata_link
+-------------------------------
+
+        Behind each port, there is a ata_link. If there is a SATA PM in the
+        topology, 15 ata_link objects are created.
+
+        If a link is behind a port, the directory name is linkX, where X is
+        ata_port_id of the port.
+        If a link is behind a PM, its name is linkX.Y where X is ata_port_id
+        of the parent port and Y the PM port.
+
+hw_sata_spd_limit
+
+        Maximum speed supported by the connected SATA device.
+
+sata_spd_limit
+
+        Maximum speed imposed by libata.
+
+sata_spd
+
+        Current speed of the link [1.5, 3Gps,...].
+
+Files under /sys/class/ata_device
+---------------------------------
+
+        Behind each link, up to two ata device are created.
+        The name of the directory is devX[.Y].Z where:
+        - X is ata_port_id of the port where the device is connected,
+        - Y the port of the PM if any, and
+        - Z the device id: for PATA, there is usually 2 devices [0,1],
+        only 1 for SATA.
+
+class
+        Device class. Can be "ata" for disk, "atapi" for packet device,
+        "pmp" for PM, or "none" if no device was found behind the link.
+
+dma_mode
+
+        Transfer modes supported by the device when in DMA mode.
+        Mostly used by PATA device.
+
+pio_mode
+
+        Transfer modes supported by the device when in PIO mode.
+        Mostly used by PATA device.
+
+xfer_mode
+
+        Current transfer mode.
+
+id
+
+        Cached result of IDENTIFY command, as described in ATA8 7.16 and 7.17.
+        Only valid if the device is not a PM.
+
+gscr
+
+        Cached result of the dump of PM GSCR register.
+        Valid registers are:
+        0:      SATA_PMP_GSCR_PROD_ID,
+        1:      SATA_PMP_GSCR_REV,
+        2:      SATA_PMP_GSCR_PORT_INFO,
+        32:     SATA_PMP_GSCR_ERROR,
+        33:     SATA_PMP_GSCR_ERROR_EN,
+        64:     SATA_PMP_GSCR_FEAT,
+        96:     SATA_PMP_GSCR_FEAT_EN,
+        130:    SATA_PMP_GSCR_SII_GPIO
+        Only valid if the device is a PM.
+
+spdn_cnt
+
+        Number of time libata decided to lower the speed of link due to errors.
+
+ering
+
+        Formatted output of the error ring of the device.
diff --git a/Documentation/ABI/testing/sysfs-devices-power b/Documentation/ABI/testing/sysfs-devices-power
index 6123c523bfd7..7628cd1bc36a 100644
--- a/Documentation/ABI/testing/sysfs-devices-power
+++ b/Documentation/ABI/testing/sysfs-devices-power
@@ -77,3 +77,91 @@ Description:
                 devices this attribute is set to "enabled" by bus type code or
                 device drivers and in that cases it should be safe to leave the
                 default value.
+
+What:           /sys/devices/.../power/wakeup_count
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_count attribute contains the number
+                of signaled wakeup events associated with the device.  This
+                attribute is read-only.  If the device is not enabled to wake up
+                the system from sleep states, this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_active_count
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_active_count attribute contains the
+                number of times the processing of wakeup events associated with
+                the device was completed (at the kernel level).  This attribute
+                is read-only.  If the device is not enabled to wake up the
+                system from sleep states, this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_hit_count
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_hit_count attribute contains the
+                number of times the processing of a wakeup event associated with
+                the device might prevent the system from entering a sleep state.
+                This attribute is read-only.  If the device is not enabled to
+                wake up the system from sleep states, this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_active
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_active attribute contains either 1,
+                or 0, depending on whether or not a wakeup event associated with
+                the device is being processed (1).  This attribute is read-only.
+                If the device is not enabled to wake up the system from sleep
+                states, this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_total_time_ms
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_total_time_ms attribute contains
+                the total time of processing wakeup events associated with the
+                device, in milliseconds.  This attribute is read-only.  If the
+                device is not enabled to wake up the system from sleep states,
+                this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_max_time_ms
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_max_time_ms attribute contains
+                the maximum time of processing a single wakeup event associated
+                with the device, in milliseconds.  This attribute is read-only.
+                If the device is not enabled to wake up the system from sleep
+                states, this attribute is empty.
+
+What:           /sys/devices/.../power/wakeup_last_time_ms
+Date:           September 2010
+Contact:        Rafael J. Wysocki <rjw@sisk.pl>
+Description:
+                The /sys/devices/.../wakeup_last_time_ms attribute contains
+                the value of the monotonic clock corresponding to the time of
+                signaling the last wakeup event associated with the device, in
+                milliseconds.  This attribute is read-only.  If the device is
+                not enabled to wake up the system from sleep states, this
+                attribute is empty.
+
+What:           /sys/devices/.../power/autosuspend_delay_ms
+Date:           September 2010
+Contact:        Alan Stern <stern@rowland.harvard.edu>
+Description:
+                The /sys/devices/.../power/autosuspend_delay_ms attribute
+                contains the autosuspend delay value (in milliseconds).  Some
+                drivers do not want their device to suspend as soon as it
+                becomes idle at run time; they want the device to remain
+                inactive for a certain minimum period of time first.  That
+                period is called the autosuspend delay.  Negative values will
+                prevent the device from being suspended at run time (similar
+                to writing "on" to the power/control attribute).  Values >=
+                1000 will cause the autosuspend timer expiration to be rounded
+                up to the nearest second.
+
+                Not all drivers support this attribute.  If it isn't supported,
+                attempts to read or write it will yield I/O errors.
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra b/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
new file mode 100644
index 000000000000..ad1125b02ff4
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
@@ -0,0 +1,98 @@
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/actual_cpi
+Date:           August 2010
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    It is possible to switch the cpi setting of the mouse with the
+                press of a button.
+                When read, this file returns the raw number of the actual cpi
+                setting reported by the mouse. This number has to be further
+                processed to receive the real dpi value.
+
+                VALUE DPI
+                1     400
+                2     800
+                4     1600
+
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/actual_profile
+Date:           August 2010
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When read, this file returns the number of the actual profile in
+                range 0-4.
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/firmware_version
+Date:           August 2010
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When read, this file returns the raw integer version number of the
+                firmware reported by the mouse. Using the integer value eases
+                further usage in other programs. To receive the real version
+                number the decimal point has to be shifted 2 positions to the
+                left. E.g. a returned value of 138 means 1.38
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/profile_settings
+Date:           August 2010
+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 in settings and buttons.
+                profile_settings 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 13 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.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/profile[1-5]_settings
+Date:           August 2010
+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 in settings and buttons.
+                profile_settings holds informations like resolution, sensitivity
+                and light effects.
+                When read, these files return the respective profile settings.
+                The returned data is 13 bytes in size.
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/profile_buttons
+Date:           August 2010
+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 in settings and buttons.
+                profile_buttons holds informations about button layout.
+                When written, this file lets one write the respective profile
+                buttons back to the mouse. The data has to be 19 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.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/profile[1-5]_buttons
+Date:           August 2010
+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 in settings and buttons.
+                profile_buttons holds informations about button layout.
+                When read, these files return the respective profile buttons.
+                The returned data is 19 bytes in size.
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/startup_profile
+Date:           August 2010
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    The integer value of this attribute ranges from 0-4.
+                When read, this attribute returns the number of the profile
+                that's active when the mouse is powered on.
+                This file is readonly.
+
+What:           /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/settings
+Date:           August 2010
+Contact:        Stefan Achatz <erazor_de@users.sourceforge.net>
+Description:    When read, this file returns the settings stored in the mouse.
+                The size of the data is 3 bytes and holds information on the
+                startup_profile.
+                When written, this file lets write settings back to the mouse.
+                The data has to be 3 bytes long. The mouse will reject invalid
+                data.
diff --git a/Documentation/ABI/testing/sysfs-module b/Documentation/ABI/testing/sysfs-module
new file mode 100644
index 000000000000..cfcec3bffc0a
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-module
@@ -0,0 +1,12 @@
+What:           /sys/module/pch_phub/drivers/.../pch_mac
+Date:           August 2010
+KernelVersion:  2.6.35
+Contact:        masa-korg@dsn.okisemi.com
+Description:    Write/read GbE MAC address.
+
+What:           /sys/module/pch_phub/drivers/.../pch_firmware
+Date:           August 2010
+KernelVersion:  2.6.35
+Contact:        masa-korg@dsn.okisemi.com
+Description:    Write/read Option ROM data.
+
diff --git a/Documentation/ABI/testing/sysfs-power b/Documentation/ABI/testing/sysfs-power
index 2875f1f74a07..194ca446ac28 100644
--- a/Documentation/ABI/testing/sysfs-power
+++ b/Documentation/ABI/testing/sysfs-power
@@ -99,9 +99,38 @@ Description:
 
                 dmesg -s 1000000 | grep 'hash matches'
 
+                If you do not get any matches (or they appear to be false
+                positives), it is possible that the last PM event point
+                referred to a device created by a loadable kernel module.  In
+                this case cat /sys/power/pm_trace_dev_match (see below) after
+                your system is started up and the kernel modules are loaded.
+
                 CAUTION: Using it will cause your machine's real-time (CMOS)
                 clock to be set to a random invalid time after a resume.
 
+What;           /sys/power/pm_trace_dev_match
+Date:           October 2010
+Contact:        James Hogan <james@albanarts.com>
+Description:
+                The /sys/power/pm_trace_dev_match file contains the name of the
+                device associated with the last PM event point saved in the RTC
+                across reboots when pm_trace has been used.  More precisely it
+                contains the list of current devices (including those
+                registered by loadable kernel modules since boot) which match
+                the device hash in the RTC at boot, with a newline after each
+                one.
+
+                The advantage of this file over the hash matches printed to the
+                kernel log (see /sys/power/pm_trace), is that it includes
+                devices created after boot by loadable kernel modules.
+
+                Due to the small hash size necessary to fit in the RTC, it is
+                possible that more than one device matches the hash, in which
+                case further investigation is required to determine which
+                device is causing the problem.  Note that genuine RTC clock
+                values (such as when pm_trace has not been used), can still
+                match a device and output it's name here.
+
 What:           /sys/power/pm_async
 Date:           January 2009
 Contact:        Rafael J. Wysocki <rjw@sisk.pl>