Loading Documentation/ABI/testing/sysfs-class-mtd +9 −8 Original line number Original line Diff line number Diff line Loading @@ -142,13 +142,14 @@ KernelVersion: 3.4 Contact: linux-mtd@lists.infradead.org Contact: linux-mtd@lists.infradead.org Description: Description: This allows the user to examine and adjust the criteria by which This allows the user to examine and adjust the criteria by which mtd returns -EUCLEAN from mtd_read(). If the maximum number of mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the bit errors that were corrected on any single region comprising maximum number of bit errors that were corrected on any single an ecc step (as reported by the driver) equals or exceeds this region comprising an ecc step (as reported by the driver) equals value, -EUCLEAN is returned. Otherwise, absent an error, 0 is or exceeds this value, -EUCLEAN is returned. Otherwise, absent returned. Higher layers (e.g., UBI) use this return code as an an error, 0 is returned. Higher layers (e.g., UBI) use this indication that an erase block may be degrading and should be return code as an indication that an erase block may be scrutinized as a candidate for being marked as bad. degrading and should be scrutinized as a candidate for being marked as bad. The initial value may be specified by the flash device driver. The initial value may be specified by the flash device driver. If not, then the default value is ecc_strength. If not, then the default value is ecc_strength. Loading @@ -167,7 +168,7 @@ Description: block degradation, but high enough to avoid the consequences of block degradation, but high enough to avoid the consequences of a persistent return value of -EUCLEAN on devices where sticky a persistent return value of -EUCLEAN on devices where sticky bitflips occur. Note that if bitflip_threshold exceeds 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 Conversely, if bitflip_threshold is zero, -EUCLEAN is always returned, absent a hard error. returned, absent a hard error. Loading Documentation/ABI/testing/sysfs-devices-system-xen_cpu 0 → 100644 +20 −0 Original line number Original line Diff line number Diff line 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. Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd 0 → 100644 +38 −0 Original line number Original line Diff line number Diff line 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). Documentation/ABI/testing/sysfs-driver-hid-roccat-savu 0 → 100644 +77 −0 Original line number Original line Diff line number Diff line 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 Documentation/ABI/testing/sysfs-kernel-iommu_groups 0 → 100644 +14 −0 Original line number Original line Diff line number Diff line 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: Loading
Documentation/ABI/testing/sysfs-class-mtd +9 −8 Original line number Original line Diff line number Diff line Loading @@ -142,13 +142,14 @@ KernelVersion: 3.4 Contact: linux-mtd@lists.infradead.org Contact: linux-mtd@lists.infradead.org Description: Description: This allows the user to examine and adjust the criteria by which This allows the user to examine and adjust the criteria by which mtd returns -EUCLEAN from mtd_read(). If the maximum number of mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the bit errors that were corrected on any single region comprising maximum number of bit errors that were corrected on any single an ecc step (as reported by the driver) equals or exceeds this region comprising an ecc step (as reported by the driver) equals value, -EUCLEAN is returned. Otherwise, absent an error, 0 is or exceeds this value, -EUCLEAN is returned. Otherwise, absent returned. Higher layers (e.g., UBI) use this return code as an an error, 0 is returned. Higher layers (e.g., UBI) use this indication that an erase block may be degrading and should be return code as an indication that an erase block may be scrutinized as a candidate for being marked as bad. degrading and should be scrutinized as a candidate for being marked as bad. The initial value may be specified by the flash device driver. The initial value may be specified by the flash device driver. If not, then the default value is ecc_strength. If not, then the default value is ecc_strength. Loading @@ -167,7 +168,7 @@ Description: block degradation, but high enough to avoid the consequences of block degradation, but high enough to avoid the consequences of a persistent return value of -EUCLEAN on devices where sticky a persistent return value of -EUCLEAN on devices where sticky bitflips occur. Note that if bitflip_threshold exceeds 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 Conversely, if bitflip_threshold is zero, -EUCLEAN is always returned, absent a hard error. returned, absent a hard error. Loading
Documentation/ABI/testing/sysfs-devices-system-xen_cpu 0 → 100644 +20 −0 Original line number Original line Diff line number Diff line 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.
Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd 0 → 100644 +38 −0 Original line number Original line Diff line number Diff line 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).
Documentation/ABI/testing/sysfs-driver-hid-roccat-savu 0 → 100644 +77 −0 Original line number Original line Diff line number Diff line 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
Documentation/ABI/testing/sysfs-kernel-iommu_groups 0 → 100644 +14 −0 Original line number Original line Diff line number Diff line 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: