diff options
Diffstat (limited to 'Documentation/ABI')
139 files changed, 0 insertions, 8948 deletions
diff --git a/Documentation/ABI/README b/Documentation/ABI/README deleted file mode 100644 index 9feaf16f161..00000000000 --- a/Documentation/ABI/README +++ /dev/null @@ -1,77 +0,0 @@ -This directory attempts to document the ABI between the Linux kernel and -userspace, and the relative stability of these interfaces. Due to the -everchanging nature of Linux, and the differing maturity levels, these -interfaces should be used by userspace programs in different ways. - -We have four different levels of ABI stability, as shown by the four -different subdirectories in this location. Interfaces may change levels -of stability according to the rules described below. - -The different levels of stability are: - - stable/ - This directory documents the interfaces that the developer has - defined to be stable. Userspace programs are free to use these - interfaces with no restrictions, and backward compatibility for - them will be guaranteed for at least 2 years. Most interfaces - (like syscalls) are expected to never change and always be - available. - - testing/ - This directory documents interfaces that are felt to be stable, - as the main development of this interface has been completed. - The interface can be changed to add new features, but the - current interface will not break by doing this, unless grave - errors or security problems are found in them. Userspace - programs can start to rely on these interfaces, but they must be - aware of changes that can occur before these interfaces move to - be marked stable. Programs that use these interfaces are - strongly encouraged to add their name to the description of - these interfaces, so that the kernel developers can easily - notify them if any changes occur (see the description of the - layout of the files below for details on how to do this.) - - obsolete/ - This directory documents interfaces that are still remaining in - the kernel, but are marked to be removed at some later point in - time. The description of the interface will document the reason - why it is obsolete and when it can be expected to be removed. - The file Documentation/feature-removal-schedule.txt may describe - some of these interfaces, giving a schedule for when they will - be removed. - - removed/ - This directory contains a list of the old interfaces that have - been removed from the kernel. - -Every file in these directories will contain the following information: - -What: Short description of the interface -Date: Date created -KernelVersion: Kernel version this feature first showed up in. -Contact: Primary contact for this interface (may be a mailing list) -Description: Long description of the interface and how to use it. -Users: All users of this interface who wish to be notified when - it changes. This is very important for interfaces in - the "testing" stage, so that kernel developers can work - with userspace developers to ensure that things do not - break in ways that are unacceptable. It is also - important to get feedback for these interfaces to make - sure they are working in a proper way and do not need to - be changed further. - - -How things move between levels: - -Interfaces in stable may move to obsolete, as long as the proper -notification is given. - -Interfaces may be removed from obsolete and the kernel as long as the -documented amount of time has gone by. - -Interfaces in the testing state can move to the stable state when the -developers feel they are finished. They cannot be removed from the -kernel tree without going through the obsolete state first. - -It's up to the developer to place their interfaces in the category they -wish for it to start out in. diff --git a/Documentation/ABI/obsolete/proc-pid-oom_adj b/Documentation/ABI/obsolete/proc-pid-oom_adj deleted file mode 100644 index 9a3cb88ade4..00000000000 --- a/Documentation/ABI/obsolete/proc-pid-oom_adj +++ /dev/null @@ -1,22 +0,0 @@ -What: /proc/<pid>/oom_adj -When: August 2012 -Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's - badness heuristic used to determine which task to kill when the kernel - is out of memory. - - The badness heuristic has since been rewritten since the introduction of - this tunable such that its meaning is deprecated. The value was - implemented as a bitshift on a score generated by the badness() - function that did not have any precise units of measure. With the - rewrite, the score is given as a proportion of available memory to the - task allocating pages, so using a bitshift which grows the score - exponentially is, thus, impossible to tune with fine granularity. - - A much more powerful interface, /proc/<pid>/oom_score_adj, was - introduced with the oom killer rewrite that allows users to increase or - decrease the badness score linearly. This interface will replace - /proc/<pid>/oom_adj. - - A warning will be emitted to the kernel log if an application uses this - deprecated interface. After it is printed once, future warnings will be - suppressed until the kernel is rebooted. diff --git a/Documentation/ABI/obsolete/sysfs-bus-usb b/Documentation/ABI/obsolete/sysfs-bus-usb deleted file mode 100644 index bd096d33fbc..00000000000 --- a/Documentation/ABI/obsolete/sysfs-bus-usb +++ /dev/null @@ -1,31 +0,0 @@ -What: /sys/bus/usb/devices/.../power/level -Date: March 2007 -KernelVersion: 2.6.21 -Contact: Alan Stern <stern@rowland.harvard.edu> -Description: - Each USB device directory will contain a file named - power/level. This file holds a power-level setting for - the device, either "on" or "auto". - - "on" means that the device is not allowed to autosuspend, - although normal suspends for system sleep will still - be honored. "auto" means the device will autosuspend - and autoresume in the usual manner, according to the - capabilities of its driver. - - During normal use, devices should be left in the "auto" - level. The "on" level is meant for administrative uses. - If you want to suspend a device immediately but leave it - free to wake up in response to I/O requests, you should - write "0" to power/autosuspend. - - Device not capable of proper suspend and resume should be - left in the "on" level. Although the USB spec requires - devices to support suspend/resume, many of them do not. - In fact so many don't that by default, the USB core - initializes all non-hub devices in the "on" level. Some - drivers may change this setting when they are bound. - - This file is deprecated and will be removed after 2010. - Use the power/control file instead; it does exactly the - same thing. diff --git a/Documentation/ABI/obsolete/sysfs-class-rfkill b/Documentation/ABI/obsolete/sysfs-class-rfkill deleted file mode 100644 index ff60ad9eca4..00000000000 --- a/Documentation/ABI/obsolete/sysfs-class-rfkill +++ /dev/null @@ -1,29 +0,0 @@ -rfkill - radio frequency (RF) connector kill switch support - -For details to this subsystem look at Documentation/rfkill.txt. - -What: /sys/class/rfkill/rfkill[0-9]+/state -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: Current state of the transmitter. - This file is deprecated and scheduled to be removed in 2014, - because its not possible to express the 'soft and hard block' - state of the rfkill driver. -Values: A numeric value. - 0: RFKILL_STATE_SOFT_BLOCKED - transmitter is turned off by software - 1: RFKILL_STATE_UNBLOCKED - transmitter is (potentially) active - 2: RFKILL_STATE_HARD_BLOCKED - transmitter is forced off by something outside of - the driver's control. - -What: /sys/class/rfkill/rfkill[0-9]+/claim -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: This file is deprecated because there no longer is a way to - claim just control over a single rfkill instance. - This file is scheduled to be removed in 2012. -Values: 0: Kernel handles events diff --git a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus b/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus deleted file mode 100644 index c2a270b45b0..00000000000 --- a/Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/startup_profile -Date: October 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 actual - profile. This value is persistent, so its equivalent to the - profile that's active when the mouse is powered on next time. - When written, this file sets the number of the startup profile - and the mouse activates this profile immediately. - Please use actual_profile, it does the same thing. diff --git a/Documentation/ABI/removed/devfs b/Documentation/ABI/removed/devfs deleted file mode 100644 index 0020c49933c..00000000000 --- a/Documentation/ABI/removed/devfs +++ /dev/null @@ -1,12 +0,0 @@ -What: devfs -Date: July 2005 (scheduled), finally removed in kernel v2.6.18 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - devfs has been unmaintained for a number of years, has unfixable - races, contains a naming policy within the kernel that is - against the LSB, and can be replaced by using udev. - The files fs/devfs/*, include/linux/devfs_fs*.h were removed, - along with the assorted devfs function calls throughout the - kernel tree. - -Users: diff --git a/Documentation/ABI/removed/dv1394 b/Documentation/ABI/removed/dv1394 deleted file mode 100644 index c2310b6676f..00000000000 --- a/Documentation/ABI/removed/dv1394 +++ /dev/null @@ -1,14 +0,0 @@ -What: dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/dv1394/* were character device files, one for each FireWire - controller and for NTSC and PAL respectively, from which DV data - could be received by read() or transmitted by write(). A few - ioctl()s allowed limited control. - This special-purpose interface has been superseded by libraw1394 + - libiec61883 which are functionally equivalent, support HDV, and - transparently work on top of the newer firewire kernel drivers. - -Users: - ffmpeg/libavformat (if configured for DV1394) diff --git a/Documentation/ABI/removed/ip_queue b/Documentation/ABI/removed/ip_queue deleted file mode 100644 index 3243613bc2d..00000000000 --- a/Documentation/ABI/removed/ip_queue +++ /dev/null @@ -1,9 +0,0 @@ -What: ip_queue -Date: finally removed in kernel v3.5.0 -Contact: Pablo Neira Ayuso <pablo@netfilter.org> -Description: - ip_queue has been replaced by nfnetlink_queue which provides - more advanced queueing mechanism to user-space. The ip_queue - module was already announced to become obsolete years ago. - -Users: diff --git a/Documentation/ABI/removed/o2cb b/Documentation/ABI/removed/o2cb deleted file mode 100644 index 20c91adca6d..00000000000 --- a/Documentation/ABI/removed/o2cb +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/o2cb symlink -Date: May 2011 -KernelVersion: 3.0 -Contact: ocfs2-devel@oss.oracle.com -Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is - removed when new versions of ocfs2-tools which know to look - in /sys/fs/o2cb are sufficiently prevalent. Don't code new - software to look here, it should try /sys/fs/o2cb instead. -Users: ocfs2-tools. It's sufficient to mail proposed changes to - ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/removed/raw1394 b/Documentation/ABI/removed/raw1394 deleted file mode 100644 index ec333e67632..00000000000 --- a/Documentation/ABI/removed/raw1394 +++ /dev/null @@ -1,15 +0,0 @@ -What: raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/raw1394 was a character device file that allowed low-level - access to FireWire buses. Its major drawbacks were its inability - to implement sensible device security policies, and its low level - of abstraction that required userspace clients to duplicate much - of the kernel's ieee1394 core functionality. - Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of - firewire-core. - -Users: - libraw1394 (works with firewire-cdev too, transparent to library ABI - users) diff --git a/Documentation/ABI/removed/video1394 b/Documentation/ABI/removed/video1394 deleted file mode 100644 index c39c25aee77..00000000000 --- a/Documentation/ABI/removed/video1394 +++ /dev/null @@ -1,16 +0,0 @@ -What: video1394 (a.k.a. "OHCI-1394 Video support" for FireWire) -Date: May 2010 (scheduled), finally removed in kernel v2.6.37 -Contact: linux1394-devel@lists.sourceforge.net -Description: - /dev/video1394/* were character device files, one for each FireWire - controller, which were used for isochronous I/O. It was added as an - alternative to raw1394's isochronous I/O functionality which had - performance issues in its first generation. Any video1394 user had - to use raw1394 + libraw1394 too because video1394 did not provide - asynchronous I/O for device discovery and configuration. - Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of - firewire-core. - -Users: - libdc1394 (works with firewire-cdev too, transparent to library ABI - users) diff --git a/Documentation/ABI/stable/firewire-cdev b/Documentation/ABI/stable/firewire-cdev deleted file mode 100644 index 16d03082736..00000000000 --- a/Documentation/ABI/stable/firewire-cdev +++ /dev/null @@ -1,103 +0,0 @@ -What: /dev/fw[0-9]+ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - The character device files /dev/fw* are the interface between - firewire-core and IEEE 1394 device drivers implemented in - userspace. The ioctl(2)- and read(2)-based ABI is defined and - documented in <linux/firewire-cdev.h>. - - This ABI offers most of the features which firewire-core also - exposes to kernelspace IEEE 1394 drivers. - - Each /dev/fw* is associated with one IEEE 1394 node, which can - be remote or local nodes. Operations on a /dev/fw* file have - different scope: - - The 1394 node which is associated with the file: - - Asynchronous request transmission - - Get the Configuration ROM - - Query node ID - - Query maximum speed of the path between this node - and local node - - The 1394 bus (i.e. "card") to which the node is attached to: - - Isochronous stream transmission and reception - - Asynchronous stream transmission and reception - - Asynchronous broadcast request transmission - - PHY packet transmission and reception - - Allocate, reallocate, deallocate isochronous - resources (channels, bandwidth) at the bus's IRM - - Query node IDs of local node, root node, IRM, bus - manager - - Query cycle time - - Bus reset initiation, bus reset event reception - - All 1394 buses: - - Allocation of IEEE 1212 address ranges on the local - link layers, reception of inbound requests to such - an address range, asynchronous response transmission - to inbound requests - - Addition of descriptors or directories to the local - nodes' Configuration ROM - - Due to the different scope of operations and in order to let - userland implement different access permission models, some - operations are restricted to /dev/fw* files that are associated - with a local node: - - Addition of descriptors or directories to the local - nodes' Configuration ROM - - PHY packet transmission and reception - - A /dev/fw* file remains associated with one particular node - during its entire life time. Bus topology changes, and hence - node ID changes, are tracked by firewire-core. ABI users do not - need to be aware of topology. - - The following file operations are supported: - - open(2) - Currently the only useful flags are O_RDWR. - - ioctl(2) - Initiate various actions. Some take immediate effect, others - are performed asynchronously while or after the ioctl returns. - See the inline documentation in <linux/firewire-cdev.h> for - descriptions of all ioctls. - - poll(2), select(2), epoll_wait(2) etc. - Watch for events to become available to be read. - - read(2) - Receive various events. There are solicited events like - outbound asynchronous transaction completion or isochronous - buffer completion, and unsolicited events such as bus resets, - request reception, or PHY packet reception. Always use a read - buffer which is large enough to receive the largest event that - could ever arrive. See <linux/firewire-cdev.h> for descriptions - of all event types and for which ioctls affect reception of - events. - - mmap(2) - Allocate a DMA buffer for isochronous reception or transmission - and map it into the process address space. The arguments should - be used as follows: addr = NULL, length = the desired buffer - size, i.e. number of packets times size of largest packet, - prot = at least PROT_READ for reception and at least PROT_WRITE - for transmission, flags = MAP_SHARED, fd = the handle to the - /dev/fw*, offset = 0. - - Isochronous reception works in packet-per-buffer fashion except - for multichannel reception which works in buffer-fill mode. - - munmap(2) - Unmap the isochronous I/O buffer from the process address space. - - close(2) - Besides stopping and freeing I/O contexts that were associated - with the file descriptor, back out any changes to the local - nodes' Configuration ROM. Deallocate isochronous channels and - bandwidth at the IRM that were marked for kernel-assisted - re- and deallocation. - -Users: libraw1394 - libdc1394 - tools like jujuutils, fwhack, ... diff --git a/Documentation/ABI/stable/o2cb b/Documentation/ABI/stable/o2cb deleted file mode 100644 index 5eb1545e0b8..00000000000 --- a/Documentation/ABI/stable/o2cb +++ /dev/null @@ -1,10 +0,0 @@ -What: /sys/fs/o2cb/ (was /sys/o2cb) -Date: Dec 2005 -KernelVersion: 2.6.16 -Contact: ocfs2-devel@oss.oracle.com -Description: Ocfs2-tools looks at 'interface-revision' for versioning - information. Each logmask/ file controls a set of debug prints - and can be written into with the strings "allow", "deny", or - "off". Reading the file returns the current state. -Users: ocfs2-tools. It's sufficient to mail proposed changes to - ocfs2-devel@oss.oracle.com. diff --git a/Documentation/ABI/stable/syscalls b/Documentation/ABI/stable/syscalls deleted file mode 100644 index c3ae3e7d6a0..00000000000 --- a/Documentation/ABI/stable/syscalls +++ /dev/null @@ -1,10 +0,0 @@ -What: The kernel syscall interface -Description: - This interface matches much of the POSIX interface and is based - on it and other Unix based interfaces. It will only be added to - over time, and not have things removed from it. - - Note that this interface is different for every architecture - that Linux supports. Please see the architecture-specific - documentation for details on the syscall numbers that are to be - mapped to each syscall. diff --git a/Documentation/ABI/stable/sysfs-acpi-pmprofile b/Documentation/ABI/stable/sysfs-acpi-pmprofile deleted file mode 100644 index 964c7a8afb2..00000000000 --- a/Documentation/ABI/stable/sysfs-acpi-pmprofile +++ /dev/null @@ -1,22 +0,0 @@ -What: /sys/firmware/acpi/pm_profile -Date: 03-Nov-2011 -KernelVersion: v3.2 -Contact: linux-acpi@vger.kernel.org -Description: The ACPI pm_profile sysfs interface exports the platform - power management (and performance) requirement expectations - as provided by BIOS. The integer value is directly passed as - retrieved from the FADT ACPI table. -Values: For possible values see ACPI specification: - 5.2.9 Fixed ACPI Description Table (FADT) - Field: Preferred_PM_Profile - - Currently these values are defined by spec: - 0 Unspecified - 1 Desktop - 2 Mobile - 3 Workstation - 4 Enterprise Server - 5 SOHO Server - 6 Appliance PC - 7 Performance Server - >7 Reserved diff --git a/Documentation/ABI/stable/sysfs-bus-firewire b/Documentation/ABI/stable/sysfs-bus-firewire deleted file mode 100644 index 3d484e5dc84..00000000000 --- a/Documentation/ABI/stable/sysfs-bus-firewire +++ /dev/null @@ -1,122 +0,0 @@ -What: /sys/bus/firewire/devices/fw[0-9]+/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 node device attributes. - Read-only. Mutable during the node device's lifetime. - See IEEE 1212 for semantic definitions. - - config_rom - Contents of the Configuration ROM register. - Binary attribute; an array of host-endian u32. - - guid - The node's EUI-64 in the bus information block of - Configuration ROM. - Hexadecimal string representation of an u64. - - -What: /sys/bus/firewire/devices/fw[0-9]+/units -Date: June 2009 -KernelVersion: 2.6.31 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 node device attribute. - Read-only. Mutable during the node device's lifetime. - See IEEE 1212 for semantic definitions. - - units - Summary of all units present in an IEEE 1394 node. - Contains space-separated tuples of specifier_id and - version of each unit present in the node. Specifier_id - and version are hexadecimal string representations of - u24 of the respective unit directory entries. - Specifier_id and version within each tuple are separated - by a colon. - -Users: udev rules to set ownership and access permissions or ACLs of - /dev/fw[0-9]+ character device files - - -What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - IEEE 1394 unit device attributes. - Read-only. Immutable during the unit device's lifetime. - See IEEE 1212 for semantic definitions. - - modalias - Same as MODALIAS in the uevent at device creation. - - rom_index - Offset of the unit directory within the parent device's - (node device's) Configuration ROM, in quadlets. - Decimal string representation. - - -What: /sys/bus/firewire/devices/*/ -Date: May 2007 -KernelVersion: 2.6.22 -Contact: linux1394-devel@lists.sourceforge.net -Description: - Attributes common to IEEE 1394 node devices and unit devices. - Read-only. Mutable during the node device's lifetime. - Immutable during the unit device's lifetime. - See IEEE 1212 for semantic definitions. - - These attributes are only created if the root directory of an - IEEE 1394 node or the unit directory of an IEEE 1394 unit - actually contains according entries. - - hardware_version - Hexadecimal string representation of an u24. - - hardware_version_name - Contents of a respective textual descriptor leaf. - - model - Hexadecimal string representation of an u24. - - model_name - Contents of a respective textual descriptor leaf. - - specifier_id - Hexadecimal string representation of an u24. - Mandatory in unit directories according to IEEE 1212. - - vendor - Hexadecimal string representation of an u24. - Mandatory in the root directory according to IEEE 1212. - - vendor_name - Contents of a respective textual descriptor leaf. - - version - Hexadecimal string representation of an u24. - Mandatory in unit directories according to IEEE 1212. - - -What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id - formerly - /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id -Date: Feb 2004 -KernelVersion: 2.6.4 -Contact: linux1394-devel@lists.sourceforge.net -Description: - SCSI target port identifier and logical unit identifier of a - logical unit of an SBP-2 target. The identifiers are specified - in SAM-2...SAM-4 annex A. They are persistent and world-wide - unique properties the SBP-2 attached target. - - Read-only attribute, immutable during the target's lifetime. - Format, as exposed by firewire-sbp2 since 2.6.22, May 2007: - Colon-separated hexadecimal string representations of - u64 EUI-64 : u24 directory_ID : u16 LUN - without 0x prefixes, without whitespace. The former sbp2 driver - (removed in 2.6.37 after being superseded by firewire-sbp2) used - a somewhat shorter format which was not as close to SAM. - -Users: udev rules to create /dev/disk/by-id/ symlinks diff --git a/Documentation/ABI/stable/sysfs-bus-xen-backend b/Documentation/ABI/stable/sysfs-bus-xen-backend deleted file mode 100644 index 3d5951c8bf5..00000000000 --- a/Documentation/ABI/stable/sysfs-bus-xen-backend +++ /dev/null @@ -1,75 +0,0 @@ -What: /sys/bus/xen-backend/devices/*/devtype -Date: Feb 2009 -KernelVersion: 2.6.38 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The type of the device. e.g., one of: 'vbd' (block), - 'vif' (network), or 'vfb' (framebuffer). - -What: /sys/bus/xen-backend/devices/*/nodename -Date: Feb 2009 -KernelVersion: 2.6.38 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - XenStore node (under /local/domain/NNN/) for this - backend device. - -What: /sys/bus/xen-backend/devices/vbd-*/physical_device -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The major:minor number (in hexidecimal) of the - physical device providing the storage for this backend - block device. - -What: /sys/bus/xen-backend/devices/vbd-*/mode -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Whether the block device is read-only ('r') or - read-write ('w'). - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/f_req -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of flush requests from the frontend. - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/oo_req -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of requests delayed because the backend was too - busy processing previous requests. - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_req -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of read requests from the frontend. - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_sect -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of sectors read by the frontend. - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_req -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of write requests from the frontend. - -What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_sect -Date: April 2011 -KernelVersion: 3.0 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Number of sectors written by the frontend. diff --git a/Documentation/ABI/stable/sysfs-class-backlight b/Documentation/ABI/stable/sysfs-class-backlight deleted file mode 100644 index 70302f370e7..00000000000 --- a/Documentation/ABI/stable/sysfs-class-backlight +++ /dev/null @@ -1,56 +0,0 @@ -What: /sys/class/backlight/<backlight>/bl_power -Date: April 2005 -KernelVersion: 2.6.12 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Control BACKLIGHT power, values are FB_BLANK_* from fb.h - - FB_BLANK_UNBLANK (0) : power on. - - FB_BLANK_POWERDOWN (4) : power off -Users: HAL - -What: /sys/class/backlight/<backlight>/brightness -Date: April 2005 -KernelVersion: 2.6.12 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Control the brightness for this <backlight>. Values - are between 0 and max_brightness. This file will also - show the brightness level stored in the driver, which - may not be the actual brightness (see actual_brightness). -Users: HAL - -What: /sys/class/backlight/<backlight>/actual_brightness -Date: March 2006 -KernelVersion: 2.6.17 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Show the actual brightness by querying the hardware. -Users: HAL - -What: /sys/class/backlight/<backlight>/max_brightness -Date: April 2005 -KernelVersion: 2.6.12 -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/stable/sysfs-class-rfkill b/Documentation/ABI/stable/sysfs-class-rfkill deleted file mode 100644 index 097f522c33b..00000000000 --- a/Documentation/ABI/stable/sysfs-class-rfkill +++ /dev/null @@ -1,67 +0,0 @@ -rfkill - radio frequency (RF) connector kill switch support - -For details to this subsystem look at Documentation/rfkill.txt. - -For the deprecated /sys/class/rfkill/*/state and -/sys/class/rfkill/*/claim knobs of this interface look in -Documentation/ABI/obsolete/sysfs-class-rfkill. - -What: /sys/class/rfkill -Date: 09-Jul-2007 -KernelVersion: v2.6.22 -Contact: linux-wireless@vger.kernel.org, -Description: The rfkill class subsystem folder. - Each registered rfkill driver is represented by an rfkillX - subfolder (X being an integer > 0). - - -What: /sys/class/rfkill/rfkill[0-9]+/name -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: Name assigned by driver to this key (interface or driver name). -Values: arbitrary string. - - -What: /sys/class/rfkill/rfkill[0-9]+/type -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: Driver type string ("wlan", "bluetooth", etc). -Values: See include/linux/rfkill.h. - - -What: /sys/class/rfkill/rfkill[0-9]+/persistent -Date: 09-Jul-2007 -KernelVersion v2.6.22 -Contact: linux-wireless@vger.kernel.org -Description: Whether the soft blocked state is initialised from non-volatile - storage at startup. -Values: A numeric value. - 0: false - 1: true - - -What: /sys/class/rfkill/rfkill[0-9]+/hard -Date: 12-March-2010 -KernelVersion v2.6.34 -Contact: linux-wireless@vger.kernel.org -Description: Current hardblock state. This file is read only. -Values: A numeric value. - 0: inactive - The transmitter is (potentially) active. - 1: active - The transmitter is forced off by something outside of - the driver's control. - - -What: /sys/class/rfkill/rfkill[0-9]+/soft -Date: 12-March-2010 -KernelVersion v2.6.34 -Contact: linux-wireless@vger.kernel.org -Description: Current softblock state. This file is read and write. -Values: A numeric value. - 0: inactive - The transmitter is (potentially) active. - 1: active - The transmitter is turned off by software. diff --git a/Documentation/ABI/stable/sysfs-class-ubi b/Documentation/ABI/stable/sysfs-class-ubi deleted file mode 100644 index 18d471d9fae..00000000000 --- a/Documentation/ABI/stable/sysfs-class-ubi +++ /dev/null @@ -1,212 +0,0 @@ -What: /sys/class/ubi/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - The ubi/ class sub-directory belongs to the UBI subsystem and - provides general UBI information, per-UBI device information - and per-UBI volume information. - -What: /sys/class/ubi/version -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - This file contains version of the latest supported UBI on-media - format. Currently it is 1, and there is no plan to change this. - However, if in the future UBI needs on-flash format changes - which cannot be done in a compatible manner, a new format - version will be added. So this is a mechanism for possible - future backward-compatible (but forward-incompatible) - improvements. - -What: /sys/class/ubiX/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - The /sys/class/ubi0, /sys/class/ubi1, etc directories describe - UBI devices (UBI device 0, 1, etc). They contain general UBI - device information and per UBI volume information (each UBI - device may have many UBI volumes) - -What: /sys/class/ubi/ubiX/avail_eraseblocks -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Amount of available logical eraseblock. For example, one may - create a new UBI volume which has this amount of logical - eraseblocks. - -What: /sys/class/ubi/ubiX/bad_peb_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Count of bad physical eraseblocks on the underlying MTD device. - -What: /sys/class/ubi/ubiX/bgt_enabled -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Contains ASCII "0\n" if the UBI background thread is disabled, - and ASCII "1\n" if it is enabled. - -What: /sys/class/ubi/ubiX/dev -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Major and minor numbers of the character device corresponding - to this UBI device (in <major>:<minor> format). - -What: /sys/class/ubi/ubiX/eraseblock_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Maximum logical eraseblock size this UBI device may provide. UBI - volumes may have smaller logical eraseblock size because of their - alignment. - -What: /sys/class/ubi/ubiX/max_ec -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Maximum physical eraseblock erase counter value. - -What: /sys/class/ubi/ubiX/max_vol_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Maximum number of volumes which this UBI device may have. - -What: /sys/class/ubi/ubiX/min_io_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Minimum input/output unit size. All the I/O may only be done - in fractions of the contained number. - -What: /sys/class/ubi/ubiX/mtd_num -Date: January 2008 -KernelVersion: 2.6.25 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Number of the underlying MTD device. - -What: /sys/class/ubi/ubiX/reserved_for_bad -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Number of physical eraseblocks reserved for bad block handling. - -What: /sys/class/ubi/ubiX/total_eraseblocks -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Total number of good (not marked as bad) physical eraseblocks on - the underlying MTD device. - -What: /sys/class/ubi/ubiX/volumes_count -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Count of volumes on this UBI device. - -What: /sys/class/ubi/ubiX/ubiX_Y/ -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - The /sys/class/ubi/ubiX/ubiX_0/, /sys/class/ubi/ubiX/ubiX_1/, - etc directories describe UBI volumes on UBI device X (volumes - 0, 1, etc). - -What: /sys/class/ubi/ubiX/ubiX_Y/alignment -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Volume alignment - the value the logical eraseblock size of - this volume has to be aligned on. For example, 2048 means that - logical eraseblock size is multiple of 2048. In other words, - volume logical eraseblock size is UBI device logical eraseblock - size aligned to the alignment value. - -What: /sys/class/ubi/ubiX/ubiX_Y/corrupted -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n" - if it is corrupted (e.g., due to an interrupted volume update). - -What: /sys/class/ubi/ubiX/ubiX_Y/data_bytes -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - The amount of data this volume contains. This value makes sense - only for static volumes, and for dynamic volume it equivalent - to the total volume size in bytes. - -What: /sys/class/ubi/ubiX/ubiX_Y/dev -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Major and minor numbers of the character device corresponding - to this UBI volume (in <major>:<minor> format). - -What: /sys/class/ubi/ubiX/ubiX_Y/name -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Volume name. - -What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Count of physical eraseblock reserved for this volume. - Equivalent to the volume size in logical eraseblocks. - -What: /sys/class/ubi/ubiX/ubiX_Y/type -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Volume type. Contains ASCII "dynamic\n" for dynamic volumes and - "static\n" for static volumes. - -What: /sys/class/ubi/ubiX/ubiX_Y/upd_marker -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Contains ASCII "0\n" if the update marker is not set for this - volume, and "1\n" if it is set. The update marker is set when - volume update starts, and cleaned when it ends. So the presence - of the update marker indicates that the volume is being updated - at the moment of the update was interrupted. The later may be - checked using the "corrupted" sysfs file. - -What: /sys/class/ubi/ubiX/ubiX_Y/usable_eb_size -Date: July 2006 -KernelVersion: 2.6.22 -Contact: Artem Bityutskiy <dedekind@infradead.org> -Description: - Logical eraseblock size of this volume. Equivalent to logical - eraseblock size of the device aligned on the volume alignment - value. diff --git a/Documentation/ABI/stable/sysfs-devices-node b/Documentation/ABI/stable/sysfs-devices-node deleted file mode 100644 index 49b82cad700..00000000000 --- a/Documentation/ABI/stable/sysfs-devices-node +++ /dev/null @@ -1,7 +0,0 @@ -What: /sys/devices/system/node/nodeX -Date: October 2002 -Contact: Linux Memory Management list <linux-mm@kvack.org> -Description: - When CONFIG_NUMA is enabled, this is a directory containing - information on node X such as what CPUs are local to the - node. diff --git a/Documentation/ABI/stable/sysfs-devices-system-xen_memory b/Documentation/ABI/stable/sysfs-devices-system-xen_memory deleted file mode 100644 index caa311d59ac..00000000000 --- a/Documentation/ABI/stable/sysfs-devices-system-xen_memory +++ /dev/null @@ -1,77 +0,0 @@ -What: /sys/devices/system/xen_memory/xen_memory0/max_retry_count -Date: May 2011 -KernelVersion: 2.6.39 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The maximum number of times the balloon driver will - attempt to increase the balloon before giving up. See - also 'retry_count' below. - A value of zero means retry forever and is the default one. - -What: /sys/devices/system/xen_memory/xen_memory0/max_schedule_delay -Date: May 2011 -KernelVersion: 2.6.39 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The limit that 'schedule_delay' (see below) will be - increased to. The default value is 32 seconds. - -What: /sys/devices/system/xen_memory/xen_memory0/retry_count -Date: May 2011 -KernelVersion: 2.6.39 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The current number of times that the balloon driver - has attempted to increase the size of the balloon. - The default value is one. With max_retry_count being - zero (unlimited), this means that the driver will attempt - to retry with a 'schedule_delay' delay. - -What: /sys/devices/system/xen_memory/xen_memory0/schedule_delay -Date: May 2011 -KernelVersion: 2.6.39 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The time (in seconds) to wait between attempts to - increase the balloon. Each time the balloon cannot be - increased, 'schedule_delay' is increased (until - 'max_schedule_delay' is reached at which point it - will use the max value). - -What: /sys/devices/system/xen_memory/xen_memory0/target -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - The target number of pages to adjust this domain's - memory reservation to. - -What: /sys/devices/system/xen_memory/xen_memory0/target_kb -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - As target above, except the value is in KiB. - -What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Current size (in KiB) of this domain's memory - reservation. - -What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Amount (in KiB) of high memory in the balloon. - -What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> -Description: - Amount (in KiB) of low (or normal) memory in the - balloon. diff --git a/Documentation/ABI/stable/sysfs-driver-qla2xxx b/Documentation/ABI/stable/sysfs-driver-qla2xxx deleted file mode 100644 index 9a59d84497e..00000000000 --- a/Documentation/ABI/stable/sysfs-driver-qla2xxx +++ /dev/null @@ -1,8 +0,0 @@ -What: /sys/bus/pci/drivers/qla2xxx/.../devices/* -Date: September 2009 -Contact: QLogic Linux Driver <linux-driver@qlogic.com> -Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to - signal a firmware-dump has been generated by the driver and is - ready for retrieval. -Users: qla2xxx-udev.sh. Proposed changes should be mailed to - linux-driver@qlogic.com diff --git a/Documentation/ABI/stable/sysfs-driver-usb-usbtmc b/Documentation/ABI/stable/sysfs-driver-usb-usbtmc deleted file mode 100644 index e960cd027e1..00000000000 --- a/Documentation/ABI/stable/sysfs-driver-usb-usbtmc +++ /dev/null @@ -1,62 +0,0 @@ -What: /sys/bus/usb/drivers/usbtmc/*/interface_capabilities -What: /sys/bus/usb/drivers/usbtmc/*/device_capabilities -Date: August 2008 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - These files show the various USB TMC capabilities as described - by the device itself. The full description of the bitfields - can be found in the USB TMC documents from the USB-IF entitled - "Universal Serial Bus Test and Measurement Class Specification - (USBTMC) Revision 1.0" section 4.2.1.8. - - The files are read only. - - -What: /sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities -What: /sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities -Date: August 2008 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - These files show the various USB TMC capabilities as described - by the device itself. The full description of the bitfields - can be found in the USB TMC documents from the USB-IF entitled - "Universal Serial Bus Test and Measurement Class, Subclass - USB488 Specification (USBTMC-USB488) Revision 1.0" section - 4.2.2. - - The files are read only. - - -What: /sys/bus/usb/drivers/usbtmc/*/TermChar -Date: August 2008 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - This file is the TermChar value to be sent to the USB TMC - device as described by the document, "Universal Serial Bus Test - and Measurement Class Specification - (USBTMC) Revision 1.0" as published by the USB-IF. - - Note that the TermCharEnabled file determines if this value is - sent to the device or not. - - -What: /sys/bus/usb/drivers/usbtmc/*/TermCharEnabled -Date: August 2008 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - This file determines if the TermChar is to be sent to the - device on every transaction or not. For more details about - this, please see the document, "Universal Serial Bus Test and - Measurement Class Specification (USBTMC) Revision 1.0" as - published by the USB-IF. - - -What: /sys/bus/usb/drivers/usbtmc/*/auto_abort -Date: August 2008 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - This file determines if the transaction of the USB TMC - device is to be automatically aborted if there is any error. - For more details about this, please see the document, - "Universal Serial Bus Test and Measurement Class Specification - (USBTMC) Revision 1.0" as published by the USB-IF. diff --git a/Documentation/ABI/stable/sysfs-firmware-efi-vars b/Documentation/ABI/stable/sysfs-firmware-efi-vars deleted file mode 100644 index 5def20b9019..00000000000 --- a/Documentation/ABI/stable/sysfs-firmware-efi-vars +++ /dev/null @@ -1,75 +0,0 @@ -What: /sys/firmware/efi/vars -Date: April 2004 -Contact: Matt Domsch <Matt_Domsch@dell.com> -Description: - This directory exposes interfaces for interactive with - EFI variables. For more information on EFI variables, - see 'Variable Services' in the UEFI specification - (section 7.2 in specification version 2.3 Errata D). - - In summary, EFI variables are named, and are classified - into separate namespaces through the use of a vendor - GUID. They also have an arbitrary binary value - associated with them. - - The efivars module enumerates these variables and - creates a separate directory for each one found. Each - directory has a name of the form "<key>-<vendor guid>" - and contains the following files: - - attributes: A read-only text file enumerating the - EFI variable flags. Potential values - include: - - EFI_VARIABLE_NON_VOLATILE - EFI_VARIABLE_BOOTSERVICE_ACCESS - EFI_VARIABLE_RUNTIME_ACCESS - EFI_VARIABLE_HARDWARE_ERROR_RECORD - EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS - - See the EFI documentation for an - explanation of each of these variables. - - data: A read-only binary file that can be read - to attain the value of the EFI variable - - guid: The vendor GUID of the variable. This - should always match the GUID in the - variable's name. - - raw_var: A binary file that can be read to obtain - a structure that contains everything - there is to know about the variable. - For structure definition see "struct - efi_variable" in the kernel sources. - - This file can also be written to in - order to update the value of a variable. - For this to work however, all fields of - the "struct efi_variable" passed must - match byte for byte with the structure - read out of the file, save for the value - portion. - - **Note** the efi_variable structure - read/written with this file contains a - 'long' type that may change widths - depending on your underlying - architecture. - - size: As ASCII representation of the size of - the variable's value. - - - In addition, two other magic binary files are provided - in the top-level directory and are used for adding and - removing variables: - - new_var: Takes a "struct efi_variable" and - instructs the EFI firmware to create a - new variable. - - del_var: Takes a "struct efi_variable" and - instructs the EFI firmware to remove any - variable that has a matching vendor GUID - and variable key name. diff --git a/Documentation/ABI/stable/sysfs-module b/Documentation/ABI/stable/sysfs-module deleted file mode 100644 index a0dd21c6db5..00000000000 --- a/Documentation/ABI/stable/sysfs-module +++ /dev/null @@ -1,30 +0,0 @@ -What: /sys/module -Description: - The /sys/module tree consists of the following structure: - - /sys/module/MODULENAME - The name of the module that is in the kernel. This - module name will show up either if the module is built - directly into the kernel, or if it is loaded as a - dynamic module. - - /sys/module/MODULENAME/parameters - This directory contains individual files that are each - individual parameters of the module that are able to be - changed at runtime. See the individual module - documentation as to the contents of these parameters and - what they accomplish. - - Note: The individual parameter names and values are not - considered stable, only the fact that they will be - placed in this location within sysfs. See the - individual driver documentation for details as to the - stability of the different parameters. - - /sys/module/MODULENAME/refcnt - If the module is able to be unloaded from the kernel, this file - will contain the current reference count of the module. - - Note: If the module is built into the kernel, or if the - CONFIG_MODULE_UNLOAD kernel configuration value is not enabled, - this file will not be present. diff --git a/Documentation/ABI/stable/thermal-notification b/Documentation/ABI/stable/thermal-notification deleted file mode 100644 index 9723e8b7aeb..00000000000 --- a/Documentation/ABI/stable/thermal-notification +++ /dev/null @@ -1,4 +0,0 @@ -What: A notification mechanism for thermal related events -Description: - This interface enables notification for thermal related events. - The notification is in the form of a netlink event. diff --git a/Documentation/ABI/stable/vdso b/Documentation/ABI/stable/vdso deleted file mode 100644 index 8a1cbb59449..00000000000 --- a/Documentation/ABI/stable/vdso +++ /dev/null @@ -1,27 +0,0 @@ -On some architectures, when the kernel loads any userspace program it -maps an ELF DSO into that program's address space. This DSO is called -the vDSO and it often contains useful and highly-optimized alternatives -to real syscalls. - -These functions are called just like ordinary C function according to -your platform's ABI. Call them from a sensible context. (For example, -if you set CS on x86 to something strange, the vDSO functions are -within their rights to crash.) In addition, if you pass a bad -pointer to a vDSO function, you might get SIGSEGV instead of -EFAULT. - -To find the DSO, parse the auxiliary vector passed to the program's -entry point. The AT_SYSINFO_EHDR entry will point to the vDSO. - -The vDSO uses symbol versioning; whenever you request a symbol from the -vDSO, specify the version you are expecting. - -Programs that dynamically link to glibc will use the vDSO automatically. -Otherwise, you can use the reference parser in Documentation/vDSO/parse_vdso.c. - -Unless otherwise noted, the set of symbols with any given version and the -ABI of those symbols is considered stable. It may vary across architectures, -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 diff --git a/Documentation/ABI/testing/configfs-spear-pcie-gadget b/Documentation/ABI/testing/configfs-spear-pcie-gadget deleted file mode 100644 index 875988146a6..00000000000 --- a/Documentation/ABI/testing/configfs-spear-pcie-gadget +++ /dev/null @@ -1,31 +0,0 @@ -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/debugfs-ec b/Documentation/ABI/testing/debugfs-ec deleted file mode 100644 index 6546115a94d..00000000000 --- a/Documentation/ABI/testing/debugfs-ec +++ /dev/null @@ -1,20 +0,0 @@ -What: /sys/kernel/debug/ec/*/{gpe,use_global_lock,io} -Date: July 2010 -Contact: Thomas Renninger <trenn@suse.de> -Description: - -General information like which GPE is assigned to the EC and whether -the global lock should get used. -Knowing the EC GPE one can watch the amount of HW events related to -the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe): -/sys/firmware/acpi/interrupts/gpeXY - -The io file is binary and a userspace tool located here: -ftp://ftp.suse.com/pub/people/trenn/sources/ec/ -should get used to read out the 256 Embedded Controller registers -or writing to them. - -CAUTION: Do not write to the Embedded Controller if you don't know -what you are doing! Rebooting afterwards also is a good idea. -This can influence the way your machine is cooled and fans may -not get switched on again after you did a wrong write. diff --git a/Documentation/ABI/testing/debugfs-ideapad b/Documentation/ABI/testing/debugfs-ideapad deleted file mode 100644 index 7079c0b2103..00000000000 --- a/Documentation/ABI/testing/debugfs-ideapad +++ /dev/null @@ -1,19 +0,0 @@ -What: /sys/kernel/debug/ideapad/cfg -Date: Sep 2011 -KernelVersion: 3.2 -Contact: Ike Panhc <ike.pan@canonical.com> -Description: - -cfg shows the return value of _CFG method in VPC2004 device. It tells machine -capability and what graphic component within the machine. - - -What: /sys/kernel/debug/ideapad/status -Date: Sep 2011 -KernelVersion: 3.2 -Contact: Ike Panhc <ike.pan@canonical.com> -Description: - -status shows infos we can read and tells its meaning and value. - - diff --git a/Documentation/ABI/testing/debugfs-olpc b/Documentation/ABI/testing/debugfs-olpc deleted file mode 100644 index bd76cc6d55f..00000000000 --- a/Documentation/ABI/testing/debugfs-olpc +++ /dev/null @@ -1,16 +0,0 @@ -What: /sys/kernel/debug/olpc-ec/cmd -Date: Dec 2011 -KernelVersion: 3.4 -Contact: devel@lists.laptop.org -Description: - -A generic interface for executing OLPC Embedded Controller commands and -reading their responses. - -To execute a command, write data with the format: CC:N A A A A -CC is the (hex) command, N is the count of expected reply bytes, and A A A A -are optional (hex) arguments. - -To read the response (if any), read from the generic node after executing -a command. Hex reply bytes will be returned, *whether or not* they came from -the immediately previous command. diff --git a/Documentation/ABI/testing/debugfs-pfo-nx-crypto b/Documentation/ABI/testing/debugfs-pfo-nx-crypto deleted file mode 100644 index 685d5a44842..00000000000 --- a/Documentation/ABI/testing/debugfs-pfo-nx-crypto +++ /dev/null @@ -1,45 +0,0 @@ -What: /sys/kernel/debug/nx-crypto/* -Date: March 2012 -KernelVersion: 3.4 -Contact: Kent Yoder <key@linux.vnet.ibm.com> -Description: - - These debugfs interfaces are built by the nx-crypto driver, built in -arch/powerpc/crypto/nx. - -Error Detection -=============== - -errors: -- A u32 providing a total count of errors since the driver was loaded. The -only errors counted here are those returned from the hcall, H_COP_OP. - -last_error: -- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not -recorded here (the hcall will retry until -EBUSY goes away). - -last_error_pid: -- The process ID of the process who received the most recent error from the -hcall. - -Device Use -========== - -aes_bytes: -- The total number of bytes encrypted using AES in any of the driver's -supported modes. - -aes_ops: -- The total number of AES operations submitted to the hardware. - -sha256_bytes: -- The total number of bytes hashed by the hardware using SHA-256. - -sha256_ops: -- The total number of SHA-256 operations submitted to the hardware. - -sha512_bytes: -- The total number of bytes hashed by the hardware using SHA-512. - -sha512_ops: -- The total number of SHA-512 operations submitted to the hardware. diff --git a/Documentation/ABI/testing/debugfs-pktcdvd b/Documentation/ABI/testing/debugfs-pktcdvd deleted file mode 100644 index cf11736acb7..00000000000 --- a/Documentation/ABI/testing/debugfs-pktcdvd +++ /dev/null @@ -1,19 +0,0 @@ -What: /sys/kernel/debug/pktcdvd/pktcdvd[0-7] -Date: Oct. 2006 -KernelVersion: 2.6.20 -Contact: Thomas Maier <balagi@justmail.de> -Description: - -debugfs interface ------------------ - -The pktcdvd module (packet writing driver) creates -these files in debugfs: - -/sys/kernel/debug/pktcdvd/pktcdvd[0-7]/ - info (0444) Lots of driver statistics and infos. - -Example: -------- - -cat /sys/kernel/debug/pktcdvd/pktcdvd0/info diff --git a/Documentation/ABI/testing/dev-kmsg b/Documentation/ABI/testing/dev-kmsg deleted file mode 100644 index 281ecc5f970..00000000000 --- a/Documentation/ABI/testing/dev-kmsg +++ /dev/null @@ -1,90 +0,0 @@ -What: /dev/kmsg -Date: Mai 2012 -KernelVersion: 3.5 -Contact: Kay Sievers <kay@vrfy.org> -Description: The /dev/kmsg character device node provides userspace access - to the kernel's printk buffer. - - Injecting messages: - Every write() to the opened device node places a log entry in - the kernel's printk buffer. - - The logged line can be prefixed with a <N> syslog prefix, which - carries the syslog priority and facility. The single decimal - prefix number is composed of the 3 lowest bits being the syslog - priority and the higher bits the syslog facility number. - - If no prefix is given, the priority number is the default kernel - log priority and the facility number is set to LOG_USER (1). It - is not possible to inject messages from userspace with the - facility number LOG_KERN (0), to make sure that the origin of - the messages can always be reliably determined. - - Accessing the buffer: - Every read() from the opened device node receives one record - of the kernel's printk buffer. - - The first read() directly following an open() always returns - first message in the buffer; there is no kernel-internal - persistent state; many readers can concurrently open the device - and read from it, without affecting other readers. - - Every read() will receive the next available record. If no more - records are available read() will block, or if O_NONBLOCK is - used -EAGAIN returned. - - Messages in the record ring buffer get overwritten as whole, - there are never partial messages received by read(). - - In case messages get overwritten in the circular buffer while - the device is kept open, the next read() will return -EPIPE, - and the seek position be updated to the next available record. - Subsequent reads() will return available records again. - - Unlike the classic syslog() interface, the 64 bit record - sequence numbers allow to calculate the amount of lost - messages, in case the buffer gets overwritten. And they allow - to reconnect to the buffer and reconstruct the read position - if needed, without limiting the interface to a single reader. - - The device supports seek with the following parameters: - SEEK_SET, 0 - seek to the first entry in the buffer - SEEK_END, 0 - seek after the last entry in the buffer - SEEK_DATA, 0 - seek after the last record available at the time - the last SYSLOG_ACTION_CLEAR was issued. - - The output format consists of a prefix carrying the syslog - prefix including priority and facility, the 64 bit message - sequence number and the monotonic timestamp in microseconds. - The values are separated by a ','. Future extensions might - add more comma separated values before the terminating ';'. - Unknown values should be gracefully ignored. - - The human readable text string starts directly after the ';' - and is terminated by a '\n'. Untrusted values derived from - hardware or other facilities are printed, therefore - all non-printable characters in the log message are escaped - by "\x00" C-style hex encoding. - - A line starting with ' ', is a continuation line, adding - key/value pairs to the log message, which provide the machine - readable context of the message, for reliable processing in - userspace. - - Example: - 7,160,424069;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored) - SUBSYSTEM=acpi - DEVICE=+acpi:PNP0A03:00 - 6,339,5140900;NET: Registered protocol family 10 - 30,340,5690716;udevd[80]: starting version 181 - - The DEVICE= key uniquely identifies devices the following way: - b12:8 - block dev_t - c127:3 - char dev_t - n8 - netdev ifindex - +sound:card0 - subsystem:devname - -Users: dmesg(1), userspace kernel log consumers diff --git a/Documentation/ABI/testing/evm b/Documentation/ABI/testing/evm deleted file mode 100644 index 8374d4557e5..00000000000 --- a/Documentation/ABI/testing/evm +++ /dev/null @@ -1,23 +0,0 @@ -What: security/evm -Date: March 2011 -Contact: Mimi Zohar <zohar@us.ibm.com> -Description: - EVM protects a file's security extended attributes(xattrs) - against integrity attacks. The initial method maintains an - HMAC-sha1 value across the extended attributes, storing the - value as the extended attribute 'security.evm'. - - EVM depends on the Kernel Key Retention System to provide it - with a trusted/encrypted key for the HMAC-sha1 operation. - The key is loaded onto the root's keyring using keyctl. Until - EVM receives notification that the key has been successfully - loaded onto the keyring (echo 1 > <securityfs>/evm), EVM - can not create or validate the 'security.evm' xattr, but - returns INTEGRITY_UNKNOWN. Loading the key and signaling EVM - should be done as early as possible. Normally this is done - in the initramfs, which has already been measured as part - of the trusted boot. For more information on creating and - loading existing trusted/encrypted keys, refer to: - Documentation/keys-trusted-encrypted.txt. (A sample dracut - patch, which loads the trusted/encrypted key and enables - EVM, is available from http://linux-ima.sourceforge.net/#EVM.) diff --git a/Documentation/ABI/testing/ima_policy b/Documentation/ABI/testing/ima_policy deleted file mode 100644 index 6cd6daefaae..00000000000 --- a/Documentation/ABI/testing/ima_policy +++ /dev/null @@ -1,61 +0,0 @@ -What: security/ima/policy -Date: May 2008 -Contact: Mimi Zohar <zohar@us.ibm.com> -Description: - The Trusted Computing Group(TCG) runtime Integrity - Measurement Architecture(IMA) maintains a list of hash - values of executables and other sensitive system files - loaded into the run-time of this system. At runtime, - the policy can be constrained based on LSM specific data. - Policies are loaded into the securityfs file ima/policy - by opening the file, writing the rules one at a time and - then closing the file. The new policy takes effect after - the file ima/policy is closed. - - rule format: action [condition ...] - - action: measure | dont_measure - condition:= base | lsm - base: [[func=] [mask=] [fsmagic=] [uid=]] - lsm: [[subj_user=] [subj_role=] [subj_type=] - [obj_user=] [obj_role=] [obj_type=]] - - base: func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK] - mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] - fsmagic:= hex value - uid:= decimal value - lsm: are LSM specific - - default policy: - # PROC_SUPER_MAGIC - dont_measure fsmagic=0x9fa0 - # SYSFS_MAGIC - dont_measure fsmagic=0x62656572 - # DEBUGFS_MAGIC - dont_measure fsmagic=0x64626720 - # TMPFS_MAGIC - dont_measure fsmagic=0x01021994 - # SECURITYFS_MAGIC - dont_measure fsmagic=0x73636673 - - measure func=BPRM_CHECK - measure func=FILE_MMAP mask=MAY_EXEC - measure func=FILE_CHECK mask=MAY_READ uid=0 - - The default policy measures all executables in bprm_check, - all files mmapped executable in file_mmap, and all files - open for read by root in do_filp_open. - - Examples of LSM specific definitions: - - SELinux: - # SELINUX_MAGIC - dont_measure fsmagic=0xF97CFF8C - - dont_measure obj_type=var_log_t - dont_measure obj_type=auditd_log_t - measure subj_user=system_u func=FILE_CHECK mask=MAY_READ - measure subj_role=system_r func=FILE_CHECK mask=MAY_READ - - Smack: - measure subj_user=_ func=FILE_CHECK mask=MAY_READ diff --git a/Documentation/ABI/testing/procfs-diskstats b/Documentation/ABI/testing/procfs-diskstats deleted file mode 100644 index f91a973a37f..00000000000 --- a/Documentation/ABI/testing/procfs-diskstats +++ /dev/null @@ -1,22 +0,0 @@ -What: /proc/diskstats -Date: February 2008 -Contact: Jerome Marchand <jmarchan@redhat.com> -Description: - The /proc/diskstats file displays the I/O statistics - of block devices. Each line contains the following 14 - fields: - 1 - major number - 2 - minor mumber - 3 - device name - 4 - reads completed successfully - 5 - reads merged - 6 - sectors read - 7 - time spent reading (ms) - 8 - writes completed - 9 - writes merged - 10 - sectors written - 11 - time spent writing (ms) - 12 - I/Os currently in progress - 13 - time spent doing I/Os (ms) - 14 - weighted time spent doing I/Os (ms) - For more details refer to Documentation/iostats.txt diff --git a/Documentation/ABI/testing/pstore b/Documentation/ABI/testing/pstore deleted file mode 100644 index ff1df4e3b05..00000000000 --- a/Documentation/ABI/testing/pstore +++ /dev/null @@ -1,47 +0,0 @@ -Where: /dev/pstore/... -Date: March 2011 -Kernel Version: 2.6.39 -Contact: tony.luck@intel.com -Description: Generic interface to platform dependent persistent storage. - - Platforms that provide a mechanism to preserve some data - across system reboots can register with this driver to - provide a generic interface to show records captured in - the dying moments. In the case of a panic the last part - of the console log is captured, but other interesting - data can also be saved. - - # mount -t pstore -o kmsg_bytes=8000 - /dev/pstore - - $ ls -l /dev/pstore - total 0 - -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1 - - Different users of this interface will result in different - filename prefixes. Currently two are defined: - - "dmesg" - saved console log - "mce" - architecture dependent data from fatal h/w error - - Once the information in a file has been read, removing - the file will signal to the underlying persistent storage - device that it can reclaim the space for later re-use. - - $ rm /dev/pstore/dmesg-erst-1 - - The expectation is that all files in /dev/pstore - will be saved elsewhere and erased from persistent store - soon after boot to free up space ready for the next - catastrophe. - - The 'kmsg_bytes' mount option changes the target amount of - data saved on each oops/panic. Pstore saves (possibly - multiple) files based on the record size of the underlying - persistent storage until at least this amount is reached. - Default is 10 Kbytes. - - Pstore only supports one backend at a time. If multiple - backends are available, the preferred backend may be - set by passing the pstore.backend= argument to the kernel at - boot time. - diff --git a/Documentation/ABI/testing/sysfs-ata b/Documentation/ABI/testing/sysfs-ata deleted file mode 100644 index 0a932155cbb..00000000000 --- a/Documentation/ABI/testing/sysfs-ata +++ /dev/null @@ -1,99 +0,0 @@ -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-block b/Documentation/ABI/testing/sysfs-block deleted file mode 100644 index c1eb41cb987..00000000000 --- a/Documentation/ABI/testing/sysfs-block +++ /dev/null @@ -1,208 +0,0 @@ -What: /sys/block/<disk>/stat -Date: February 2008 -Contact: Jerome Marchand <jmarchan@redhat.com> -Description: - The /sys/block/<disk>/stat files displays the I/O - statistics of disk <disk>. They contain 11 fields: - 1 - reads completed successfully - 2 - reads merged - 3 - sectors read - 4 - time spent reading (ms) - 5 - writes completed - 6 - writes merged - 7 - sectors written - 8 - time spent writing (ms) - 9 - I/Os currently in progress - 10 - time spent doing I/Os (ms) - 11 - weighted time spent doing I/Os (ms) - For more details refer Documentation/iostats.txt - - -What: /sys/block/<disk>/<part>/stat -Date: February 2008 -Contact: Jerome Marchand <jmarchan@redhat.com> -Description: - The /sys/block/<disk>/<part>/stat files display the - I/O statistics of partition <part>. The format is the - same as the above-written /sys/block/<disk>/stat - format. - - -What: /sys/block/<disk>/integrity/format -Date: June 2008 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Metadata format for integrity capable block device. - E.g. T10-DIF-TYPE1-CRC. - - -What: /sys/block/<disk>/integrity/read_verify -Date: June 2008 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Indicates whether the block layer should verify the - integrity of read requests serviced by devices that - support sending integrity metadata. - - -What: /sys/block/<disk>/integrity/tag_size -Date: June 2008 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Number of bytes of integrity tag space available per - 512 bytes of data. - - -What: /sys/block/<disk>/integrity/write_generate -Date: June 2008 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Indicates whether the block layer should automatically - generate checksums for write requests bound for - devices that support receiving integrity metadata. - -What: /sys/block/<disk>/alignment_offset -Date: April 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Storage devices may report a physical block size that is - bigger than the logical block size (for instance a drive - with 4KB physical sectors exposing 512-byte logical - blocks to the operating system). This parameter - indicates how many bytes the beginning of the device is - offset from the disk's natural alignment. - -What: /sys/block/<disk>/<partition>/alignment_offset -Date: April 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Storage devices may report a physical block size that is - bigger than the logical block size (for instance a drive - with 4KB physical sectors exposing 512-byte logical - blocks to the operating system). This parameter - indicates how many bytes the beginning of the partition - is offset from the disk's natural alignment. - -What: /sys/block/<disk>/queue/logical_block_size -Date: May 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - This is the smallest unit the storage device can - address. It is typically 512 bytes. - -What: /sys/block/<disk>/queue/physical_block_size -Date: May 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - This is the smallest unit a physical storage device can - write atomically. It is usually the same as the logical - block size but may be bigger. One example is SATA - drives with 4KB sectors that expose a 512-byte logical - block size to the operating system. For stacked block - devices the physical_block_size variable contains the - maximum physical_block_size of the component devices. - -What: /sys/block/<disk>/queue/minimum_io_size -Date: April 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Storage devices may report a granularity or preferred - minimum I/O size which is the smallest request the - device can perform without incurring a performance - penalty. For disk drives this is often the physical - block size. For RAID arrays it is often the stripe - chunk size. A properly aligned multiple of - minimum_io_size is the preferred request size for - workloads where a high number of I/O operations is - desired. - -What: /sys/block/<disk>/queue/optimal_io_size -Date: April 2009 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Storage devices may report an optimal I/O size, which is - the device's preferred unit for sustained I/O. This is - rarely reported for disk drives. For RAID arrays it is - usually the stripe width or the internal track size. A - properly aligned multiple of optimal_io_size is the - preferred request size for workloads where sustained - throughput is desired. If no optimal I/O size is - reported this file contains 0. - -What: /sys/block/<disk>/queue/nomerges -Date: January 2010 -Contact: -Description: - Standard I/O elevator operations include attempts to - merge contiguous I/Os. For known random I/O loads these - attempts will always fail and result in extra cycles - being spent in the kernel. This allows one to turn off - this behavior on one of two ways: When set to 1, complex - merge checks are disabled, but the simple one-shot merges - with the previous I/O request are enabled. When set to 2, - all merge tries are disabled. The default value is 0 - - which enables all types of merge tries. - -What: /sys/block/<disk>/discard_alignment -Date: May 2011 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Devices that support discard functionality may - internally allocate space in units that are bigger than - the exported logical block size. The discard_alignment - parameter indicates how many bytes the beginning of the - device is offset from the internal allocation unit's - natural alignment. - -What: /sys/block/<disk>/<partition>/discard_alignment -Date: May 2011 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Devices that support discard functionality may - internally allocate space in units that are bigger than - the exported logical block size. The discard_alignment - parameter indicates how many bytes the beginning of the - partition is offset from the internal allocation unit's - natural alignment. - -What: /sys/block/<disk>/queue/discard_granularity -Date: May 2011 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Devices that support discard functionality may - internally allocate space using units that are bigger - than the logical block size. The discard_granularity - parameter indicates the size of the internal allocation - unit in bytes if reported by the device. Otherwise the - discard_granularity will be set to match the device's - physical block size. A discard_granularity of 0 means - that the device does not support discard functionality. - -What: /sys/block/<disk>/queue/discard_max_bytes -Date: May 2011 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Devices that support discard functionality may have - internal limits on the number of bytes that can be - trimmed or unmapped in a single operation. Some storage - protocols also have inherent limits on the number of - blocks that can be described in a single command. The - discard_max_bytes parameter is set by the device driver - to the maximum number of bytes that can be discarded in - a single operation. Discard requests issued to the - device must not exceed this limit. A discard_max_bytes - value of 0 means that the device does not support - discard functionality. - -What: /sys/block/<disk>/queue/discard_zeroes_data -Date: May 2011 -Contact: Martin K. Petersen <martin.petersen@oracle.com> -Description: - Devices that support discard functionality may return - stale or random data when a previously discarded block - is read back. This can cause problems if the filesystem - expects discarded blocks to be explicitly cleared. If a - device reports that it deterministically returns zeroes - when a discarded area is read the discard_zeroes_data - parameter will be set to one. Otherwise it will be 0 and - the result of reading a discarded area is undefined. diff --git a/Documentation/ABI/testing/sysfs-block-dm b/Documentation/ABI/testing/sysfs-block-dm deleted file mode 100644 index 87ca5691e29..00000000000 --- a/Documentation/ABI/testing/sysfs-block-dm +++ /dev/null @@ -1,25 +0,0 @@ -What: /sys/block/dm-<num>/dm/name -Date: January 2009 -KernelVersion: 2.6.29 -Contact: dm-devel@redhat.com -Description: Device-mapper device name. - Read-only string containing mapped device name. -Users: util-linux, device-mapper udev rules - -What: /sys/block/dm-<num>/dm/uuid -Date: January 2009 -KernelVersion: 2.6.29 -Contact: dm-devel@redhat.com -Description: Device-mapper device UUID. - Read-only string containing DM-UUID or empty string - if DM-UUID is not set. -Users: util-linux, device-mapper udev rules - -What: /sys/block/dm-<num>/dm/suspended -Date: June 2009 -KernelVersion: 2.6.31 -Contact: dm-devel@redhat.com -Description: Device-mapper device suspend state. - Contains the value 1 while the device is suspended. - Otherwise it contains 0. Read-only attribute. -Users: util-linux, device-mapper udev rules diff --git a/Documentation/ABI/testing/sysfs-block-rssd b/Documentation/ABI/testing/sysfs-block-rssd deleted file mode 100644 index beef30c046b..00000000000 --- a/Documentation/ABI/testing/sysfs-block-rssd +++ /dev/null @@ -1,5 +0,0 @@ -What: /sys/block/rssd*/status -Date: April 2012 -KernelVersion: 3.4 -Contact: Asai Thambi S P <asamymuthupa@micron.com> -Description: This is a read-only file. Indicates the status of the device. diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram deleted file mode 100644 index c8b3b48ec62..00000000000 --- a/Documentation/ABI/testing/sysfs-block-zram +++ /dev/null @@ -1,99 +0,0 @@ -What: /sys/block/zram<id>/disksize -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The disksize file is read-write and specifies the disk size - which represents the limit on the *uncompressed* worth of data - that can be stored in this disk. - -What: /sys/block/zram<id>/initstate -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The disksize file is read-only and shows the initialization - state of the device. - -What: /sys/block/zram<id>/reset -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The disksize file is write-only and allows resetting the - device. The reset operation frees all the memory assocaited - with this device. - -What: /sys/block/zram<id>/num_reads -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The num_reads file is read-only and specifies the number of - reads (failed or successful) done on this device. - -What: /sys/block/zram<id>/num_writes -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The num_writes file is read-only and specifies the number of - writes (failed or successful) done on this device. - -What: /sys/block/zram<id>/invalid_io -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The invalid_io file is read-only and specifies the number of - non-page-size-aligned I/O requests issued to this device. - -What: /sys/block/zram<id>/notify_free -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The notify_free file is read-only and specifies the number of - swap slot free notifications received by this device. These - notifications are send to a swap block device when a swap slot - is freed. This statistic is applicable only when this disk is - being used as a swap disk. - -What: /sys/block/zram<id>/discard -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The discard file is read-only and specifies the number of - discard requests received by this device. These requests - provide information to block device regarding blocks which are - no longer used by filesystem. - -What: /sys/block/zram<id>/zero_pages -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The zero_pages file is read-only and specifies number of zero - filled pages written to this disk. No memory is allocated for - such pages. - -What: /sys/block/zram<id>/orig_data_size -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The orig_data_size file is read-only and specifies uncompressed - size of data stored in this disk. This excludes zero-filled - pages (zero_pages) since no memory is allocated for them. - Unit: bytes - -What: /sys/block/zram<id>/compr_data_size -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The compr_data_size file is read-only and specifies compressed - size of data stored in this disk. So, compression ratio can be - calculated using orig_data_size and this statistic. - Unit: bytes - -What: /sys/block/zram<id>/mem_used_total -Date: August 2010 -Contact: Nitin Gupta <ngupta@vflare.org> -Description: - The mem_used_total file is read-only and specifies the amount - of memory, including allocator fragmentation and metadata - 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 diff --git a/Documentation/ABI/testing/sysfs-bus-bcma b/Documentation/ABI/testing/sysfs-bus-bcma deleted file mode 100644 index 721b4aea302..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-bcma +++ /dev/null @@ -1,31 +0,0 @@ -What: /sys/bus/bcma/devices/.../manuf -Date: May 2011 -KernelVersion: 3.0 -Contact: Rafał Miłecki <zajec5@gmail.com> -Description: - Each BCMA core has it's manufacturer id. See - include/linux/bcma/bcma.h for possible values. - -What: /sys/bus/bcma/devices/.../id -Date: May 2011 -KernelVersion: 3.0 -Contact: Rafał Miłecki <zajec5@gmail.com> -Description: - There are a few types of BCMA cores, they can be identified by - id field. - -What: /sys/bus/bcma/devices/.../rev -Date: May 2011 -KernelVersion: 3.0 -Contact: Rafał Miłecki <zajec5@gmail.com> -Description: - BCMA cores of the same type can still slightly differ depending - on their revision. Use it for detailed programming. - -What: /sys/bus/bcma/devices/.../class -Date: May 2011 -KernelVersion: 3.0 -Contact: Rafał Miłecki <zajec5@gmail.com> -Description: - Each BCMA core is identified by few fields, including class it - belongs to. See include/linux/bcma/bcma.h for possible values. diff --git a/Documentation/ABI/testing/sysfs-bus-css b/Documentation/ABI/testing/sysfs-bus-css deleted file mode 100644 index 2979c40c10e..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-css +++ /dev/null @@ -1,35 +0,0 @@ -What: /sys/bus/css/devices/.../type -Date: March 2008 -Contact: Cornelia Huck <cornelia.huck@de.ibm.com> - linux-s390@vger.kernel.org -Description: Contains the subchannel type, as reported by the hardware. - This attribute is present for all subchannel types. - -What: /sys/bus/css/devices/.../modalias -Date: March 2008 -Contact: Cornelia Huck <cornelia.huck@de.ibm.com> - linux-s390@vger.kernel.org -Description: Contains the module alias as reported with uevents. - It is of the format css:t<type> and present for all - subchannel types. - -What: /sys/bus/css/drivers/io_subchannel/.../chpids -Date: December 2002 -Contact: Cornelia Huck <cornelia.huck@de.ibm.com> - linux-s390@vger.kernel.org -Description: Contains the ids of the channel paths used by this - subchannel, as reported by the channel subsystem - during subchannel recognition. - Note: This is an I/O-subchannel specific attribute. -Users: s390-tools, HAL - -What: /sys/bus/css/drivers/io_subchannel/.../pimpampom -Date: December 2002 -Contact: Cornelia Huck <cornelia.huck@de.ibm.com> - linux-s390@vger.kernel.org -Description: Contains the PIM/PAM/POM values, as reported by the - channel subsystem when last queried by the common I/O - layer (this implies that this attribute is not necessarily - in sync with the values current in the channel subsystem). - Note: This is an I/O-subchannel specific attribute. -Users: s390-tools, HAL diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-format b/Documentation/ABI/testing/sysfs-bus-event_source-devices-format deleted file mode 100644 index 079afc71363..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-format +++ /dev/null @@ -1,14 +0,0 @@ -Where: /sys/bus/event_source/devices/<dev>/format -Date: January 2012 -Kernel Version: 3.3 -Contact: Jiri Olsa <jolsa@redhat.com> -Description: - Attribute group to describe the magic bits that go into - perf_event_attr::config[012] for a particular pmu. - Each attribute of this group defines the 'hardware' bitmask - we want to export, so that userspace can deal with sane - name/value pairs. - - Example: 'config1:1,6-10,44' - Defines contents of attribute that occupies bits 1,6-10,44 of - perf_event_attr::config1. diff --git a/Documentation/ABI/testing/sysfs-bus-fcoe b/Documentation/ABI/testing/sysfs-bus-fcoe deleted file mode 100644 index 469d09c02f6..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-fcoe +++ /dev/null @@ -1,77 +0,0 @@ -What: /sys/bus/fcoe/ctlr_X -Date: March 2012 -KernelVersion: TBD -Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org -Description: 'FCoE Controller' instances on the fcoe bus -Attributes: - - fcf_dev_loss_tmo: Device loss timeout peroid (see below). Changing - this value will change the dev_loss_tmo for all - FCFs discovered by this controller. - - lesb_link_fail: Link Error Status Block (LESB) link failure count. - - lesb_vlink_fail: Link Error Status Block (LESB) virtual link - failure count. - - lesb_miss_fka: Link Error Status Block (LESB) missed FCoE - Initialization Protocol (FIP) Keep-Alives (FKA). - - lesb_symb_err: Link Error Status Block (LESB) symbolic error count. - - lesb_err_block: Link Error Status Block (LESB) block error count. - - lesb_fcs_error: Link Error Status Block (LESB) Fibre Channel - Serivces error count. - -Notes: ctlr_X (global increment starting at 0) - -What: /sys/bus/fcoe/fcf_X -Date: March 2012 -KernelVersion: TBD -Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org -Description: 'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel - Forwarder, which is a FCoE switch that can accept FCoE - (Ethernet) packets, unpack them, and forward the embedded - Fibre Channel frames into a FC fabric. It can also take - outbound FC frames and pack them in Ethernet packets to - be sent to their destination on the Ethernet segment. -Attributes: - - fabric_name: Identifies the fabric that the FCF services. - - switch_name: Identifies the FCF. - - priority: The switch's priority amongst other FCFs on the same - fabric. - - selected: 1 indicates that the switch has been selected for use; - 0 indicates that the swich will not be used. - - fc_map: The Fibre Channel MAP - - vfid: The Virtual Fabric ID - - mac: The FCF's MAC address - - fka_peroid: The FIP Keep-Alive peroid - - fabric_state: The internal kernel state - "Unknown" - Initialization value - "Disconnected" - No link to the FCF/fabric - "Connected" - Host is connected to the FCF - "Deleted" - FCF is being removed from the system - - dev_loss_tmo: The device loss timeout peroid for this FCF. - -Notes: A device loss infrastructre similar to the FC Transport's - is present in fcoe_sysfs. It is nice to have so that a - link flapping adapter doesn't continually advance the count - used to identify the discovered FCF. FCFs will exist in a - "Disconnected" state until either the timer expires and the - FCF becomes "Deleted" or the FCF is rediscovered and becomes - "Connected." - - -Users: The first user of this interface will be the fcoeadm application, - which is commonly packaged in the fcoe-utils package. diff --git a/Documentation/ABI/testing/sysfs-bus-hsi b/Documentation/ABI/testing/sysfs-bus-hsi deleted file mode 100644 index 1b1b282a99e..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-hsi +++ /dev/null @@ -1,19 +0,0 @@ -What: /sys/bus/hsi -Date: April 2012 -KernelVersion: 3.4 -Contact: Carlos Chinea <carlos.chinea@nokia.com> -Description: - High Speed Synchronous Serial Interface (HSI) is a - serial interface mainly used for connecting application - engines (APE) with cellular modem engines (CMT) in cellular - handsets. - The bus will be populated with devices (hsi_clients) representing - the protocols available in the system. Bus drivers implement - those protocols. - -What: /sys/bus/hsi/devices/.../modalias -Date: April 2012 -KernelVersion: 3.4 -Contact: Carlos Chinea <carlos.chinea@nokia.com> -Description: Stores the same MODALIAS value emitted by uevent - Format: hsi:<hsi_client device name> diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 deleted file mode 100644 index 9de269bb0ae..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 +++ /dev/null @@ -1,21 +0,0 @@ -What: /sys/bus/i2c/devices/.../device -Date: February 2011 -Contact: Minkyu Kang <mk7.kang@samsung.com> -Description: - show what device is attached - NONE - no device - USB - USB device is attached - UART - UART is attached - CHARGER - Charger is attaced - JIG - JIG is attached - -What: /sys/bus/i2c/devices/.../switch -Date: February 2011 -Contact: Minkyu Kang <mk7.kang@samsung.com> -Description: - show or set the state of manual switch - VAUDIO - switch to VAUDIO path - UART - switch to UART path - AUDIO - switch to AUDIO path - DHOST - switch to DHOST path - AUTO - switch automatically by device diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 deleted file mode 100644 index feb2e4a8707..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 +++ /dev/null @@ -1,21 +0,0 @@ -Where: /sys/bus/i2c/devices/.../heading0_input -Date: April 2010 -Kernel Version: 2.6.36? -Contact: alan.cox@intel.com -Description: Reports the current heading from the compass as a floating - point value in degrees. - -Where: /sys/bus/i2c/devices/.../power_state -Date: April 2010 -Kernel Version: 2.6.36? -Contact: alan.cox@intel.com -Description: Sets the power state of the device. 0 sets the device into - sleep mode, 1 wakes it up. - -Where: /sys/bus/i2c/devices/.../calibration -Date: April 2010 -Kernel Version: 2.6.36? -Contact: alan.cox@intel.com -Description: Sets the calibration on or off (1 = on, 0 = off). See the - chip data sheet. - diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 deleted file mode 100644 index 1b62230b33b..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533 +++ /dev/null @@ -1,15 +0,0 @@ -What: /sys/bus/i2c/devices/.../output_hvled[n] -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the controlling backlight device for high-voltage current - sink HVLED[n] (n = 1, 2) (0, 1). - -What: /sys/bus/i2c/devices/.../output_lvled[n] -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the controlling led device for low-voltage current sink - LVLED[n] (n = 1..5) (0..3). diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio deleted file mode 100644 index cfedf63cce1..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-iio +++ /dev/null @@ -1,768 +0,0 @@ -What: /sys/bus/iio/devices/iio:deviceX -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Hardware chip or device accessed by one communication port. - Corresponds to a grouping of sensor channels. X is the IIO - index of the device. - -What: /sys/bus/iio/devices/triggerX -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - An event driven driver of data capture to an in kernel buffer. - May be provided by a device driver that also has an IIO device - based on hardware generated events (e.g. data ready) or - provided by a separate driver for other hardware (e.g. - periodic timer, GPIO or high resolution timer). - Contains trigger type specific elements. These do not - generalize well and hence are not documented in this file. - X is the IIO index of the trigger. - -What: /sys/bus/iio/devices/iio:deviceX/buffer -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Directory of attributes relating to the buffer for the device. - -What: /sys/bus/iio/devices/iio:deviceX/name -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Description of the physical chip / device for device X. - Typically a part number. - -What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency -What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency -What: /sys/bus/iio/devices/triggerX/sampling_frequency -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Some devices have internal clocks. This parameter sets the - resulting sampling frequency. In many devices this - parameter has an effect on input filters etc rather than - simply controlling when the input is sampled. As this - effects datardy triggers, hardware buffers and the sysfs - direct access interfaces, it may be found in any of the - relevant directories. If it effects all of the above - then it is to be found in the base device directory. - -What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available -What: /sys/.../iio:deviceX/buffer/sampling_frequency_available -What: /sys/bus/iio/devices/triggerX/sampling_frequency_available -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - When the internal sampling clock can only take a small - discrete set of values, this file lists those available. - -What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Hardware dependent ADC oversampling. Controls the sampling ratio - of the digital filter if available. - -What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Hardware dependent values supported by the oversampling filter. - -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Raw (unscaled no bias removal etc) voltage measurement from - channel Y. In special cases where the channel does not - correspond to externally available input one of the named - versions may be used. The number must always be specified and - unique to allow association with event codes. Units after - application of scale and offset are microvolts. - -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Raw (unscaled) differential voltage measurement equivalent to - channel Y - channel Z where these channel numbers apply to the - physically equivalent inputs when non differential readings are - separately available. In differential only parts, then all that - is required is a consistent labeling. Units after application - of scale and offset are microvolts. - -What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw -KernelVersion: 3.2 -Contact: linux-iio@vger.kernel.org -Description: - Raw capacitance measurement from channel Y. Units after - application of scale and offset are nanofarads. - -What: /sys/.../iio:deviceX/in_capacitanceY-in_capacitanceZ_raw -KernelVersion: 3.2 -Contact: linux-iio@vger.kernel.org -Description: - Raw differential capacitance measurement equivalent to - channel Y - channel Z where these channel numbers apply to the - physically equivalent inputs when non differential readings are - separately available. In differential only parts, then all that - is required is a consistent labeling. Units after application - of scale and offset are nanofarads. - -What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw -What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw -What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw -What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw -What: /sys/bus/iio/devices/iio:deviceX/in_temp_z_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Raw (unscaled no bias removal etc) temperature measurement. - If an axis is specified it generally means that the temperature - sensor is associated with one part of a compound device (e.g. - a gyroscope axis). Units after application of scale and offset - are milli degrees Celsuis. - -What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Scaled temperature measurement in milli degrees Celsius. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw -What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_raw -What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Acceleration in direction x, y or z (may be arbitrarily assigned - but should match other such assignments on device). - Has all of the equivalent parameters as per voltageY. Units - after application of scale and offset are m/s^2. - -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_raw -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_raw -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Angular velocity about axis x, y or z (may be arbitrarily - assigned) Data converted by application of offset then scale to - radians per second. Has all the equivalent parameters as - per voltageY. Units after application of scale and offset are - radians per second. - -What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw -What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw -What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Inclination raw reading about axis x, y or z (may be - arbitrarily assigned). Data converted by application of offset - and scale to Degrees. - -What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw -What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw -What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Magnetic field along axis x, y or z (may be arbitrarily - assigned). Data converted by application of offset - then scale to Gauss. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw -What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw -What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw -KernelVersion: 2.6.36 -Contact: linux-iio@vger.kernel.org -Description: - Highest value since some reset condition. These - attributes allow access to this and are otherwise - the direct equivalent of the <type>Y[_name]_raw attributes. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw -KernelVersion: 2.6.36 -Contact: linux-iio@vger.kernel.org -Description: - A computed peak value based on the sum squared magnitude of - the underlying value in the specified directions. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset -What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset -What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset -What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset -What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset -What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset -What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - If known for a device, offset to be added to <type>[Y]_raw prior - to scaling by <type>[Y]_scale in order to obtain value in the - <type> units as specified in <type>[y]_raw documentation. - Not present if the offset is always 0 or unknown. If Y or - axis <x|y|z> is not present, then the offset applies to all - in channels of <type>. - May be writable if a variable offset can be applied on the - device. Note that this is different to calibbias which - is for devices (or drivers) that apply offsets to compensate - for variation between different instances of the part, typically - adjusted by using some hardware supported calibration procedure. - Calibbias is applied internally, offset is applied in userspace - to the _raw output. - -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale -What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale -What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale -What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale -What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale -What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale -What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale -What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale -What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale -What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - If known for a device, scale to be applied to <type>Y[_name]_raw - post addition of <type>[Y][_name]_offset in order to obtain the - measured value in <type> units as specified in - <type>[Y][_name]_raw documentation. If shared across all in - channels then Y and <x|y|z> are not present and the value is - called <type>[Y][_name]_scale. The peak modifier means this - value is applied to <type>Y[_name]_peak_raw values. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias -What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Hardware applied calibration offset. (assumed to fix production - inaccuracies). - -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale -What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale -what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale -what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Hardware applied calibration scale factor. (assumed to fix - production inaccuracies). If shared across all channels, - <type>_calibscale is used. - -What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available -What: /sys/.../iio:deviceX/in_voltageX_scale_available -What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available -What: /sys/.../iio:deviceX/out_voltageX_scale_available -What: /sys/.../iio:deviceX/out_altvoltageX_scale_available -What: /sys/.../iio:deviceX/in_capacitance_scale_available -KernelVersion: 2.635 -Contact: linux-iio@vger.kernel.org -Description: - If a discrete set of scale values are available, they - are listed in this attribute. - -What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Hardware applied gain factor. If shared across all channels, - <type>_hardwaregain is used. - -What: /sys/.../in_accel_filter_low_pass_3db_frequency -What: /sys/.../in_magn_filter_low_pass_3db_frequency -What: /sys/.../in_anglvel_filter_low_pass_3db_frequency -KernelVersion: 3.2 -Contact: linux-iio@vger.kernel.org -Description: - If a known or controllable low pass filter is applied - to the underlying data channel, then this parameter - gives the 3dB frequency of the filter in Hz. - -What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Raw (unscaled, no bias etc.) output voltage for - channel Y. The number must always be specified and - unique if the output corresponds to a single channel. - While DAC like devices typically use out_voltage, - a continuous frequency generating device, such as - a DDS or PLL should use out_altvoltage. - -What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Raw (unscaled, no bias etc.) output voltage for an aggregate of - channel Y, channel Z, etc. This interface is available in cases - where a single output sets the value for multiple channels - simultaneously. - -What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode -What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Specifies the output powerdown mode. - DAC output stage is disconnected from the amplifier and - 1kohm_to_gnd: connected to ground via an 1kOhm resistor - 100kohm_to_gnd: connected to ground via an 100kOhm resistor - three_state: left floating - For a list of available output power down options read - outX_powerdown_mode_available. If Y is not present the - mode is shared across all outputs. - -What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available -What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available -What: /sys/.../iio:deviceX/out_altvotlageY_powerdown_mode_available -What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Lists all available output power down modes. - If Y is not present the mode is shared across all outputs. - -What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown -What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - Writing 1 causes output Y to enter the power down mode specified - by the corresponding outY_powerdown_mode. Clearing returns to - normal operation. Y may be suppressed if all outputs are - controlled together. - -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency -KernelVersion: 3.4.0 -Contact: linux-iio@vger.kernel.org -Description: - Output frequency for channel Y in Hz. The number must always be - specified and unique if the output corresponds to a single - channel. - -What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase -KernelVersion: 3.4.0 -Contact: linux-iio@vger.kernel.org -Description: - Phase in radians of one frequency/clock output Y - (out_altvoltageY) relative to another frequency/clock output - (out_altvoltageZ) of the device X. The number must always be - specified and unique if the output corresponds to a single - channel. - -What: /sys/bus/iio/devices/iio:deviceX/events -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Configuration of which hardware generated events are passed up - to user-space. - -What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en -What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en -What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Event generated when channel passes a threshold in the specified - (_rising|_falling) direction. If the direction is not specified, - then either the device will report an event which ever direction - a single threshold value is passed in (e.g. - <type>[Y][_name]_<raw|input>_thresh_value) or - <type>[Y][_name]_<raw|input>_thresh_rising_value and - <type>[Y][_name]_<raw|input>_thresh_falling_value may take - different values, but the device can only enable both thresholds - or neither. - Note the driver will assume the last p events requested are - to be enabled where p is however many it supports (which may - vary depending on the exact set requested. So if you want to be - sure you have set what you think you have, check the contents of - these attributes after everything is configured. Drivers may - have to buffer any parameters so that they are consistent when - a given event type is enabled a future point (and not those for - whatever event was previously enabled). - -What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en -What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en -What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en -What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en -What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en -What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en -What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en -What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en -What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en -What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en -What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en -What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en -What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en -What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en -What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en -What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en -What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en -What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en -What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en -What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Event generated when channel passes a threshold on the rate of - change (1st differential) in the specified (_rising|_falling) - direction. If the direction is not specified, then either the - device will report an event which ever direction a single - threshold value is passed in (e.g. - <type>[Y][_name]_<raw|input>_roc_value) or - <type>[Y][_name]_<raw|input>_roc_rising_value and - <type>[Y][_name]_<raw|input>_roc_falling_value may take - different values, but the device can only enable both rate of - change thresholds or neither. - Note the driver will assume the last p events requested are - to be enabled where p is however many it supports (which may - vary depending on the exact set requested. So if you want to be - sure you have set what you think you have, check the contents of - these attributes after everything is configured. Drivers may - have to buffer any parameters so that they are consistent when - a given event type is enabled a future point (and not those for - whatever event was previously enabled). - -What: /sys/.../events/in_accel_x_raw_thresh_rising_value -What: /sys/.../events/in_accel_x_raw_thresh_falling_value -What: /sys/.../events/in_accel_y_raw_thresh_rising_value -What: /sys/.../events/in_accel_y_raw_thresh_falling_value -What: /sys/.../events/in_accel_z_raw_thresh_rising_value -What: /sys/.../events/in_accel_z_raw_thresh_falling_value -What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value -What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value -What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value -What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value -What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value -What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value -What: /sys/.../events/in_magn_x_raw_thresh_rising_value -What: /sys/.../events/in_magn_x_raw_thresh_falling_value -What: /sys/.../events/in_magn_y_raw_thresh_rising_value -What: /sys/.../events/in_magn_y_raw_thresh_falling_value -What: /sys/.../events/in_magn_z_raw_thresh_rising_value -What: /sys/.../events/in_magn_z_raw_thresh_falling_value -What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value -What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value -What: /sys/.../events/in_voltageY_raw_thresh_rising_value -What: /sys/.../events/in_voltageY_raw_thresh_falling_value -What: /sys/.../events/in_tempY_raw_thresh_rising_value -What: /sys/.../events/in_tempY_raw_thresh_falling_value -What: /sys/.../events/in_illuminance0_thresh_falling_value -what: /sys/.../events/in_illuminance0_thresh_rising_value -what: /sys/.../events/in_proximity0_thresh_falling_value -what: /sys/.../events/in_proximity0_thresh_rising_value -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Specifies the value of threshold that the device is comparing - against for the events enabled by - <type>Y[_name]_thresh[_rising|falling]_en. - If separate attributes exist for the two directions, but - direction is not specified for this attribute, then a single - threshold value applies to both directions. - The raw or input element of the name indicates whether the - value is in raw device units or in processed units (as _raw - and _input do on sysfs direct channel read attributes). - -What: /sys/.../events/in_accel_x_raw_roc_rising_value -What: /sys/.../events/in_accel_x_raw_roc_falling_value -What: /sys/.../events/in_accel_y_raw_roc_rising_value -What: /sys/.../events/in_accel_y_raw_roc_falling_value -What: /sys/.../events/in_accel_z_raw_roc_rising_value -What: /sys/.../events/in_accel_z_raw_roc_falling_value -What: /sys/.../events/in_anglvel_x_raw_roc_rising_value -What: /sys/.../events/in_anglvel_x_raw_roc_falling_value -What: /sys/.../events/in_anglvel_y_raw_roc_rising_value -What: /sys/.../events/in_anglvel_y_raw_roc_falling_value -What: /sys/.../events/in_anglvel_z_raw_roc_rising_value -What: /sys/.../events/in_anglvel_z_raw_roc_falling_value -What: /sys/.../events/in_magn_x_raw_roc_rising_value -What: /sys/.../events/in_magn_x_raw_roc_falling_value -What: /sys/.../events/in_magn_y_raw_roc_rising_value -What: /sys/.../events/in_magn_y_raw_roc_falling_value -What: /sys/.../events/in_magn_z_raw_roc_rising_value -What: /sys/.../events/in_magn_z_raw_roc_falling_value -What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value -What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value -What: /sys/.../events/in_voltageY_raw_roc_rising_value -What: /sys/.../events/in_voltageY_raw_roc_falling_value -What: /sys/.../events/in_tempY_raw_roc_rising_value -What: /sys/.../events/in_tempY_raw_roc_falling_value -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Specifies the value of rate of change threshold that the - device is comparing against for the events enabled by - <type>[Y][_name]_roc[_rising|falling]_en. - If separate attributes exist for the two directions, - but direction is not specified for this attribute, - then a single threshold value applies to both directions. - The raw or input element of the name indicates whether the - value is in raw device units or in processed units (as _raw - and _input do on sysfs direct channel read attributes). - -What: /sys/.../events/in_accel_x_thresh_rising_period -What: /sys/.../events/in_accel_x_thresh_falling_period -hat: /sys/.../events/in_accel_x_roc_rising_period -What: /sys/.../events/in_accel_x_roc_falling_period -What: /sys/.../events/in_accel_y_thresh_rising_period -What: /sys/.../events/in_accel_y_thresh_falling_period -What: /sys/.../events/in_accel_y_roc_rising_period -What: /sys/.../events/in_accel_y_roc_falling_period -What: /sys/.../events/in_accel_z_thresh_rising_period -What: /sys/.../events/in_accel_z_thresh_falling_period -What: /sys/.../events/in_accel_z_roc_rising_period -What: /sys/.../events/in_accel_z_roc_falling_period -What: /sys/.../events/in_anglvel_x_thresh_rising_period -What: /sys/.../events/in_anglvel_x_thresh_falling_period -What: /sys/.../events/in_anglvel_x_roc_rising_period -What: /sys/.../events/in_anglvel_x_roc_falling_period -What: /sys/.../events/in_anglvel_y_thresh_rising_period -What: /sys/.../events/in_anglvel_y_thresh_falling_period -What: /sys/.../events/in_anglvel_y_roc_rising_period -What: /sys/.../events/in_anglvel_y_roc_falling_period -What: /sys/.../events/in_anglvel_z_thresh_rising_period -What: /sys/.../events/in_anglvel_z_thresh_falling_period -What: /sys/.../events/in_anglvel_z_roc_rising_period -What: /sys/.../events/in_anglvel_z_roc_falling_period -What: /sys/.../events/in_magn_x_thresh_rising_period -What: /sys/.../events/in_magn_x_thresh_falling_period -What: /sys/.../events/in_magn_x_roc_rising_period -What: /sys/.../events/in_magn_x_roc_falling_period -What: /sys/.../events/in_magn_y_thresh_rising_period -What: /sys/.../events/in_magn_y_thresh_falling_period -What: /sys/.../events/in_magn_y_roc_rising_period -What: /sys/.../events/in_magn_y_roc_falling_period -What: /sys/.../events/in_magn_z_thresh_rising_period -What: /sys/.../events/in_magn_z_thresh_falling_period -What: /sys/.../events/in_magn_z_roc_rising_period -What: /sys/.../events/in_magn_z_roc_falling_period -What: /sys/.../events/in_voltageY_supply_thresh_rising_period -What: /sys/.../events/in_voltageY_supply_thresh_falling_period -What: /sys/.../events/in_voltageY_supply_roc_rising_period -What: /sys/.../events/in_voltageY_supply_roc_falling_period -What: /sys/.../events/in_voltageY_thresh_rising_period -What: /sys/.../events/in_voltageY_thresh_falling_period -What: /sys/.../events/in_voltageY_roc_rising_period -What: /sys/.../events/in_voltageY_roc_falling_period -What: /sys/.../events/in_tempY_thresh_rising_period -What: /sys/.../events/in_tempY_thresh_falling_period -What: /sys/.../events/in_tempY_roc_rising_period -What: /sys/.../events/in_tempY_roc_falling_period -What: /sys/.../events/in_accel_x&y&z_mag_falling_period -What: /sys/.../events/in_intensity0_thresh_period -What: /sys/.../events/in_proximity0_thresh_period -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Period of time (in seconds) for which the condition must be - met before an event is generated. If direction is not - specified then this period applies to both directions. - -What: /sys/.../iio:deviceX/events/in_accel_mag_en -What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en -What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en -What: /sys/.../iio:deviceX/events/in_accel_x_mag_en -What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en -What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en -What: /sys/.../iio:deviceX/events/in_accel_y_mag_en -What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en -What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en -What: /sys/.../iio:deviceX/events/in_accel_z_mag_en -What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en -What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en -What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en -What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Similar to in_accel_x_thresh[_rising|_falling]_en, but here the - magnitude of the channel is compared to the threshold, not its - signed value. - -What: /sys/.../events/in_accel_raw_mag_value -What: /sys/.../events/in_accel_x_raw_mag_rising_value -What: /sys/.../events/in_accel_y_raw_mag_rising_value -What: /sys/.../events/in_accel_z_raw_mag_rising_value -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - The value to which the magnitude of the channel is compared. If - number or direction is not specified, applies to all channels of - this type. - -What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - The name of the trigger source being used, as per string given - in /sys/class/iio/triggerY/name. - -What: /sys/bus/iio/devices/iio:deviceX/buffer/length -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Number of scans contained by the buffer. - -What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Bytes per scan. Due to alignment fun, the scan may be larger - than implied directly by the scan_element parameters. - -What: /sys/bus/iio/devices/iio:deviceX/buffer/enable -KernelVersion: 2.6.35 -Contact: linux-iio@vger.kernel.org -Description: - Actually start the buffer capture up. Will start trigger - if first device and appropriate. - -What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Directory containing interfaces for elements that will be - captured for a single triggered sample set in the buffer. - -What: /sys/.../buffer/scan_elements/in_accel_x_en -What: /sys/.../buffer/scan_elements/in_accel_y_en -What: /sys/.../buffer/scan_elements/in_accel_z_en -What: /sys/.../buffer/scan_elements/in_anglvel_x_en -What: /sys/.../buffer/scan_elements/in_anglvel_y_en -What: /sys/.../buffer/scan_elements/in_anglvel_z_en -What: /sys/.../buffer/scan_elements/in_magn_x_en -What: /sys/.../buffer/scan_elements/in_magn_y_en -What: /sys/.../buffer/scan_elements/in_magn_z_en -What: /sys/.../buffer/scan_elements/in_timestamp_en -What: /sys/.../buffer/scan_elements/in_voltageY_supply_en -What: /sys/.../buffer/scan_elements/in_voltageY_en -What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en -What: /sys/.../buffer/scan_elements/in_incli_x_en -What: /sys/.../buffer/scan_elements/in_incli_y_en -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Scan element control for triggered data capture. - -What: /sys/.../buffer/scan_elements/in_accel_type -What: /sys/.../buffer/scan_elements/in_anglvel_type -What: /sys/.../buffer/scan_elements/in_magn_type -What: /sys/.../buffer/scan_elements/in_incli_type -What: /sys/.../buffer/scan_elements/in_voltageY_type -What: /sys/.../buffer/scan_elements/in_voltage-in_type -What: /sys/.../buffer/scan_elements/in_voltageY_supply_type -What: /sys/.../buffer/scan_elements/in_timestamp_type -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - Description of the scan element data storage within the buffer - and hence the form in which it is read from user-space. - Form is [be|le]:[s|u]bits/storagebits[>>shift]. - be or le specifies big or little endian. s or u specifies if - signed (2's complement) or unsigned. bits is the number of bits - of data and storagebits is the space (after padding) that it - occupies in the buffer. shift if specified, is the shift that - needs to be applied prior to masking out unused bits. Some - devices put their data in the middle of the transferred elements - with additional information on both sides. Note that some - devices will have additional information in the unused bits - so to get a clean value, the bits value must be used to mask - the buffer output value appropriately. The storagebits value - also specifies the data alignment. So s48/64>>2 will be a - signed 48 bit integer stored in a 64 bit location aligned to - a a64 bit boundary. To obtain the clean value, shift right 2 - and apply a mask to zero the top 16 bits of the result. - For other storage combinations this attribute will be extended - appropriately. - -What: /sys/.../buffer/scan_elements/in_accel_type_available -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - If the type parameter can take one of a small set of values, - this attribute lists them. - -What: /sys/.../buffer/scan_elements/in_voltageY_index -What: /sys/.../buffer/scan_elements/in_voltageY_supply_index -What: /sys/.../buffer/scan_elements/in_accel_x_index -What: /sys/.../buffer/scan_elements/in_accel_y_index -What: /sys/.../buffer/scan_elements/in_accel_z_index -What: /sys/.../buffer/scan_elements/in_anglvel_x_index -What: /sys/.../buffer/scan_elements/in_anglvel_y_index -What: /sys/.../buffer/scan_elements/in_anglvel_z_index -What: /sys/.../buffer/scan_elements/in_magn_x_index -What: /sys/.../buffer/scan_elements/in_magn_y_index -What: /sys/.../buffer/scan_elements/in_magn_z_index -What: /sys/.../buffer/scan_elements/in_incli_x_index -What: /sys/.../buffer/scan_elements/in_incli_y_index -What: /sys/.../buffer/scan_elements/in_timestamp_index -KernelVersion: 2.6.37 -Contact: linux-iio@vger.kernel.org -Description: - A single positive integer specifying the position of this - scan element in the buffer. Note these are not dependent on - what is enabled and may not be contiguous. Thus for user-space - to establish the full layout these must be used in conjunction - with all _en attributes to establish which channels are present, - and the relevant _type attributes to establish the data storage - format. - -What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw -KernelVersion: 2.6.38 -Contact: linux-iio@vger.kernel.org -Description: - This attribute is used to read the amount of quadrature error - present in the device at a given time. diff --git a/Documentation/ABI/testing/sysfs-bus-media b/Documentation/ABI/testing/sysfs-bus-media deleted file mode 100644 index 7057e574154..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-media +++ /dev/null @@ -1,6 +0,0 @@ -What: /sys/bus/media/devices/.../model -Date: January 2011 -Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com> - linux-media@vger.kernel.org -Description: Contains the device model name in UTF-8. The device version is - is not be appended to the model name. diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci deleted file mode 100644 index 34f51100f02..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-pci +++ /dev/null @@ -1,212 +0,0 @@ -What: /sys/bus/pci/drivers/.../bind -Date: December 2003 -Contact: linux-pci@vger.kernel.org -Description: - Writing a device location to this file will cause - the driver to attempt to bind to the device found at - this location. This is useful for overriding default - bindings. The format for the location is: DDDD:BB:DD.F. - That is Domain:Bus:Device.Function and is the same as - found in /sys/bus/pci/devices/. For example: - # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind - (Note: kernels before 2.6.28 may require echo -n). - -What: /sys/bus/pci/drivers/.../unbind -Date: December 2003 -Contact: linux-pci@vger.kernel.org -Description: - Writing a device location to this file will cause the - driver to attempt to unbind from the device found at - this location. This may be useful when overriding default - bindings. The format for the location is: DDDD:BB:DD.F. - That is Domain:Bus:Device.Function and is the same as - found in /sys/bus/pci/devices/. For example: - # echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind - (Note: kernels before 2.6.28 may require echo -n). - -What: /sys/bus/pci/drivers/.../new_id -Date: December 2003 -Contact: linux-pci@vger.kernel.org -Description: - Writing a device ID to this file will attempt to - dynamically add a new device ID to a PCI device driver. - This may allow the driver to support more hardware than - was included in the driver's static device ID support - table at compile time. The format for the device ID is: - VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, - Device ID, Subsystem Vendor ID, Subsystem Device ID, - Class, Class Mask, and Private Driver Data. The Vendor ID - and Device ID fields are required, the rest are optional. - Upon successfully adding an ID, the driver will probe - for the device and attempt to bind to it. For example: - # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id - -What: /sys/bus/pci/drivers/.../remove_id -Date: February 2009 -Contact: Chris Wright <chrisw@sous-sol.org> -Description: - Writing a device ID to this file will remove an ID - that was dynamically added via the new_id sysfs entry. - The format for the device ID is: - VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device - ID, Subsystem Vendor ID, Subsystem Device ID, Class, - and Class Mask. The Vendor ID and Device ID fields are - required, the rest are optional. After successfully - removing an ID, the driver will no longer support the - device. This is useful to ensure auto probing won't - match the driver to the device. For example: - # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id - -What: /sys/bus/pci/rescan -Date: January 2009 -Contact: Linux PCI developers <linux-pci@vger.kernel.org> -Description: - Writing a non-zero value to this attribute will - force a rescan of all PCI buses in the system, and - re-discover previously removed devices. - Depends on CONFIG_HOTPLUG. - -What: /sys/bus/pci/devices/.../msi_irqs/ -Date: September, 2011 -Contact: Neil Horman <nhorman@tuxdriver.com> -Description: - The /sys/devices/.../msi_irqs directory contains a variable set - of sub-directories, with each sub-directory being named after a - corresponding msi irq vector allocated to that device. Each - numbered sub-directory N contains attributes of that irq. - Note that this directory is not created for device drivers which - do not support msi irqs - -What: /sys/bus/pci/devices/.../msi_irqs/<N>/mode -Date: September 2011 -Contact: Neil Horman <nhorman@tuxdriver.com> -Description: - This attribute indicates the mode that the irq vector named by - the parent directory is in (msi vs. msix) - -What: /sys/bus/pci/devices/.../remove -Date: January 2009 -Contact: Linux PCI developers <linux-pci@vger.kernel.org> -Description: - Writing a non-zero value to this attribute will - hot-remove the PCI device and any of its children. - Depends on CONFIG_HOTPLUG. - -What: /sys/bus/pci/devices/.../pci_bus/.../rescan -Date: May 2011 -Contact: Linux PCI developers <linux-pci@vger.kernel.org> -Description: - Writing a non-zero value to this attribute will - force a rescan of the bus and all child buses, - and re-discover devices removed earlier from this - part of the device tree. Depends on CONFIG_HOTPLUG. - -What: /sys/bus/pci/devices/.../rescan -Date: January 2009 -Contact: Linux PCI developers <linux-pci@vger.kernel.org> -Description: - Writing a non-zero value to this attribute will - force a rescan of the device's parent bus and all - child buses, and re-discover devices removed earlier - from this part of the device tree. - Depends on CONFIG_HOTPLUG. - -What: /sys/bus/pci/devices/.../reset -Date: July 2009 -Contact: Michael S. Tsirkin <mst@redhat.com> -Description: - Some devices allow an individual function to be reset - without affecting other functions in the same device. - For devices that have this support, a file named reset - will be present in sysfs. Writing 1 to this file - will perform reset. - -What: /sys/bus/pci/devices/.../vpd -Date: February 2008 -Contact: Ben Hutchings <bhutchings@solarflare.com> -Description: - A file named vpd in a device directory will be a - binary file containing the Vital Product Data for the - device. It should follow the VPD format defined in - PCI Specification 2.1 or 2.2, but users should consider - that some devices may have malformatted data. If the - underlying VPD has a writable section then the - corresponding section of this file will be writable. - -What: /sys/bus/pci/devices/.../virtfnN -Date: March 2009 -Contact: Yu Zhao <yu.zhao@intel.com> -Description: - This symbolic link appears when hardware supports the SR-IOV - capability and the Physical Function driver has enabled it. - The symbolic link points to the PCI device sysfs entry of the - Virtual Function whose index is N (0...MaxVFs-1). - -What: /sys/bus/pci/devices/.../dep_link -Date: March 2009 -Contact: Yu Zhao <yu.zhao@intel.com> -Description: - This symbolic link appears when hardware supports the SR-IOV - capability and the Physical Function driver has enabled it, - and this device has vendor specific dependencies with others. - The symbolic link points to the PCI device sysfs entry of - Physical Function this device depends on. - -What: /sys/bus/pci/devices/.../physfn -Date: March 2009 -Contact: Yu Zhao <yu.zhao@intel.com> -Description: - This symbolic link appears when a device is a Virtual Function. - The symbolic link points to the PCI device sysfs entry of the - Physical Function this device associates with. - -What: /sys/bus/pci/slots/.../module -Date: June 2009 -Contact: linux-pci@vger.kernel.org -Description: - This symbolic link points to the PCI hotplug controller driver - module that manages the hotplug slot. - -What: /sys/bus/pci/devices/.../label -Date: July 2010 -Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com -Description: - Reading this attribute will provide the firmware - given name (SMBIOS type 41 string or ACPI _DSM string) of - the PCI device. The attribute will be created only - if the firmware has given a name to the PCI device. - ACPI _DSM string name will be given priority if the - system firmware provides SMBIOS type 41 string also. -Users: - Userspace applications interested in knowing the - firmware assigned name of the PCI device. - -What: /sys/bus/pci/devices/.../index -Date: July 2010 -Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com -Description: - Reading this attribute will provide the firmware - given instance (SMBIOS type 41 device type instance) of the - PCI device. The attribute will be created only if the firmware - has given an instance number to the PCI device. -Users: - Userspace applications interested in knowing the - firmware assigned device type instance of the PCI - device that can help in understanding the firmware - intended order of the PCI device. - -What: /sys/bus/pci/devices/.../acpi_index -Date: July 2010 -Contact: Narendra K <narendra_k@dell.com>, linux-bugs@dell.com -Description: - Reading this attribute will provide the firmware - given instance (ACPI _DSM instance number) of the PCI device. - The attribute will be created only if the firmware has given - an instance number to the PCI device. ACPI _DSM instance number - will be given priority if the system firmware provides SMBIOS - type 41 device type instance also. -Users: - Userspace applications interested in knowing the - firmware assigned instance number of the PCI - device that can help in understanding the firmware - intended order of the PCI device. diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss deleted file mode 100644 index 53d99edd1d7..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss +++ /dev/null @@ -1,80 +0,0 @@ -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/model -Date: March 2009 -Kernel Version: 2.6.30 -Contact: iss_storagedev@hp.com -Description: Displays the SCSI INQUIRY page 0 model for logical drive - Y of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/rev -Date: March 2009 -Kernel Version: 2.6.30 -Contact: iss_storagedev@hp.com -Description: Displays the SCSI INQUIRY page 0 revision for logical - drive Y of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/unique_id -Date: March 2009 -Kernel Version: 2.6.30 -Contact: iss_storagedev@hp.com -Description: Displays the SCSI INQUIRY page 83 serial number for logical - drive Y of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/vendor -Date: March 2009 -Kernel Version: 2.6.30 -Contact: iss_storagedev@hp.com -Description: Displays the SCSI INQUIRY page 0 vendor for logical drive - Y of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/block:cciss!cXdY -Date: March 2009 -Kernel Version: 2.6.30 -Contact: iss_storagedev@hp.com -Description: A symbolic link to /sys/block/cciss!cXdY - -Where: /sys/bus/pci/devices/<dev>/ccissX/rescan -Date: August 2009 -Kernel Version: 2.6.31 -Contact: iss_storagedev@hp.com -Description: Kicks of a rescan of the controller to discover logical - drive topology changes. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/lunid -Date: August 2009 -Kernel Version: 2.6.31 -Contact: iss_storagedev@hp.com -Description: Displays the 8-byte LUN ID used to address logical - drive Y of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/raid_level -Date: August 2009 -Kernel Version: 2.6.31 -Contact: iss_storagedev@hp.com -Description: Displays the RAID level of logical drive Y of - controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/cXdY/usage_count -Date: August 2009 -Kernel Version: 2.6.31 -Contact: iss_storagedev@hp.com -Description: Displays the usage count (number of opens) of logical drive Y - of controller X. - -Where: /sys/bus/pci/devices/<dev>/ccissX/resettable -Date: February 2011 -Kernel Version: 2.6.38 -Contact: iss_storagedev@hp.com -Description: Value of 1 indicates the controller can honor the reset_devices - kernel parameter. Value of 0 indicates reset_devices cannot be - honored. This is to allow, for example, kexec tools to be able - to warn the user if they designate an unresettable device as - a dump device, as kdump requires resetting the device in order - to work reliably. - -Where: /sys/bus/pci/devices/<dev>/ccissX/transport_mode -Date: July 2011 -Kernel Version: 3.0 -Contact: iss_storagedev@hp.com -Description: Value of "simple" indicates that the controller has been placed - in "simple mode". Value of "performant" indicates that the - controller has been placed in "performant mode". diff --git a/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd b/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd deleted file mode 100644 index 60c60fa624b..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd +++ /dev/null @@ -1,46 +0,0 @@ -What: /sys/bus/pci/drivers/ehci_hcd/.../companion - /sys/bus/usb/devices/usbN/../companion -Date: January 2007 -KernelVersion: 2.6.21 -Contact: Alan Stern <stern@rowland.harvard.edu> -Description: - PCI-based EHCI USB controllers (i.e., high-speed USB-2.0 - controllers) are often implemented along with a set of - "companion" full/low-speed USB-1.1 controllers. When a - high-speed device is plugged in, the connection is routed - to the EHCI controller; when a full- or low-speed device - is plugged in, the connection is routed to the companion - controller. - - Sometimes you want to force a high-speed device to connect - at full speed, which can be accomplished by forcing the - connection to be routed to the companion controller. - That's what this file does. Writing a port number to the - file causes connections on that port to be routed to the - companion controller, and writing the negative of a port - number returns the port to normal operation. - - For example: To force the high-speed device attached to - port 4 on bus 2 to run at full speed: - - echo 4 >/sys/bus/usb/devices/usb2/../companion - - To return the port to high-speed operation: - - echo -4 >/sys/bus/usb/devices/usb2/../companion - - Reading the file gives the list of ports currently forced - to the companion controller. - - Note: Some EHCI controllers do not have companions; they - may contain an internal "transaction translator" or they - may be attached directly to a "rate-matching hub". This - mechanism will not work with such controllers. Also, it - cannot be used to force a port on a high-speed hub to - connect at full speed. - - Note: When this file was first added, it appeared in a - different sysfs directory. The location given above is - correct for 2.6.35 (and probably several earlier kernel - versions as well). - diff --git a/Documentation/ABI/testing/sysfs-bus-rbd b/Documentation/ABI/testing/sysfs-bus-rbd deleted file mode 100644 index bcd88eb7ebc..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-rbd +++ /dev/null @@ -1,76 +0,0 @@ -What: /sys/bus/rbd/ -Date: November 2010 -Contact: Yehuda Sadeh <yehuda@newdream.net>, - Sage Weil <sage@newdream.net> -Description: - -Being used for adding and removing rbd block devices. - -Usage: <mon ip addr> <options> <pool name> <rbd image name> [snap name] - - $ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add - -The snapshot name can be "-" or omitted to map the image read/write. A <dev-id> -will be assigned for any registered block device. If snapshot is used, it will -be mapped read-only. - -Removal of a device: - - $ echo <dev-id> > /sys/bus/rbd/remove - -Entries under /sys/bus/rbd/devices/<dev-id>/ --------------------------------------------- - -client_id - - The ceph unique client id that was assigned for this specific session. - -major - - The block device major number. - -name - - The name of the rbd image. - -pool - - The pool where this rbd image resides. The pool-name pair is unique - per rados system. - -size - - The size (in bytes) of the mapped block device. - -refresh - - Writing to this file will reread the image header data and set - all relevant datastructures accordingly. - -current_snap - - The current snapshot for which the device is mapped. - -create_snap - - Create a snapshot: - - $ echo <snap-name> > /sys/bus/rbd/devices/<dev-id>/snap_create - -snap_* - - A directory per each snapshot - - -Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name> -------------------------------------------------------------- - -snap_id - - The rados internal snapshot id assigned for this snapshot - -snap_size - - The size of the image when this snapshot was taken. - - diff --git a/Documentation/ABI/testing/sysfs-bus-rpmsg b/Documentation/ABI/testing/sysfs-bus-rpmsg deleted file mode 100644 index 189e419a5a2..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-rpmsg +++ /dev/null @@ -1,75 +0,0 @@ -What: /sys/bus/rpmsg/devices/.../name -Date: June 2011 -KernelVersion: 3.3 -Contact: Ohad Ben-Cohen <ohad@wizery.com> -Description: - Every rpmsg device is a communication channel with a remote - processor. Channels are identified with a (textual) name, - which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in - rpmsg.h). - - This sysfs entry contains the name of this channel. - -What: /sys/bus/rpmsg/devices/.../src -Date: June 2011 -KernelVersion: 3.3 -Contact: Ohad Ben-Cohen <ohad@wizery.com> -Description: - Every rpmsg device is a communication channel with a remote - processor. Channels have a local ("source") rpmsg address, - and remote ("destination") rpmsg address. When an entity - starts listening on one end of a channel, it assigns it with - a unique rpmsg address (a 32 bits integer). This way when - inbound messages arrive to this address, the rpmsg core - dispatches them to the listening entity (a kernel driver). - - This sysfs entry contains the src (local) rpmsg address - of this channel. If it contains 0xffffffff, then an address - wasn't assigned (can happen if no driver exists for this - channel). - -What: /sys/bus/rpmsg/devices/.../dst -Date: June 2011 -KernelVersion: 3.3 -Contact: Ohad Ben-Cohen <ohad@wizery.com> -Description: - Every rpmsg device is a communication channel with a remote - processor. Channels have a local ("source") rpmsg address, - and remote ("destination") rpmsg address. When an entity - starts listening on one end of a channel, it assigns it with - a unique rpmsg address (a 32 bits integer). This way when - inbound messages arrive to this address, the rpmsg core - dispatches them to the listening entity. - - This sysfs entry contains the dst (remote) rpmsg address - of this channel. If it contains 0xffffffff, then an address - wasn't assigned (can happen if the kernel driver that - is attached to this channel is exposing a service to the - remote processor. This make it a local rpmsg server, - and it is listening for inbound messages that may be sent - from any remote rpmsg client; it is not bound to a single - remote entity). - -What: /sys/bus/rpmsg/devices/.../announce -Date: June 2011 -KernelVersion: 3.3 -Contact: Ohad Ben-Cohen <ohad@wizery.com> -Description: - Every rpmsg device is a communication channel with a remote - processor. Channels are identified by a textual name (see - /sys/bus/rpmsg/devices/.../name above) and have a local - ("source") rpmsg address, and remote ("destination") rpmsg - address. - - A channel is first created when an entity, whether local - or remote, starts listening on it for messages (and is thus - called an rpmsg server). - - When that happens, a "name service" announcement is sent - to the other processor, in order to let it know about the - creation of the channel (this way remote clients know they - can start sending messages). - - This sysfs entry tells us whether the channel is a local - server channel that is announced (values are either - true or false). diff --git a/Documentation/ABI/testing/sysfs-bus-umc b/Documentation/ABI/testing/sysfs-bus-umc deleted file mode 100644 index 948fec41244..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-umc +++ /dev/null @@ -1,28 +0,0 @@ -What: /sys/bus/umc/ -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The Wireless Host Controller Interface (WHCI) - specification describes a PCI-based device with - multiple capabilities; the UWB Multi-interface - Controller (UMC). - - The umc bus presents each of the individual - capabilties as a device. - -What: /sys/bus/umc/devices/.../capability_id -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The ID of this capability, with 0 being the radio - controller capability. - -What: /sys/bus/umc/devices/.../version -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The specification version this capability's hardware - interface complies with. diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb deleted file mode 100644 index 6df4e6f5756..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-usb +++ /dev/null @@ -1,210 +0,0 @@ -What: /sys/bus/usb/devices/.../power/autosuspend -Date: March 2007 -KernelVersion: 2.6.21 -Contact: Alan Stern <stern@rowland.harvard.edu> -Description: - Each USB device directory will contain a file named - power/autosuspend. This file holds the time (in seconds) - the device must be idle before it will be autosuspended. - 0 means the device will be autosuspended as soon as - possible. Negative values will prevent the device from - being autosuspended at all, and writing a negative value - will resume the device if it is already suspended. - - The autosuspend delay for newly-created devices is set to - the value of the usbcore.autosuspend module parameter. - -What: /sys/bus/usb/devices/.../power/persist -Date: May 2007 -KernelVersion: 2.6.23 -Contact: Alan Stern <stern@rowland.harvard.edu> -Description: - If CONFIG_USB_PERSIST is set, then each USB device directory - will contain a file named power/persist. The file holds a - boolean value (0 or 1) indicating whether or not the - "USB-Persist" facility is enabled for the device. Since the - facility is inherently dangerous, it is disabled by default - for all devices except hubs. For more information, see - Documentation/usb/persist.txt. - -What: /sys/bus/usb/device/.../power/connected_duration -Date: January 2008 -KernelVersion: 2.6.25 -Contact: Sarah Sharp <sarah.a.sharp@intel.com> -Description: - If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file - is present. When read, it returns the total time (in msec) - that the USB device has been connected to the machine. This - file is read-only. -Users: - PowerTOP <power@bughost.org> - http://www.lesswatts.org/projects/powertop/ - -What: /sys/bus/usb/device/.../power/active_duration -Date: January 2008 -KernelVersion: 2.6.25 -Contact: Sarah Sharp <sarah.a.sharp@intel.com> -Description: - If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file - is present. When read, it returns the total time (in msec) - that the USB device has been active, i.e. not in a suspended - state. This file is read-only. - - Tools can use this file and the connected_duration file to - compute the percentage of time that a device has been active. - For example, - echo $((100 * `cat active_duration` / `cat connected_duration`)) - will give an integer percentage. Note that this does not - account for counter wrap. -Users: - PowerTOP <power@bughost.org> - http://www.lesswatts.org/projects/powertop/ - -What: /sys/bus/usb/device/<busnum>-<devnum>...:<config num>-<interface num>/supports_autosuspend -Date: January 2008 -KernelVersion: 2.6.27 -Contact: Sarah Sharp <sarah.a.sharp@intel.com> -Description: - When read, this file returns 1 if the interface driver - for this interface supports autosuspend. It also - returns 1 if no driver has claimed this interface, as an - unclaimed interface will not stop the device from being - autosuspended if all other interface drivers are idle. - The file returns 0 if autosuspend support has not been - added to the driver. -Users: - USB PM tool - git://git.moblin.org/users/sarah/usb-pm-tool/ - -What: /sys/bus/usb/device/.../authorized -Date: July 2008 -KernelVersion: 2.6.26 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - Authorized devices are available for use by device - drivers, non-authorized one are not. By default, wired - USB devices are authorized. - - Certified Wireless USB devices are not authorized - initially and should be (by writing 1) after the - device has been authenticated. - -What: /sys/bus/usb/device/.../wusb_cdid -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - For Certified Wireless USB devices only. - - A devices's CDID, as 16 space-separated hex octets. - -What: /sys/bus/usb/device/.../wusb_ck -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - For Certified Wireless USB devices only. - - Write the device's connection key (CK) to start the - authentication of the device. The CK is 16 - space-separated hex octets. - -What: /sys/bus/usb/device/.../wusb_disconnect -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - For Certified Wireless USB devices only. - - Write a 1 to force the device to disconnect - (equivalent to unplugging a wired USB device). - -What: /sys/bus/usb/drivers/.../new_id -Date: October 2011 -Contact: linux-usb@vger.kernel.org -Description: - Writing a device ID to this file will attempt to - dynamically add a new device ID to a USB device driver. - This may allow the driver to support more hardware than - was included in the driver's static device ID support - table at compile time. The format for the device ID is: - idVendor idProduct bInterfaceClass. - The vendor ID and device ID fields are required, the - interface class is optional. - Upon successfully adding an ID, the driver will probe - for the device and attempt to bind to it. For example: - # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id - - Reading from this file will list all dynamically added - device IDs in the same format, with one entry per - line. For example: - # cat /sys/bus/usb/drivers/foo/new_id - 8086 10f5 - dead beef 06 - f00d cafe - - The list will be truncated at PAGE_SIZE bytes due to - sysfs restrictions. - -What: /sys/bus/usb-serial/drivers/.../new_id -Date: October 2011 -Contact: linux-usb@vger.kernel.org -Description: - For serial USB drivers, this attribute appears under the - extra bus folder "usb-serial" in sysfs; apart from that - difference, all descriptions from the entry - "/sys/bus/usb/drivers/.../new_id" apply. - -What: /sys/bus/usb/drivers/.../remove_id -Date: November 2009 -Contact: CHENG Renquan <rqcheng@smu.edu.sg> -Description: - Writing a device ID to this file will remove an ID - that was dynamically added via the new_id sysfs entry. - The format for the device ID is: - idVendor idProduct. After successfully - removing an ID, the driver will no longer support the - device. This is useful to ensure auto probing won't - match the driver to the device. For example: - # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id - - Reading from this file will list the dynamically added - device IDs, exactly like reading from the entry - "/sys/bus/usb/drivers/.../new_id" - -What: /sys/bus/usb/device/.../avoid_reset_quirk -Date: December 2009 -Contact: Oliver Neukum <oliver@neukum.org> -Description: - Writing 1 to this file tells the kernel that this - device will morph into another mode when it is reset. - Drivers will not use reset for error handling for - such devices. -Users: - usb_modeswitch - -What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm -Date: September 2011 -Contact: Andiry Xu <andiry.xu@amd.com> -Description: - If CONFIG_USB_SUSPEND is set and a USB 2.0 lpm-capable device - is plugged in to a xHCI host which support link PM, it will - perform a LPM test; if the test is passed and host supports - USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will - be enabled for the device and the USB device directory will - contain a file named power/usb2_hardware_lpm. The file holds - a string value (enable or disable) indicating whether or not - USB2 hardware LPM is enabled for the device. Developer can - write y/Y/1 or n/N/0 to the file to enable/disable the - feature. - -What: /sys/bus/usb/devices/.../removable -Date: February 2012 -Contact: Matthew Garrett <mjg@redhat.com> -Description: - Some information about whether a given USB device is - physically fixed to the platform can be inferred from a - combination of hub descriptor bits and platform-specific data - such as ACPI. This file will read either "removable" or - "fixed" if the information is available, and "unknown" - otherwise. diff --git a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg deleted file mode 100644 index cb830df8777..00000000000 --- a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg +++ /dev/null @@ -1,43 +0,0 @@ -Where: /sys/bus/usb/.../powered -Date: August 2008 -Kernel Version: 2.6.26 -Contact: Harrison Metzger <harrisonmetz@gmail.com> -Description: Controls whether the device's display will powered. - A value of 0 is off and a non-zero value is on. - -Where: /sys/bus/usb/.../mode_msb -Where: /sys/bus/usb/.../mode_lsb -Date: August 2008 -Kernel Version: 2.6.26 -Contact: Harrison Metzger <harrisonmetz@gmail.com> -Description: Controls the devices display mode. - For a 6 character display the values are - MSB 0x06; LSB 0x3F, and - for an 8 character display the values are - MSB 0x08; LSB 0xFF. - -Where: /sys/bus/usb/.../textmode -Date: August 2008 -Kernel Version: 2.6.26 -Contact: Harrison Metzger <harrisonmetz@gmail.com> -Description: Controls the way the device interprets its text buffer. - raw: each character controls its segment manually - hex: each character is between 0-15 - ascii: each character is between '0'-'9' and 'A'-'F'. - -Where: /sys/bus/usb/.../text -Date: August 2008 -Kernel Version: 2.6.26 -Contact: Harrison Metzger <harrisonmetz@gmail.com> -Description: The text (or data) for the device to display - -Where: /sys/bus/usb/.../decimals -Date: August 2008 -Kernel Version: 2.6.26 -Contact: Harrison Metzger <harrisonmetz@gmail.com> -Description: Controls the decimal places on the device. - To set the nth decimal place, give this field - 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 diff --git a/Documentation/ABI/testing/sysfs-c2port b/Documentation/ABI/testing/sysfs-c2port deleted file mode 100644 index 716cffc457e..00000000000 --- a/Documentation/ABI/testing/sysfs-c2port +++ /dev/null @@ -1,88 +0,0 @@ -What: /sys/class/c2port/ -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/ directory will contain files and - directories that will provide a unified interface to - the C2 port interface. - -What: /sys/class/c2port/c2portX -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/ directory is related to X-th - C2 port into the system. Each directory will contain files to - manage and control its C2 port. - -What: /sys/class/c2port/c2portX/access -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/access file enable the access - to the C2 port from the system. No commands can be sent - till this entry is set to 0. - -What: /sys/class/c2port/c2portX/dev_id -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/dev_id file show the device ID - of the connected micro. - -What: /sys/class/c2port/c2portX/flash_access -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_access file enable the - access to the on-board flash of the connected micro. - No commands can be sent till this entry is set to 0. - -What: /sys/class/c2port/c2portX/flash_block_size -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_block_size file show - the on-board flash block size of the connected micro. - -What: /sys/class/c2port/c2portX/flash_blocks_num -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_blocks_num file show - the on-board flash blocks number of the connected micro. - -What: /sys/class/c2port/c2portX/flash_data -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_data file export - the content of the on-board flash of the connected micro. - -What: /sys/class/c2port/c2portX/flash_erase -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_erase file execute - the "erase" command on the on-board flash of the connected - micro. - -What: /sys/class/c2port/c2portX/flash_erase -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/flash_erase file show the - on-board flash size of the connected micro. - -What: /sys/class/c2port/c2portX/reset -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/reset file execute a "reset" - command on the connected micro. - -What: /sys/class/c2port/c2portX/rev_id -Date: October 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/c2port/c2portX/rev_id file show the revision ID - of the connected micro. diff --git a/Documentation/ABI/testing/sysfs-cfq-target-latency b/Documentation/ABI/testing/sysfs-cfq-target-latency deleted file mode 100644 index df0f7828c5e..00000000000 --- a/Documentation/ABI/testing/sysfs-cfq-target-latency +++ /dev/null @@ -1,8 +0,0 @@ -What: /sys/block/<device>/iosched/target_latency -Date: March 2012 -contact: Tao Ma <boyu.mt@taobao.com> -Description: - The /sys/block/<device>/iosched/target_latency only exists - when the user sets cfq to /sys/block/<device>/scheduler. - It contains an estimated latency time for the cfq. cfq will - use it to calculate the time slice used for every task. diff --git a/Documentation/ABI/testing/sysfs-class b/Documentation/ABI/testing/sysfs-class deleted file mode 100644 index 676530fcf74..00000000000 --- a/Documentation/ABI/testing/sysfs-class +++ /dev/null @@ -1,16 +0,0 @@ -What: /sys/class/ -Date: Febuary 2006 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - The /sys/class directory will consist of a group of - subdirectories describing individual classes of devices - in the kernel. The individual directories will consist - of either subdirectories, or symlinks to other - directories. - - All programs that use this directory tree must be able - to handle both subdirectories or symlinks in order to - work properly. - -Users: - udev <linux-hotplug-devel@lists.sourceforge.net> diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 deleted file mode 100644 index 4a9c545bda4..00000000000 --- a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 +++ /dev/null @@ -1,56 +0,0 @@ -What: /sys/class/backlight/<backlight>/<ambient light zone>_max -What: /sys/class/backlight/<backlight>/l1_daylight_max -What: /sys/class/backlight/<backlight>/l2_bright_max -What: /sys/class/backlight/<backlight>/l3_office_max -What: /sys/class/backlight/<backlight>/l4_indoor_max -What: /sys/class/backlight/<backlight>/l5_dark_max -Date: May 2011 -KernelVersion: 3.0 -Contact: device-drivers-devel@blackfin.uclinux.org -Description: - Control the maximum brightness for <ambient light zone> - on this <backlight>. Values are between 0 and 127. This file - will also show the brightness level stored for this - <ambient light zone>. - -What: /sys/class/backlight/<backlight>/<ambient light zone>_dim -What: /sys/class/backlight/<backlight>/l2_bright_dim -What: /sys/class/backlight/<backlight>/l3_office_dim -What: /sys/class/backlight/<backlight>/l4_indoor_dim -What: /sys/class/backlight/<backlight>/l5_dark_dim -Date: May 2011 -KernelVersion: 3.0 -Contact: device-drivers-devel@blackfin.uclinux.org -Description: - Control the dim brightness for <ambient light zone> - on this <backlight>. Values are between 0 and 127, typically - set to 0. Full off when the backlight is disabled. - This file will also show the dim brightness level stored for - this <ambient light zone>. - -What: /sys/class/backlight/<backlight>/ambient_light_level -Date: May 2011 -KernelVersion: 3.0 -Contact: device-drivers-devel@blackfin.uclinux.org -Description: - Get conversion value of the light sensor. - This value is updated every 80 ms (when the light sensor - is enabled). Returns integer between 0 (dark) and - 8000 (max ambient brightness) - -What: /sys/class/backlight/<backlight>/ambient_light_zone -Date: May 2011 -KernelVersion: 3.0 -Contact: device-drivers-devel@blackfin.uclinux.org -Description: - Get/Set current ambient light zone. Reading returns - integer between 1..5 (1 = daylight, 2 = bright, ..., 5 = dark). - Writing a value between 1..5 forces the backlight controller - to enter the corresponding ambient light zone. - Writing 0 returns to normal/automatic ambient light level - operation. The ambient light sensing feature on these devices - is an extension to the API documented in - 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 diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 b/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 deleted file mode 100644 index 77cf7ac949a..00000000000 --- a/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 +++ /dev/null @@ -1,48 +0,0 @@ -What: /sys/class/backlight/<backlight>/als_channel -Date: May 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Get the ALS output channel used as input in - ALS-current-control mode (0, 1), where - - 0 - out_current0 (backlight 0) - 1 - out_current1 (backlight 1) - -What: /sys/class/backlight/<backlight>/als_en -Date: May 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Enable ALS-current-control mode (0, 1). - -What: /sys/class/backlight/<backlight>/id -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Get the id of this backlight (0, 1). - -What: /sys/class/backlight/<backlight>/linear -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the brightness-mapping mode (0, 1), where - - 0 - exponential mode - 1 - linear mode - -What: /sys/class/backlight/<backlight>/pwm -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the PWM-input control mask (5 bits), where - - bit 5 - PWM-input enabled in Zone 4 - bit 4 - PWM-input enabled in Zone 3 - bit 3 - PWM-input enabled in Zone 2 - bit 2 - PWM-input enabled in Zone 1 - bit 1 - PWM-input enabled in Zone 0 - bit 0 - PWM-input enabled diff --git a/Documentation/ABI/testing/sysfs-class-bdi b/Documentation/ABI/testing/sysfs-class-bdi deleted file mode 100644 index 5f500977b42..00000000000 --- a/Documentation/ABI/testing/sysfs-class-bdi +++ /dev/null @@ -1,50 +0,0 @@ -What: /sys/class/bdi/<bdi>/ -Date: January 2008 -Contact: Peter Zijlstra <a.p.zijlstra@chello.nl> -Description: - -Provide a place in sysfs for the backing_dev_info object. This allows -setting and retrieving various BDI specific variables. - -The <bdi> identifier can be either of the following: - -MAJOR:MINOR - - Device number for block devices, or value of st_dev on - non-block filesystems which provide their own BDI, such as NFS - and FUSE. - -MAJOR:MINOR-fuseblk - - Value of st_dev on fuseblk filesystems. - -default - - The default backing dev, used for non-block device backed - filesystems which do not provide their own BDI. - -Files under /sys/class/bdi/<bdi>/ ---------------------------------- - -read_ahead_kb (read-write) - - Size of the read-ahead window in kilobytes - -min_ratio (read-write) - - Under normal circumstances each device is given a part of the - total write-back cache that relates to its current average - writeout speed in relation to the other devices. - - The 'min_ratio' parameter allows assigning a minimum - percentage of the write-back cache to a particular device. - For example, this is useful for providing a minimum QoS. - -max_ratio (read-write) - - Allows limiting a particular device to use not more than the - given percentage of the write-back cache. This is useful in - situations where we want to avoid one device taking all or - most of the write-back cache. For example in case of an NFS - mount that is prone to get stuck, or a FUSE mount which cannot - be trusted to play fair. diff --git a/Documentation/ABI/testing/sysfs-class-devfreq b/Documentation/ABI/testing/sysfs-class-devfreq deleted file mode 100644 index 23d78b5aab1..00000000000 --- a/Documentation/ABI/testing/sysfs-class-devfreq +++ /dev/null @@ -1,52 +0,0 @@ -What: /sys/class/devfreq/.../ -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - Provide a place in sysfs for the devfreq objects. - This allows accessing various devfreq specific variables. - The name of devfreq object denoted as ... is same as the - name of device using devfreq. - -What: /sys/class/devfreq/.../governor -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/devfreq/.../governor shows the name of the - governor used by the corresponding devfreq object. - -What: /sys/class/devfreq/.../cur_freq -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/devfreq/.../cur_freq shows the current - frequency of the corresponding devfreq object. - -What: /sys/class/devfreq/.../central_polling -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/devfreq/.../central_polling shows whether - the devfreq ojbect is using devfreq-provided central - polling mechanism or not. - -What: /sys/class/devfreq/.../polling_interval -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/devfreq/.../polling_interval shows and sets - the requested polling interval of the corresponding devfreq - object. The values are represented in ms. If the value is - less than 1 jiffy, it is considered to be 0, which means - no polling. This value is meaningless if the governor is - not polling; thus. If the governor is not using - devfreq-provided central polling - (/sys/class/devfreq/.../central_polling is 0), this value - may be useless. - -What: /sys/class/devfreq/.../userspace/set_freq -Date: September 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/devfreq/.../userspace/set_freq shows and - sets the requested frequency for the devfreq object if - userspace governor is in effect. diff --git a/Documentation/ABI/testing/sysfs-class-extcon b/Documentation/ABI/testing/sysfs-class-extcon deleted file mode 100644 index 20ab361bd8c..00000000000 --- a/Documentation/ABI/testing/sysfs-class-extcon +++ /dev/null @@ -1,97 +0,0 @@ -What: /sys/class/extcon/.../ -Date: February 2012 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - Provide a place in sysfs for the extcon objects. - This allows accessing extcon specific variables. - The name of extcon object denoted as ... is the name given - with extcon_dev_register. - - One extcon device denotes a single external connector - port. An external connector may have multiple cables - attached simultaneously. Many of docks, cradles, and - accessory cables have such capability. For example, - the 30-pin port of Nuri board (/arch/arm/mach-exynos) - may have both HDMI and Charger attached, or analog audio, - video, and USB cables attached simulteneously. - - If there are cables mutually exclusive with each other, - such binary relations may be expressed with extcon_dev's - mutually_exclusive array. - -What: /sys/class/extcon/.../name -Date: February 2012 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/extcon/.../name shows the name of the extcon - object. If the extcon object has an optional callback - "show_name" defined, the callback will provide the name with - this sysfs node. - -What: /sys/class/extcon/.../state -Date: February 2012 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/extcon/.../state shows and stores the cable - attach/detach information of the corresponding extcon object. - If the extcon object has an optional callback "show_state" - defined, the showing function is overriden with the optional - callback. - - If the default callback for showing function is used, the - format is like this: - # cat state - USB_OTG=1 - HDMI=0 - TA=1 - EAR_JACK=0 - # - In this example, the extcon device have USB_OTG and TA - cables attached and HDMI and EAR_JACK cables detached. - - In order to update the state of an extcon device, enter a hex - state number starting with 0x. - echo 0xHEX > state - - This updates the whole state of the extcon dev. - Inputs of all the methods are required to meet the - mutually_exclusive contidions if they exist. - - It is recommended to use this "global" state interface if - you need to enter the value atomically. The later state - interface associated with each cable cannot update - multiple cable states of an extcon device simultaneously. - -What: /sys/class/extcon/.../cable.x/name -Date: February 2012 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/extcon/.../cable.x/name shows the name of cable - "x" (integer between 0 and 31) of an extcon device. - -What: /sys/class/extcon/.../cable.x/state -Date: February 2012 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - The /sys/class/extcon/.../cable.x/name shows and stores the - state of cable "x" (integer between 0 and 31) of an extcon - device. The state value is either 0 (detached) or 1 - (attached). - -What: /sys/class/extcon/.../mutually_exclusive/... -Date: December 2011 -Contact: MyungJoo Ham <myungjoo.ham@samsung.com> -Description: - Shows the relations of mutually exclusiveness. For example, - if the mutually_exclusive array of extcon_dev is - {0x3, 0x5, 0xC, 0x0}, the, the output is: - # ls mutually_exclusive/ - 0x3 - 0x5 - 0xc - # - - Note that mutually_exclusive is a sub-directory of the extcon - device and the file names under the mutually_exclusive - directory show the mutually-exclusive sets, not the contents - of the files. diff --git a/Documentation/ABI/testing/sysfs-class-lcd b/Documentation/ABI/testing/sysfs-class-lcd deleted file mode 100644 index 35906bf7aa7..00000000000 --- a/Documentation/ABI/testing/sysfs-class-lcd +++ /dev/null @@ -1,23 +0,0 @@ -What: /sys/class/lcd/<lcd>/lcd_power -Date: April 2005 -KernelVersion: 2.6.12 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Control LCD power, values are FB_BLANK_* from fb.h - - FB_BLANK_UNBLANK (0) : power on. - - FB_BLANK_POWERDOWN (4) : power off - -What: /sys/class/lcd/<lcd>/contrast -Date: April 2005 -KernelVersion: 2.6.12 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Current contrast of this LCD device. Value is between 0 and - /sys/class/lcd/<lcd>/max_contrast. - -What: /sys/class/lcd/<lcd>/max_contrast -Date: April 2005 -KernelVersion: 2.6.12 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Maximum contrast for this LCD device. diff --git a/Documentation/ABI/testing/sysfs-class-led b/Documentation/ABI/testing/sysfs-class-led deleted file mode 100644 index 3646ec85d51..00000000000 --- a/Documentation/ABI/testing/sysfs-class-led +++ /dev/null @@ -1,37 +0,0 @@ -What: /sys/class/leds/<led>/brightness -Date: March 2006 -KernelVersion: 2.6.17 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Set the brightness of the LED. Most LEDs don't - have hardware brightness support so will just be turned on for - non-zero brightness settings. The value is between 0 and - /sys/class/leds/<led>/max_brightness. - -What: /sys/class/leds/<led>/max_brightness -Date: March 2006 -KernelVersion: 2.6.17 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Maximum brightness level for this led, default is 255 (LED_FULL). - -What: /sys/class/leds/<led>/trigger -Date: March 2006 -KernelVersion: 2.6.17 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Set the trigger for this LED. A trigger is a kernel based source - of led events. - You can change triggers in a similar manner to the way an IO - scheduler is chosen. Trigger specific parameters can appear in - /sys/class/leds/<led> once a given trigger is selected. - -What: /sys/class/leds/<led>/inverted -Date: January 2011 -KernelVersion: 2.6.38 -Contact: Richard Purdie <rpurdie@rpsys.net> -Description: - Invert the LED on/off state. This parameter is specific to - gpio and backlight triggers. In case of the backlight trigger, - it is useful when driving a LED which is intended to indicate - a device in a standby like state. diff --git a/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 b/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 deleted file mode 100644 index 620ebb3b9ba..00000000000 --- a/Documentation/ABI/testing/sysfs-class-led-driver-lm3533 +++ /dev/null @@ -1,65 +0,0 @@ -What: /sys/class/leds/<led>/als_channel -Date: May 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the ALS output channel to use as input in - ALS-current-control mode (1, 2), where - - 1 - out_current1 - 2 - out_current2 - -What: /sys/class/leds/<led>/als_en -Date: May 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Enable ALS-current-control mode (0, 1). - -What: /sys/class/leds/<led>/falltime -What: /sys/class/leds/<led>/risetime -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the pattern generator fall and rise times (0..7), where - - 0 - 2048 us - 1 - 262 ms - 2 - 524 ms - 3 - 1.049 s - 4 - 2.097 s - 5 - 4.194 s - 6 - 8.389 s - 7 - 16.78 s - -What: /sys/class/leds/<led>/id -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Get the id of this led (0..3). - -What: /sys/class/leds/<led>/linear -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the brightness-mapping mode (0, 1), where - - 0 - exponential mode - 1 - linear mode - -What: /sys/class/leds/<led>/pwm -Date: April 2012 -KernelVersion: 3.5 -Contact: Johan Hovold <jhovold@gmail.com> -Description: - Set the PWM-input control mask (5 bits), where - - bit 5 - PWM-input enabled in Zone 4 - bit 4 - PWM-input enabled in Zone 3 - bit 3 - PWM-input enabled in Zone 2 - bit 2 - PWM-input enabled in Zone 1 - bit 1 - PWM-input enabled in Zone 0 - bit 0 - PWM-input enabled diff --git a/Documentation/ABI/testing/sysfs-class-mtd b/Documentation/ABI/testing/sysfs-class-mtd deleted file mode 100644 index db1ad7e34fc..00000000000 --- a/Documentation/ABI/testing/sysfs-class-mtd +++ /dev/null @@ -1,176 +0,0 @@ -What: /sys/class/mtd/ -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - The mtd/ class subdirectory belongs to the MTD subsystem - (MTD core). - -What: /sys/class/mtd/mtdX/ -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - The /sys/class/mtd/mtd{0,1,2,3,...} directories correspond - to each /dev/mtdX character device. These may represent - physical/simulated flash devices, partitions on a flash - device, or concatenated flash devices. They exist regardless - of whether CONFIG_MTD_CHAR is actually enabled. - -What: /sys/class/mtd/mtdXro/ -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - These directories provide the corresponding read-only device - nodes for /sys/class/mtd/mtdX/ . They are only created - (for the benefit of udev) if CONFIG_MTD_CHAR is enabled. - -What: /sys/class/mtd/mtdX/dev -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - Major and minor numbers of the character device corresponding - to this MTD device (in <major>:<minor> format). This is the - read-write device so <minor> will be even. - -What: /sys/class/mtd/mtdXro/dev -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - Major and minor numbers of the character device corresponding - to the read-only variant of thie MTD device (in - <major>:<minor> format). In this case <minor> will be odd. - -What: /sys/class/mtd/mtdX/erasesize -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - "Major" erase size for the device. If numeraseregions is - zero, this is the eraseblock size for the entire device. - Otherwise, the MEMGETREGIONCOUNT/MEMGETREGIONINFO ioctls - can be used to determine the actual eraseblock layout. - -What: /sys/class/mtd/mtdX/flags -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - A hexadecimal value representing the device flags, ORed - together: - - 0x0400: MTD_WRITEABLE - device is writable - 0x0800: MTD_BIT_WRITEABLE - single bits can be flipped - 0x1000: MTD_NO_ERASE - no erase necessary - 0x2000: MTD_POWERUP_LOCK - always locked after reset - -What: /sys/class/mtd/mtdX/name -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - A human-readable ASCII name for the device or partition. - This will match the name in /proc/mtd . - -What: /sys/class/mtd/mtdX/numeraseregions -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - For devices that have variable eraseblock sizes, this - provides the total number of erase regions. Otherwise, - it will read back as zero. - -What: /sys/class/mtd/mtdX/oobsize -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - Number of OOB bytes per page. - -What: /sys/class/mtd/mtdX/size -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - Total size of the device/partition, in bytes. - -What: /sys/class/mtd/mtdX/type -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - One of the following ASCII strings, representing the device - type: - - absent, ram, rom, nor, nand, dataflash, ubi, unknown - -What: /sys/class/mtd/mtdX/writesize -Date: April 2009 -KernelVersion: 2.6.29 -Contact: linux-mtd@lists.infradead.org -Description: - Minimal writable flash unit size. This will always be - a positive integer. - - In the case of NOR flash it is 1 (even though individual - bits can be cleared). - - In the case of NAND flash it is one NAND page (or a - half page, or a quarter page). - - In the case of ECC NOR, it is the ECC block size. - -What: /sys/class/mtd/mtdX/ecc_strength -Date: April 2012 -KernelVersion: 3.4 -Contact: linux-mtd@lists.infradead.org -Description: - Maximum number of bit errors that the device is capable of - correcting within each region covering an ecc step. This will - always be a non-negative integer. Note that some devices will - have multiple ecc steps within each writesize region. - - In the case of devices lacking any ECC capability, it is 0. - -What: /sys/class/mtd/mtdX/bitflip_threshold -Date: April 2012 -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. - - The initial value may be specified by the flash device driver. - If not, then the default value is ecc_strength. - - The introduction of this feature brings a subtle change to the - meaning of the -EUCLEAN return code. Previously, it was - interpreted to mean simply "one or more bit errors were - corrected". Its new interpretation can be phrased as "a - dangerously high number of bit errors were corrected on one or - more regions comprising an ecc step". The precise definition of - "dangerously high" can be adjusted by the user with - bitflip_threshold. Users are discouraged from doing this, - however, unless they know what they are doing and have intimate - knowledge of the properties of their device. Broadly speaking, - bitflip_threshold should be low enough to detect genuine erase - 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(). - Conversely, if bitflip_threshold is zero, -EUCLEAN is always - returned, absent a hard error. - - This is generally applicable only to NAND flash devices with ECC - capability. It is ignored on devices lacking ECC capability; - i.e., devices for which ecc_strength is zero. diff --git a/Documentation/ABI/testing/sysfs-class-net-batman-adv b/Documentation/ABI/testing/sysfs-class-net-batman-adv deleted file mode 100644 index 38dd762def4..00000000000 --- a/Documentation/ABI/testing/sysfs-class-net-batman-adv +++ /dev/null @@ -1,14 +0,0 @@ - -What: /sys/class/net/<iface>/batman-adv/mesh_iface -Date: May 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - The /sys/class/net/<iface>/batman-adv/mesh_iface file - displays the batman mesh interface this <iface> - currently is associated with. - -What: /sys/class/net/<iface>/batman-adv/iface_status -Date: May 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Indicates the status of <iface> as it is seen by batman. diff --git a/Documentation/ABI/testing/sysfs-class-net-mesh b/Documentation/ABI/testing/sysfs-class-net-mesh deleted file mode 100644 index c81fe89c4c4..00000000000 --- a/Documentation/ABI/testing/sysfs-class-net-mesh +++ /dev/null @@ -1,93 +0,0 @@ - -What: /sys/class/net/<mesh_iface>/mesh/aggregated_ogms -Date: May 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Indicates whether the batman protocol messages of the - mesh <mesh_iface> shall be aggregated or not. - -What: /sys/class/net/<mesh_iface>/mesh/bonding -Date: June 2010 -Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de> -Description: - Indicates whether the data traffic going through the - mesh will be sent using multiple interfaces at the - same time (if available). - -What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance -Date: November 2011 -Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de> -Description: - Indicates whether the bridge loop avoidance feature - is enabled. This feature detects and avoids loops - between the mesh and devices bridged with the soft - interface <mesh_iface>. - -What: /sys/class/net/<mesh_iface>/mesh/fragmentation -Date: October 2010 -Contact: Andreas Langer <an.langer@gmx.de> -Description: - Indicates whether the data traffic going through the - mesh will be fragmented or silently discarded if the - packet size exceeds the outgoing interface MTU. - -What: /sys/class/net/<mesh_iface>/mesh/ap_isolation -Date: May 2011 -Contact: Antonio Quartulli <ordex@autistici.org> -Description: - Indicates whether the data traffic going from a - wireless client to another wireless client will be - silently dropped. - -What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth -Date: October 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Defines the bandwidth which is propagated by this - node if gw_mode was set to 'server'. - -What: /sys/class/net/<mesh_iface>/mesh/gw_mode -Date: October 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Defines the state of the gateway features. Can be - either 'off', 'client' or 'server'. - -What: /sys/class/net/<mesh_iface>/mesh/gw_sel_class -Date: October 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Defines the selection criteria this node will use - to choose a gateway if gw_mode was set to 'client'. - -What: /sys/class/net/<mesh_iface>/mesh/orig_interval -Date: May 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Defines the interval in milliseconds in which batman - sends its protocol messages. - -What: /sys/class/net/<mesh_iface>/mesh/hop_penalty -Date: Oct 2010 -Contact: Linus Lüssing <linus.luessing@web.de> -Description: - Defines the penalty which will be applied to an - originator message's tq-field on every hop. - -What: /sys/class/net/<mesh_iface>/mesh/routing_algo -Date: Dec 2011 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Defines the routing procotol this mesh instance - uses to find the optimal paths through the mesh. - -What: /sys/class/net/<mesh_iface>/mesh/vis_mode -Date: May 2010 -Contact: Marek Lindner <lindner_marek@yahoo.de> -Description: - Each batman node only maintains information about its - own local neighborhood, therefore generating graphs - showing the topology of the entire mesh is not easily - feasible without having a central instance to collect - the local topologies from all nodes. This file allows - to activate the collecting (server) mode. diff --git a/Documentation/ABI/testing/sysfs-class-pktcdvd b/Documentation/ABI/testing/sysfs-class-pktcdvd deleted file mode 100644 index b1c3f026335..00000000000 --- a/Documentation/ABI/testing/sysfs-class-pktcdvd +++ /dev/null @@ -1,72 +0,0 @@ -What: /sys/class/pktcdvd/ -Date: Oct. 2006 -KernelVersion: 2.6.20 -Contact: Thomas Maier <balagi@justmail.de> -Description: - -sysfs interface ---------------- - -The pktcdvd module (packet writing driver) creates -these files in the sysfs: -(<devid> is in format major:minor ) - -/sys/class/pktcdvd/ - add (0200) Write a block device id (major:minor) - to create a new pktcdvd device and map - it to the block device. - - remove (0200) Write the pktcdvd device id (major:minor) - to it to remove the pktcdvd device. - - device_map (0444) Shows the device mapping in format: - pktcdvd[0-7] <pktdevid> <blkdevid> - -/sys/class/pktcdvd/pktcdvd[0-7]/ - dev (0444) Device id - uevent (0200) To send an uevent. - -/sys/class/pktcdvd/pktcdvd[0-7]/stat/ - packets_started (0444) Number of started packets. - packets_finished (0444) Number of finished packets. - - kb_written (0444) kBytes written. - kb_read (0444) kBytes read. - kb_read_gather (0444) kBytes read to fill write packets. - - reset (0200) Write any value to it to reset - pktcdvd device statistic values, like - bytes read/written. - -/sys/class/pktcdvd/pktcdvd[0-7]/write_queue/ - size (0444) Contains the size of the bio write - queue. - - congestion_off (0644) If bio write queue size is below - this mark, accept new bio requests - from the block layer. - - congestion_on (0644) If bio write queue size is higher - as this mark, do no longer accept - bio write requests from the block - layer and wait till the pktcdvd - device has processed enough bio's - so that bio write queue size is - below congestion off mark. - A value of <= 0 disables congestion - control. - - -Example: --------- -To use the pktcdvd sysfs interface directly, you can do: - -# create a new pktcdvd device mapped to /dev/hdc -echo "22:0" >/sys/class/pktcdvd/add -cat /sys/class/pktcdvd/device_map -# assuming device pktcdvd0 was created, look at stat's -cat /sys/class/pktcdvd/pktcdvd0/stat/kb_written -# print the device id of the mapped block device -fgrep pktcdvd0 /sys/class/pktcdvd/device_map -# remove device, using pktcdvd0 device id 253:0 -echo "253:0" >/sys/class/pktcdvd/remove diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power deleted file mode 100644 index 78c7baca358..00000000000 --- a/Documentation/ABI/testing/sysfs-class-power +++ /dev/null @@ -1,20 +0,0 @@ -What: /sys/class/power/ds2760-battery.*/charge_now -Date: May 2010 -KernelVersion: 2.6.35 -Contact: Daniel Mack <daniel@caiaq.de> -Description: - This file is writeable and can be used to set the current - coloumb counter value inside the battery monitor chip. This - is needed for unavoidable corrections of aging batteries. - A userspace daemon can monitor the battery charging logic - and once the counter drops out of considerable bounds, take - appropriate action. - -What: /sys/class/power/ds2760-battery.*/charge_full -Date: May 2010 -KernelVersion: 2.6.35 -Contact: Daniel Mack <daniel@caiaq.de> -Description: - This file is writeable and can be used to set the assumed - battery 'full level'. As batteries age, this value has to be - amended over time. diff --git a/Documentation/ABI/testing/sysfs-class-regulator b/Documentation/ABI/testing/sysfs-class-regulator deleted file mode 100644 index e091fa87379..00000000000 --- a/Documentation/ABI/testing/sysfs-class-regulator +++ /dev/null @@ -1,351 +0,0 @@ -What: /sys/class/regulator/.../state -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - state. This reports the regulator enable control, for - regulators which can report that input value. - - This will be one of the following strings: - - 'enabled' - 'disabled' - 'unknown' - - 'enabled' means the regulator output is ON and is supplying - power to the system (assuming no error prevents it). - - 'disabled' means the regulator output is OFF and is not - supplying power to the system (unless some non-Linux - control has enabled it). - - 'unknown' means software cannot determine the state, or - the reported state is invalid. - - NOTE: this field can be used in conjunction with microvolts - or microamps to determine configured regulator output levels. - - -What: /sys/class/regulator/.../status -Description: - Some regulator directories will contain a field called - "status". This reports the current regulator status, for - regulators which can report that output value. - - This will be one of the following strings: - - off - on - error - fast - normal - idle - standby - - "off" means the regulator is not supplying power to the - system. - - "on" means the regulator is supplying power to the system, - and the regulator can't report a detailed operation mode. - - "error" indicates an out-of-regulation status such as being - disabled due to thermal shutdown, or voltage being unstable - because of problems with the input power supply. - - "fast", "normal", "idle", and "standby" are all detailed - regulator operation modes (described elsewhere). They - imply "on", but provide more detail. - - Note that regulator status is a function of many inputs, - not limited to control inputs from Linux. For example, - the actual load presented may trigger "error" status; or - a regulator may be enabled by another user, even though - Linux did not enable it. - - -What: /sys/class/regulator/.../type -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Each regulator directory will contain a field called - type. This holds the regulator type. - - This will be one of the following strings: - - 'voltage' - 'current' - 'unknown' - - 'voltage' means the regulator output voltage can be controlled - by software. - - 'current' means the regulator output current limit can be - controlled by software. - - 'unknown' means software cannot control either voltage or - current limit. - - -What: /sys/class/regulator/.../microvolts -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - microvolts. This holds the regulator output voltage setting - measured in microvolts (i.e. E-6 Volts), for regulators - which can report the control input for voltage. - - NOTE: This value should not be used to determine the regulator - output voltage level as this value is the same regardless of - whether the regulator is enabled or disabled. - - -What: /sys/class/regulator/.../microamps -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - microamps. This holds the regulator output current limit - setting measured in microamps (i.e. E-6 Amps), for regulators - which can report the control input for a current limit. - - NOTE: This value should not be used to determine the regulator - output current level as this value is the same regardless of - whether the regulator is enabled or disabled. - - -What: /sys/class/regulator/.../opmode -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - opmode. This holds the current regulator operating mode, - for regulators which can report that control input value. - - The opmode value can be one of the following strings: - - 'fast' - 'normal' - 'idle' - 'standby' - 'unknown' - - The modes are described in include/linux/regulator/consumer.h - - NOTE: This value should not be used to determine the regulator - output operating mode as this value is the same regardless of - whether the regulator is enabled or disabled. A "status" - attribute may be available to determine the actual mode. - - -What: /sys/class/regulator/.../min_microvolts -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - min_microvolts. This holds the minimum safe working regulator - output voltage setting for this domain measured in microvolts, - for regulators which support voltage constraints. - - NOTE: this will return the string 'constraint not defined' if - the power domain has no min microvolts constraint defined by - platform code. - - -What: /sys/class/regulator/.../max_microvolts -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - max_microvolts. This holds the maximum safe working regulator - output voltage setting for this domain measured in microvolts, - for regulators which support voltage constraints. - - NOTE: this will return the string 'constraint not defined' if - the power domain has no max microvolts constraint defined by - platform code. - - -What: /sys/class/regulator/.../min_microamps -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - min_microamps. This holds the minimum safe working regulator - output current limit setting for this domain measured in - microamps, for regulators which support current constraints. - - NOTE: this will return the string 'constraint not defined' if - the power domain has no min microamps constraint defined by - platform code. - - -What: /sys/class/regulator/.../max_microamps -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - max_microamps. This holds the maximum safe working regulator - output current limit setting for this domain measured in - microamps, for regulators which support current constraints. - - NOTE: this will return the string 'constraint not defined' if - the power domain has no max microamps constraint defined by - platform code. - - -What: /sys/class/regulator/.../name -Date: October 2008 -KernelVersion: 2.6.28 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Each regulator directory will contain a field called - name. This holds a string identifying the regulator for - display purposes. - - NOTE: this will be empty if no suitable name is provided - by platform or regulator drivers. - - -What: /sys/class/regulator/.../num_users -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Each regulator directory will contain a field called - num_users. This holds the number of consumer devices that - have called regulator_enable() on this regulator. - - -What: /sys/class/regulator/.../requested_microamps -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - requested_microamps. This holds the total requested load - current in microamps for this regulator from all its consumer - devices. - - -What: /sys/class/regulator/.../parent -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a link called parent. - This points to the parent or supply regulator if one exists. - -What: /sys/class/regulator/.../suspend_mem_microvolts -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_mem_microvolts. This holds the regulator output - voltage setting for this domain measured in microvolts when - the system is suspended to memory, for voltage regulators - implementing suspend voltage configuration constraints. - -What: /sys/class/regulator/.../suspend_disk_microvolts -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_disk_microvolts. This holds the regulator output - voltage setting for this domain measured in microvolts when - the system is suspended to disk, for voltage regulators - implementing suspend voltage configuration constraints. - -What: /sys/class/regulator/.../suspend_standby_microvolts -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_standby_microvolts. This holds the regulator output - voltage setting for this domain measured in microvolts when - the system is suspended to standby, for voltage regulators - implementing suspend voltage configuration constraints. - -What: /sys/class/regulator/.../suspend_mem_mode -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_mem_mode. This holds the regulator operating mode - setting for this domain when the system is suspended to - memory, for regulators implementing suspend mode - configuration constraints. - -What: /sys/class/regulator/.../suspend_disk_mode -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_disk_mode. This holds the regulator operating mode - setting for this domain when the system is suspended to disk, - for regulators implementing suspend mode configuration - constraints. - -What: /sys/class/regulator/.../suspend_standby_mode -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_standby_mode. This holds the regulator operating mode - setting for this domain when the system is suspended to - standby, for regulators implementing suspend mode - configuration constraints. - -What: /sys/class/regulator/.../suspend_mem_state -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_mem_state. This holds the regulator operating state - when suspended to memory, for regulators implementing suspend - configuration constraints. - - This will be one of the same strings reported by - the "state" attribute. - -What: /sys/class/regulator/.../suspend_disk_state -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_disk_state. This holds the regulator operating state - when suspended to disk, for regulators implementing - suspend configuration constraints. - - This will be one of the same strings reported by - the "state" attribute. - -What: /sys/class/regulator/.../suspend_standby_state -Date: May 2008 -KernelVersion: 2.6.26 -Contact: Liam Girdwood <lrg@slimlogic.co.uk> -Description: - Some regulator directories will contain a field called - suspend_standby_state. This holds the regulator operating - state when suspended to standby, for regulators implementing - suspend configuration constraints. - - This will be one of the same strings reported by - the "state" attribute. diff --git a/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration b/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration deleted file mode 100644 index 4cf1e72222d..00000000000 --- a/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration +++ /dev/null @@ -1,12 +0,0 @@ -What: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock -Date: Oct 2011 -KernelVersion: 3.0 -Contact: Mark Godfrey <mark.godfrey@stericsson.com> -Description: The rtc_calibration attribute allows the userspace to - calibrate the AB8500.s 32KHz Real Time Clock. - Every 60 seconds the AB8500 will correct the RTC's value - by adding to it the value of this attribute. - The range of the attribute is -127 to +127 in units of - 30.5 micro-seconds (half-parts-per-million of the 32KHz clock) -Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration - daemon uses this interface. diff --git a/Documentation/ABI/testing/sysfs-class-scsi_host b/Documentation/ABI/testing/sysfs-class-scsi_host deleted file mode 100644 index 29a4f892e43..00000000000 --- a/Documentation/ABI/testing/sysfs-class-scsi_host +++ /dev/null @@ -1,13 +0,0 @@ -What: /sys/class/scsi_host/hostX/isci_id -Date: June 2011 -Contact: Dave Jiang <dave.jiang@intel.com> -Description: - This file contains the enumerated host ID for the Intel - SCU controller. The Intel(R) C600 Series Chipset SATA/SAS - Storage Control Unit embeds up to two 4-port controllers in - a single PCI device. The controllers are enumerated in order - which usually means the lowest number scsi_host corresponds - with the first controller, but this association is not - guaranteed. The 'isci_id' attribute unambiguously identifies - the controller index: '0' for the first controller, - '1' for the second. diff --git a/Documentation/ABI/testing/sysfs-class-uwb_rc b/Documentation/ABI/testing/sysfs-class-uwb_rc deleted file mode 100644 index 6a5fd072849..00000000000 --- a/Documentation/ABI/testing/sysfs-class-uwb_rc +++ /dev/null @@ -1,146 +0,0 @@ -What: /sys/class/uwb_rc -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - Interfaces for WiMedia Ultra Wideband Common Radio - Platform (UWB) radio controllers. - - Familiarity with the ECMA-368 'High Rate Ultra - Wideband MAC and PHY Specification' is assumed. - -What: /sys/class/uwb_rc/beacon_timeout_ms -Date: July 2008 -KernelVersion: 2.6.27 -Description: - If no beacons are received from a device for at least - this time, the device will be considered to have gone - and it will be removed. The default is 3 superframes - (~197 ms) as required by the specification. - -What: /sys/class/uwb_rc/uwbN/ -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - An individual UWB radio controller. - -What: /sys/class/uwb_rc/uwbN/beacon -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - Write: - - <channel> - - to force a specific channel to be used when beaconing, - or, if <channel> is -1, to prohibit beaconing. If - <channel> is 0, then the default channel selection - algorithm will be used. Valid channels depends on the - radio controller's supported band groups. - - Reading returns the currently active channel, or -1 if - the radio controller is not beaconing. - -What: /sys/class/uwb_rc/uwbN/scan -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - Write: - - <channel> <type> [<bpst offset>] - - to start (or stop) scanning on a channel. <type> is one of: - 0 - scan - 1 - scan outside BP - 2 - scan while inactive - 3 - scanning disabled - 4 - scan (with start time of <bpst offset>) - -What: /sys/class/uwb_rc/uwbN/mac_address -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - The EUI-48, in colon-separated hex octets, for this - radio controller. A write will change the radio - controller's EUI-48 but only do so while the device is - not beaconing or scanning. - -What: /sys/class/uwb_rc/uwbN/wusbhc -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - A symlink to the device (if any) of the WUSB Host - Controller PAL using this radio controller. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/ -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - A neighbour UWB device that has either been detected - as part of a scan or is a member of the radio - controllers beacon group. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/BPST -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - The time (using the radio controllers internal 1 ms - interval superframe timer) of the last beacon from - this device was received. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/DevAddr -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - The current DevAddr of this device in colon separated - hex octets. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/EUI_48 -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - - The EUI-48 of this device in colon separated hex - octets. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/BPST -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/IEs -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - The latest IEs included in this device's beacon, in - space separated hex octets with one IE per line. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/LQE -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - Link Quality Estimate - the Signal to Noise Ratio - (SNR) of all packets received from this device in dB. - This gives an estimate on a suitable PHY rate. Refer - to [ECMA-368] section 13.3 for more details. - -What: /sys/class/uwb_rc/uwbN/<EUI-48>/RSSI -Date: July 2008 -KernelVersion: 2.6.27 -Contact: linux-usb@vger.kernel.org -Description: - Received Signal Strength Indication - the strength of - the received signal in dB. LQE is a more useful - measure of the radio link quality. diff --git a/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc b/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc deleted file mode 100644 index 25b1e751b77..00000000000 --- a/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc +++ /dev/null @@ -1,38 +0,0 @@ -What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_chid -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - Write the CHID (16 space-separated hex octets) for this host controller. - This starts the host controller, allowing it to accept connection from - WUSB devices. - - Set an all zero CHID to stop the host controller. - -What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_trust_timeout -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - Devices that haven't sent a WUSB packet to the host - within 'wusb_trust_timeout' ms are considered to have - disconnected and are removed. The default value of - 4000 ms is the value required by the WUSB - specification. - - Since this relates to security (specifically, the - lifetime of PTKs and GTKs) it should not be changed - from the default. - -What: /sys/class/uwb_rc/uwbN/wusbhc/wusb_phy_rate -Date: August 2009 -KernelVersion: 2.6.32 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The maximum PHY rate to use for all connected devices. - This is only of limited use for testing and - development as the hardware's automatic rate - adaptation is better then this simple control. - - Refer to [ECMA-368] section 10.3.1.1 for the value to - use. diff --git a/Documentation/ABI/testing/sysfs-dev b/Documentation/ABI/testing/sysfs-dev deleted file mode 100644 index a9f2b8b0530..00000000000 --- a/Documentation/ABI/testing/sysfs-dev +++ /dev/null @@ -1,20 +0,0 @@ -What: /sys/dev -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Dan Williams <dan.j.williams@intel.com> -Description: The /sys/dev tree provides a method to look up the sysfs - path for a device using the information returned from - stat(2). There are two directories, 'block' and 'char', - beneath /sys/dev containing symbolic links with names of - the form "<major>:<minor>". These links point to the - corresponding sysfs path for the given device. - - Example: - $ readlink /sys/dev/block/8:32 - ../../block/sdc - - Entries in /sys/dev/char and /sys/dev/block will be - dynamically created and destroyed as devices enter and - leave the system. - -Users: mdadm <linux-raid@vger.kernel.org> diff --git a/Documentation/ABI/testing/sysfs-devices b/Documentation/ABI/testing/sysfs-devices deleted file mode 100644 index 5fcc94358b8..00000000000 --- a/Documentation/ABI/testing/sysfs-devices +++ /dev/null @@ -1,25 +0,0 @@ -What: /sys/devices -Date: February 2006 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: - The /sys/devices tree contains a snapshot of the - internal state of the kernel device tree. Devices will - be added and removed dynamically as the machine runs, - and between different kernel versions, the layout of the - devices within this tree will change. - - Please do not rely on the format of this tree because of - this. If a program wishes to find different things in - the tree, please use the /sys/class structure and rely - on the symlinks there to point to the proper location - within the /sys/devices tree of the individual devices. - Or rely on the uevent messages to notify programs of - devices being added and removed from this tree to find - the location of those devices. - - Note that sometimes not all devices along the directory - chain will have emitted uevent messages, so userspace - programs must be able to handle such occurrences. - -Users: - udev <linux-hotplug-devel@lists.sourceforge.net> diff --git a/Documentation/ABI/testing/sysfs-devices-memory b/Documentation/ABI/testing/sysfs-devices-memory deleted file mode 100644 index 7405de26ee6..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-memory +++ /dev/null @@ -1,85 +0,0 @@ -What: /sys/devices/system/memory -Date: June 2008 -Contact: Badari Pulavarty <pbadari@us.ibm.com> -Description: - The /sys/devices/system/memory contains a snapshot of the - internal state of the kernel memory blocks. Files could be - added or removed dynamically to represent hot-add/remove - operations. -Users: hotplug memory add/remove tools - http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils - -What: /sys/devices/system/memory/memoryX/removable -Date: June 2008 -Contact: Badari Pulavarty <pbadari@us.ibm.com> -Description: - The file /sys/devices/system/memory/memoryX/removable - indicates whether this memory block is removable or not. - This is useful for a user-level agent to determine - identify removable sections of the memory before attempting - potentially expensive hot-remove memory operation -Users: hotplug memory remove tools - http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils - -What: /sys/devices/system/memory/memoryX/phys_device -Date: September 2008 -Contact: Badari Pulavarty <pbadari@us.ibm.com> -Description: - The file /sys/devices/system/memory/memoryX/phys_device - is read-only and is designed to show the name of physical - memory device. Implementation is currently incomplete. - -What: /sys/devices/system/memory/memoryX/phys_index -Date: September 2008 -Contact: Badari Pulavarty <pbadari@us.ibm.com> -Description: - The file /sys/devices/system/memory/memoryX/phys_index - is read-only and contains the section ID in hexadecimal - which is equivalent to decimal X contained in the - memory section directory name. - -What: /sys/devices/system/memory/memoryX/state -Date: September 2008 -Contact: Badari Pulavarty <pbadari@us.ibm.com> -Description: - The file /sys/devices/system/memory/memoryX/state - is read-write. When read, its contents show the - online/offline state of the memory section. When written, - root can toggle the the online/offline state of a removable - memory section (see removable file description above) - using the following commands. - # echo online > /sys/devices/system/memory/memoryX/state - # echo offline > /sys/devices/system/memory/memoryX/state - - For example, if /sys/devices/system/memory/memory22/removable - contains a value of 1 and - /sys/devices/system/memory/memory22/state contains the - string "online" the following command can be executed by - by root to offline that section. - # echo offline > /sys/devices/system/memory/memory22/state -Users: hotplug memory remove tools - http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils - - -What: /sys/devices/system/memoryX/nodeY -Date: October 2009 -Contact: Linux Memory Management list <linux-mm@kvack.org> -Description: - When CONFIG_NUMA is enabled, a symbolic link that - points to the corresponding NUMA node directory. - - For example, the following symbolic link is created for - memory section 9 on node0: - /sys/devices/system/memory/memory9/node0 -> ../../node/node0 - - -What: /sys/devices/system/node/nodeX/memoryY -Date: September 2008 -Contact: Gary Hade <garyhade@us.ibm.com> -Description: - When CONFIG_NUMA is enabled - /sys/devices/system/node/nodeX/memoryY is a symbolic link that - points to the corresponding /sys/devices/system/memory/memoryY - memory section directory. For example, the following symbolic - link is created for memory section 9 on node0. - /sys/devices/system/node/node0/memory9 -> ../../memory/memory9 diff --git a/Documentation/ABI/testing/sysfs-devices-mmc b/Documentation/ABI/testing/sysfs-devices-mmc deleted file mode 100644 index 5a50ab65584..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-mmc +++ /dev/null @@ -1,21 +0,0 @@ -What: /sys/devices/.../mmc_host/mmcX/mmcX:XXXX/enhanced_area_offset -Date: January 2011 -Contact: Chuanxiao Dong <chuanxiao.dong@intel.com> -Description: - Enhanced area is a new feature defined in eMMC4.4 standard. - eMMC4.4 or later card can support such feature. This kind of - area can help to improve the card performance. If the feature - is enabled, this attribute will indicate the start address of - enhanced data area. If not, this attribute will be -EINVAL. - Unit Byte. Format decimal. - -What: /sys/devices/.../mmc_host/mmcX/mmcX:XXXX/enhanced_area_size -Date: January 2011 -Contact: Chuanxiao Dong <chuanxiao.dong@intel.com> -Description: - Enhanced area is a new feature defined in eMMC4.4 standard. - eMMC4.4 or later card can support such feature. This kind of - area can help to improve the card performance. If the feature - is enabled, this attribute will indicate the size of enhanced - data area. If not, this attribute will be -EINVAL. - Unit KByte. Format decimal. diff --git a/Documentation/ABI/testing/sysfs-devices-node b/Documentation/ABI/testing/sysfs-devices-node deleted file mode 100644 index 453a210c3ce..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-node +++ /dev/null @@ -1,7 +0,0 @@ -What: /sys/devices/system/node/nodeX/compact -Date: February 2010 -Contact: Mel Gorman <mel@csn.ul.ie> -Description: - When this file is written to, all memory within that node - will be compacted. When it completes, memory will be freed - into blocks which have as many contiguous pages as possible diff --git a/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget b/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget deleted file mode 100644 index d548eaac230..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget +++ /dev/null @@ -1,21 +0,0 @@ -What: /sys/devices/platform/_UDC_/gadget/suspended -Date: April 2010 -Contact: Fabien Chouteau <fabien.chouteau@barco.com> -Description: - Show the suspend state of an USB composite gadget. - 1 -> suspended - 0 -> resumed - - (_UDC_ is the name of the USB Device Controller driver) - -What: /sys/devices/platform/_UDC_/gadget/gadget-lunX/nofua -Date: July 2010 -Contact: Andy Shevchenko <andy.shevchenko@gmail.com> -Description: - Show or set the reaction on the FUA (Force Unit Access) bit in - the SCSI WRITE(10,12) commands when a gadget in USB Mass - Storage mode. - - Possible values are: - 1 -> ignore the FUA flag - 0 -> obey the FUA flag diff --git a/Documentation/ABI/testing/sysfs-devices-platform-docg3 b/Documentation/ABI/testing/sysfs-devices-platform-docg3 deleted file mode 100644 index 8aa36716882..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-platform-docg3 +++ /dev/null @@ -1,34 +0,0 @@ -What: /sys/devices/platform/docg3/f[0-3]_dps[01]_is_keylocked -Date: November 2011 -KernelVersion: 3.3 -Contact: Robert Jarzmik <robert.jarzmik@free.fr> -Description: - Show whether the floor (0 to 4), protection area (0 or 1) is - keylocked. Each docg3 chip (or floor) has 2 protection areas, - which can cover any part of it, block aligned, called DPS. - The protection has information embedded whether it blocks reads, - writes or both. - The result is: - 0 -> the DPS is not keylocked - 1 -> the DPS is keylocked -Users: None identified so far. - -What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key -Date: November 2011 -KernelVersion: 3.3 -Contact: Robert Jarzmik <robert.jarzmik@free.fr> -Description: - Enter the protection key for the floor (0 to 4), protection area - (0 or 1). Each docg3 chip (or floor) has 2 protection areas, - which can cover any part of it, block aligned, called DPS. - The protection has information embedded whether it blocks reads, - writes or both. - The protection key is a string of 8 bytes (value 0-255). - Entering the correct value toggle the lock, and can be observed - through f[0-3]_dps[01]_is_keylocked. - Possible values are: - - 8 bytes - Typical values are: - - "00000000" - - "12345678" -Users: None identified so far. diff --git a/Documentation/ABI/testing/sysfs-devices-power b/Documentation/ABI/testing/sysfs-devices-power deleted file mode 100644 index 45000f0db4d..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-power +++ /dev/null @@ -1,206 +0,0 @@ -What: /sys/devices/.../power/ -Date: January 2009 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../power directory contains attributes - allowing the user space to check and modify some power - management related properties of given device. - -What: /sys/devices/.../power/wakeup -Date: January 2009 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../power/wakeup attribute allows the user - space to check if the device is enabled to wake up the system - from sleep states, such as the memory sleep state (suspend to - RAM) and hibernation (suspend to disk), and to enable or disable - it to do that as desired. - - Some devices support "wakeup" events, which are hardware signals - used to activate the system from a sleep state. Such devices - have one of the following two values for the sysfs power/wakeup - file: - - + "enabled\n" to issue the events; - + "disabled\n" not to do so; - - In that cases the user space can change the setting represented - by the contents of this file by writing either "enabled", or - "disabled" to it. - - For the devices that are not capable of generating system wakeup - events this file is not present. In that case the device cannot - be enabled to wake up the system from sleep states. - -What: /sys/devices/.../power/control -Date: January 2009 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../power/control attribute allows the user - space to control the run-time power management of the device. - - All devices have one of the following two values for the - power/control file: - - + "auto\n" to allow the device to be power managed at run time; - + "on\n" to prevent the device from being power managed; - - The default for all devices is "auto", which means that they may - be subject to automatic power management, depending on their - drivers. Changing this attribute to "on" prevents the driver - from power managing the device at run time. Doing that while - the device is suspended causes it to be woken up. - -What: /sys/devices/.../power/async -Date: January 2009 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../async attribute allows the user space to - enable or diasble the device's suspend and resume callbacks to - be executed asynchronously (ie. in separate threads, in parallel - with the main suspend/resume thread) during system-wide power - transitions (eg. suspend to RAM, hibernation). - - All devices have one of the following two values for the - power/async file: - - + "enabled\n" to permit the asynchronous suspend/resume; - + "disabled\n" to forbid it; - - The value of this attribute may be changed by writing either - "enabled", or "disabled" to it. - - It generally is unsafe to permit the asynchronous suspend/resume - of a device unless it is certain that all of the PM dependencies - of the device are known to the PM core. However, for some - 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 not present. - -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 not present. - -What: /sys/devices/.../power/wakeup_abort_count -Date: February 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../wakeup_abort_count attribute contains the - number of times the processing of a wakeup event associated with - the device might have aborted system transition into a sleep - state in progress. This attribute is read-only. If the device - is not enabled to wake up the system from sleep states, this - attribute is not present. - -What: /sys/devices/.../power/wakeup_expire_count -Date: February 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../wakeup_expire_count attribute contains the - number of times a wakeup event associated with the device has - been reported with a timeout that expired. This attribute is - read-only. If the device is not enabled to wake up the system - from sleep states, this attribute is not present. - -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 not present. - -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 not present. - -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 not present. - -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 not present. - -What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms -Date: February 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute - contains the total time the device has been preventing - opportunistic transitions to sleep states from occuring. - This attribute is read-only. If the device is not enabled to - wake up the system from sleep states, this attribute is not - present. - -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. - -What: /sys/devices/.../power/pm_qos_latency_us -Date: March 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/devices/.../power/pm_qos_resume_latency_us attribute - contains the PM QoS resume latency limit for the given device, - which is the maximum allowed time it can take to resume the - device, after it has been suspended at run time, from a resume - request to the moment the device will be ready to process I/O, - in microseconds. If it is equal to 0, however, this means that - the PM QoS resume latency may be arbitrary. - - Not all drivers support this attribute. If it isn't supported, - it is not present. - - This attribute has no effect on system-wide suspend/resume and - hibernation. diff --git a/Documentation/ABI/testing/sysfs-devices-soc b/Documentation/ABI/testing/sysfs-devices-soc deleted file mode 100644 index 6d9cc253f2b..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-soc +++ /dev/null @@ -1,58 +0,0 @@ -What: /sys/devices/socX -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - The /sys/devices/ directory contains a sub-directory for each - System-on-Chip (SoC) device on a running platform. Information - regarding each SoC can be obtained by reading sysfs files. This - functionality is only available if implemented by the platform. - - The directory created for each SoC will also house information - about devices which are commonly contained in /sys/devices/platform. - It has been agreed that if an SoC device exists, its supported - devices would be better suited to appear as children of that SoC. - -What: /sys/devices/socX/machine -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - Read-only attribute common to all SoCs. Contains the SoC machine - name (e.g. Ux500). - -What: /sys/devices/socX/family -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - Read-only attribute common to all SoCs. Contains SoC family name - (e.g. DB8500). - -What: /sys/devices/socX/soc_id -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - Read-only attribute supported by most SoCs. In the case of - ST-Ericsson's chips this contains the SoC serial number. - -What: /sys/devices/socX/revision -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - Read-only attribute supported by most SoCs. Contains the SoC's - manufacturing revision number. - -What: /sys/devices/socX/process -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - Read-only attribute supported ST-Ericsson's silicon. Contains the - the process by which the silicon chip was manufactured. - -What: /sys/bus/soc -Date: January 2012 -contact: Lee Jones <lee.jones@linaro.org> -Description: - The /sys/bus/soc/ directory contains the usual sub-folders - expected under most buses. /sys/bus/soc/devices is of particular - interest, as it contains a symlink for each SoC device found on - the system. Each symlink points back into the aforementioned - /sys/devices/socX devices. diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu deleted file mode 100644 index 5dab36448b4..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-system-cpu +++ /dev/null @@ -1,178 +0,0 @@ -What: /sys/devices/system/cpu/ -Date: pre-git history -Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description: - A collection of both global and individual CPU attributes - - Individual CPU attributes are contained in subdirectories - named by the kernel's logical CPU number, e.g.: - - /sys/devices/system/cpu/cpu#/ - -What: /sys/devices/system/cpu/kernel_max - /sys/devices/system/cpu/offline - /sys/devices/system/cpu/online - /sys/devices/system/cpu/possible - /sys/devices/system/cpu/present -Date: December 2008 -Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description: CPU topology files that describe kernel limits related to - hotplug. Briefly: - - kernel_max: the maximum cpu index allowed by the kernel - configuration. - - offline: cpus that are not online because they have been - HOTPLUGGED off or exceed the limit of cpus allowed by the - kernel configuration (kernel_max above). - - online: cpus that are online and being scheduled. - - possible: cpus that have been allocated resources and can be - brought online if they are present. - - present: cpus that have been identified as being present in - the system. - - See Documentation/cputopology.txt for more information. - - -What: /sys/devices/system/cpu/probe - /sys/devices/system/cpu/release -Date: November 2009 -Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description: Dynamic addition and removal of CPU's. This is not hotplug - removal, this is meant complete removal/addition of the CPU - from the system. - - probe: writes to this file will dynamically add a CPU to the - system. Information written to the file to add CPU's is - architecture specific. - - release: writes to this file dynamically remove a CPU from - the system. Information writtento the file to remove CPU's - is architecture specific. - -What: /sys/devices/system/cpu/cpu#/node -Date: October 2009 -Contact: Linux memory management mailing list <linux-mm@kvack.org> -Description: Discover NUMA node a CPU belongs to - - When CONFIG_NUMA is enabled, a symbolic link that points - to the corresponding NUMA node directory. - - For example, the following symlink is created for cpu42 - in NUMA node 2: - - /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2 - - -What: /sys/devices/system/cpu/cpu#/node -Date: October 2009 -Contact: Linux memory management mailing list <linux-mm@kvack.org> -Description: Discover NUMA node a CPU belongs to - - When CONFIG_NUMA is enabled, a symbolic link that points - to the corresponding NUMA node directory. - - For example, the following symlink is created for cpu42 - in NUMA node 2: - - /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2 - - -What: /sys/devices/system/cpu/cpu#/topology/core_id - /sys/devices/system/cpu/cpu#/topology/core_siblings - /sys/devices/system/cpu/cpu#/topology/core_siblings_list - /sys/devices/system/cpu/cpu#/topology/physical_package_id - /sys/devices/system/cpu/cpu#/topology/thread_siblings - /sys/devices/system/cpu/cpu#/topology/thread_siblings_list -Date: December 2008 -Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description: CPU topology files that describe a logical CPU's relationship - to other cores and threads in the same physical package. - - One cpu# directory is created per logical CPU in the system, - e.g. /sys/devices/system/cpu/cpu42/. - - Briefly, the files above are: - - core_id: the CPU core ID of cpu#. Typically it is the - hardware platform's identifier (rather than the kernel's). - The actual value is architecture and platform dependent. - - core_siblings: internal kernel map of cpu#'s hardware threads - within the same physical_package_id. - - core_siblings_list: human-readable list of the logical CPU - numbers within the same physical_package_id as cpu#. - - physical_package_id: physical package id of cpu#. Typically - corresponds to a physical socket number, but the actual value - is architecture and platform dependent. - - thread_siblings: internel kernel map of cpu#'s hardware - threads within the same core as cpu# - - thread_siblings_list: human-readable list of cpu#'s hardware - threads within the same core as cpu# - - See Documentation/cputopology.txt for more information. - - -What: /sys/devices/system/cpu/cpuidle/current_driver - /sys/devices/system/cpu/cpuidle/current_governer_ro -Date: September 2007 -Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description: Discover cpuidle policy and mechanism - - Various CPUs today support multiple idle levels that are - differentiated by varying exit latencies and power - consumption during idle. - - Idle policy (governor) is differentiated from idle mechanism - (driver) - - current_driver: displays current idle mechanism - - current_governor_ro: displays current idle policy - - See files in Documentation/cpuidle/ for more information. - - -What: /sys/devices/system/cpu/cpu#/cpufreq/* -Date: pre-git history -Contact: cpufreq@vger.kernel.org -Description: Discover and change clock speed of CPUs - - Clock scaling allows you to change the clock speed of the - CPUs on the fly. This is a nice method to save battery - power, because the lower the clock speed, the less power - the CPU consumes. - - There are many knobs to tweak in this directory. - - See files in Documentation/cpu-freq/ for more information. - - In particular, read Documentation/cpu-freq/user-guide.txt - to learn how to control the knobs. - - -What: /sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1} -Date: August 2008 -KernelVersion: 2.6.27 -Contact: discuss@x86-64.org -Description: Disable L3 cache indices - - These files exist in every CPU's cache/index3 directory. Each - cache_disable_{0,1} file corresponds to one disable slot which - can be used to disable a cache index. Reading from these files - on a processor with this functionality will return the currently - disabled index for that node. There is one L3 structure per - node, or per internal node on MCM machines. Writing a valid - index to one of these files will cause the specificed cache - index to be disabled. - - All AMD processors with L3 caches provide this functionality. - For details, see BKDGs at - http://developer.amd.com/documentation/guides/Pages/default.aspx diff --git a/Documentation/ABI/testing/sysfs-devices-system-ibm-rtl b/Documentation/ABI/testing/sysfs-devices-system-ibm-rtl deleted file mode 100644 index b82deeaec31..00000000000 --- a/Documentation/ABI/testing/sysfs-devices-system-ibm-rtl +++ /dev/null @@ -1,22 +0,0 @@ -What: state -Date: Sep 2010 -KernelVersion: 2.6.37 -Contact: Vernon Mauery <vernux@us.ibm.com> -Description: The state file allows a means by which to change in and - out of Premium Real-Time Mode (PRTM), as well as the - ability to query the current state. - 0 => PRTM off - 1 => PRTM enabled -Users: The ibm-prtm userspace daemon uses this interface. - - -What: version -Date: Sep 2010 -KernelVersion: 2.6.37 -Contact: Vernon Mauery <vernux@us.ibm.com> -Description: The version file provides a means by which to query - the RTL table version that lives in the Extended - BIOS Data Area (EBDA). -Users: The ibm-prtm userspace daemon uses this interface. - - diff --git a/Documentation/ABI/testing/sysfs-driver-hid b/Documentation/ABI/testing/sysfs-driver-hid deleted file mode 100644 index b6490e14fe8..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid +++ /dev/null @@ -1,10 +0,0 @@ -What: For USB devices : /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor - For BT devices : /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor - Symlink : /sys/class/hidraw/hidraw<num>/device/report_descriptor -Date: Jan 2011 -KernelVersion: 2.0.39 -Contact: Alan Ott <alan@signal11.us> -Description: When read, this file returns the device's raw binary HID - report descriptor. - This file cannot be written. -Users: HIDAPI library (http://www.signal11.us/oss/hidapi) diff --git a/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff b/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff deleted file mode 100644 index 167d9032b97..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff +++ /dev/null @@ -1,7 +0,0 @@ -What: /sys/module/hid_logitech/drivers/hid:logitech/<dev>/range. -Date: July 2011 -KernelVersion: 3.2 -Contact: Michal Malý <madcatxster@gmail.com> -Description: Display minimum, maximum and current range of the steering - wheel. Writing a value within min and max boundaries sets the - range of the wheel. diff --git a/Documentation/ABI/testing/sysfs-driver-hid-multitouch b/Documentation/ABI/testing/sysfs-driver-hid-multitouch deleted file mode 100644 index f79839d1af3..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-multitouch +++ /dev/null @@ -1,9 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/quirks -Date: November 2011 -Contact: Benjamin Tissoires <benjamin.tissoires@gmail.com> -Description: The integer value of this attribute corresponds to the - quirks actually in place to handle the device's protocol. - When read, this attribute returns the current settings (see - MT_QUIRKS_* in hid-multitouch.c). - When written this attribute change on the fly the quirks, then - the protocol to handle the device. diff --git a/Documentation/ABI/testing/sysfs-driver-hid-picolcd b/Documentation/ABI/testing/sysfs-driver-hid-picolcd deleted file mode 100644 index 08579e7e1e8..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-picolcd +++ /dev/null @@ -1,43 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/operation_mode -Date: March 2010 -Contact: Bruno Prémont <bonbons@linux-vserver.org> -Description: Make it possible to switch the PicoLCD device between LCD - (firmware) and bootloader (flasher) operation modes. - - Reading: returns list of available modes, the active mode being - enclosed in brackets ('[' and ']') - - Writing: causes operation mode switch. Permitted values are - the non-active mode names listed when read. - - Note: when switching mode the current PicoLCD HID device gets - disconnected and reconnects after above delay (see attribute - operation_mode_delay for its value). - - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/operation_mode_delay -Date: April 2010 -Contact: Bruno Prémont <bonbons@linux-vserver.org> -Description: Delay PicoLCD waits before restarting in new mode when - operation_mode has changed. - - Reading/Writing: It is expressed in ms and permitted range is - 0..30000ms. - - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/fb_update_rate -Date: March 2010 -Contact: Bruno Prémont <bonbons@linux-vserver.org> -Description: Make it possible to adjust defio refresh rate. - - Reading: returns list of available refresh rates (expressed in Hz), - the active refresh rate being enclosed in brackets ('[' and ']') - - Writing: accepts new refresh rate expressed in integer Hz - within permitted rates. - - Note: As device can barely do 2 complete refreshes a second - it only makes sense to adjust this value if only one or two - tiles get changed and it's not appropriate to expect the application - to flush it's tiny changes explicitely at higher than default rate. - diff --git a/Documentation/ABI/testing/sysfs-driver-hid-prodikeys b/Documentation/ABI/testing/sysfs-driver-hid-prodikeys deleted file mode 100644 index 05d988c29a8..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-prodikeys +++ /dev/null @@ -1,29 +0,0 @@ -What: /sys/bus/hid/drivers/prodikeys/.../channel -Date: April 2010 -KernelVersion: 2.6.34 -Contact: Don Prince <dhprince.devel@yahoo.co.uk> -Description: - Allows control (via software) the midi channel to which - that the pc-midi keyboard will output.midi data. - Range: 0..15 - Type: Read/write -What: /sys/bus/hid/drivers/prodikeys/.../sustain -Date: April 2010 -KernelVersion: 2.6.34 -Contact: Don Prince <dhprince.devel@yahoo.co.uk> -Description: - Allows control (via software) the sustain duration of a - note held by the pc-midi driver. - 0 means sustain mode is disabled. - Range: 0..5000 (milliseconds) - Type: Read/write -What: /sys/bus/hid/drivers/prodikeys/.../octave -Date: April 2010 -KernelVersion: 2.6.34 -Contact: Don Prince <dhprince.devel@yahoo.co.uk> -Description: - Controls the octave shift modifier in the pc-midi driver. - The octave can be shifted via software up/down 2 octaves. - 0 means the no ocatve shift. - Range: -2..2 (minus 2 to plus 2) - Type: Read/Write diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-arvo b/Documentation/ABI/testing/sysfs-driver-hid-roccat-arvo deleted file mode 100644 index 55e281b0071..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-arvo +++ /dev/null @@ -1,53 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/actual_profile -Date: Januar 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 1-5. - When read, this attribute returns the number of the actual - profile which is also the profile that's active on device startup. - When written this attribute activates the selected profile - immediately. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/button -Date: Januar 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The keyboard can store short macros with consist of 1 button with - several modifier keys internally. - When written, this file lets one set the sequence for a specific - button for a specific profile. Button and profile numbers are - included in written data. The data has to be 24 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>/arvo/roccatarvo<minor>/info -Date: Januar 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When read, this file returns some info about the device like the - installed firmware version. - The size of the data is 8 bytes in size. - 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>/arvo/roccatarvo<minor>/key_mask -Date: Januar 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The keyboard lets the user deactivate 5 certain keys like the - windows and application keys, to protect the user from the outcome - of accidentally pressing them. - The integer value of this attribute has bits 0-4 set depending - on the state of the corresponding key. - When read, this file returns the current state of the buttons. - When written, the given buttons are activated/deactivated - immediately. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/mode_key -Date: Januar 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The keyboard has a condensed layout without num-lock key. - Instead it uses a mode-key which activates a gaming mode where - the assignment of the number block changes. - The integer value of this attribute ranges from 0 (OFF) to 1 (ON). - When read, this file returns the actual state of the key. - When written, the key is activated/deactivated immediately. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-isku b/Documentation/ABI/testing/sysfs-driver-hid-roccat-isku deleted file mode 100644 index 189dc43891b..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-isku +++ /dev/null @@ -1,135 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/actual_profile -Date: June 2011 -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 actual - profile. This value is persistent, so its equivalent to the - profile that's active when the device is powered on next time. - When written, this file sets the number of the startup profile - and the device activates this profile immediately. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/info -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When read, this file returns general data like firmware version. - The data is 6 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>/isku/roccatisku<minor>/key_mask -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one deactivate certain keys like - windows and application keys, to prevent accidental presses. - Profile number for which this settings occur is included in - written data. The data has to be 6 bytes long. - 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>/isku/roccatisku<minor>/keys_capslock -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the - capslock key for a specific profile. Profile number is included - in written data. The data has to be 6 bytes long. - 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>/isku/roccatisku<minor>/keys_easyzone -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the - easyzone keys for a specific profile. Profile number is included - in written data. The data has to be 65 bytes long. - 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>/isku/roccatisku<minor>/keys_function -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the - function keys for a specific profile. Profile number is included - in written data. The data has to be 41 bytes long. - 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>/isku/roccatisku<minor>/keys_macro -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the macro - keys for a specific profile. Profile number is included in - written data. The data has to be 35 bytes long. - 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>/isku/roccatisku<minor>/keys_media -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the media - keys for a specific profile. Profile number is included in - written data. The data has to be 29 bytes long. - 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>/isku/roccatisku<minor>/keys_thumbster -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the function of the - thumbster keys for a specific profile. Profile number is included - in written data. The data has to be 23 bytes long. - 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>/isku/roccatisku<minor>/last_set -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the time in secs since - epoch in which the last configuration took place. - The data has to be 20 bytes long. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/light -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one set the backlight intensity for - a specific profile. Profile number is included in written data. - The data has to be 10 bytes long. - 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>/isku/roccatisku<minor>/macro -Date: June 2011 -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>/isku/roccatisku<minor>/control -Date: June 2011 -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>/isku/roccatisku<minor>/talk -Date: June 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written, this file lets one trigger easyshift functionality - from the host. - The data has to be 16 bytes long. - This file is writeonly. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kone b/Documentation/ABI/testing/sysfs-driver-hid-roccat-kone deleted file mode 100644 index 3ca3971109b..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kone +++ /dev/null @@ -1,106 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/actual_dpi -Date: March 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: It is possible to switch the dpi setting of the mouse with the - press of a button. - When read, this file returns the raw number of the actual dpi - setting reported by the mouse. This number has to be further - processed to receive the real dpi value. - - VALUE DPI - 1 800 - 2 1200 - 3 1600 - 4 2000 - 5 2400 - 6 3200 - - 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>/kone/roccatkone<minor>/actual_profile -Date: March 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When read, this file returns the number of the actual profile. - 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>/kone/roccatkone<minor>/firmware_version -Date: March 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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/profile[1-5] -Date: March 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 holds information like button - mappings, sensitivity, the colors of the 5 leds and light - effects. - When read, these files return the respective profile. The - returned data is 975 bytes in size. - When written, this file lets one write the respective profile - data back to the mouse. The data has to be 975 bytes long. - The mouse will reject invalid data, whereas the profile number - stored in the profile doesn't need to fit the number of the - store. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/settings -Date: March 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 36 bytes and holds information like the - startup_profile, tcu state and calibration_data. - When written, this file lets write settings back to the mouse. - The data has to be 36 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>/kone/roccatkone<minor>/startup_profile -Date: March 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 1 to 5. - When read, this attribute returns the number of the profile - that's active when the mouse is powered on. - When written, this file sets the number of the startup profile - and the mouse activates this profile immediately. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/tcu -Date: March 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The mouse has a "Tracking Control Unit" which lets the user - calibrate the laser power to fit the mousepad surface. - When read, this file returns the current state of the TCU, - where 0 means off and 1 means on. - Writing 0 in this file will switch the TCU off. - Writing 1 in this file will start the calibration which takes - around 6 seconds to complete and activates the TCU. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/weight -Date: March 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The mouse can be equipped with one of four supplied weights - ranging from 5 to 20 grams which are recognized by the mouse - and its value can be read out. When read, this file returns the - raw value returned by the mouse which eases further processing - in other software. - The values map to the weights as follows: - - VALUE WEIGHT - 0 none - 1 5g - 2 10g - 3 15g - 4 20g - - This file is readonly. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus b/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus deleted file mode 100644 index 65e6e5dd67e..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus +++ /dev/null @@ -1,120 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/actual_profile -Date: October 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 actual - profile. This value is persistent, so its equivalent to the - profile that's active when the mouse is powered on next time. - When written, this file sets the number of the startup profile - and the mouse activates this profile immediately. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/firmware_version -Date: October 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 121 means 1.21 - 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>/koneplus/roccatkoneplus<minor>/macro -Date: October 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The mouse can store a macro with max 500 key/button strokes - internally. - When written, this file lets one set the sequence for a specific - button for a specific profile. Button and profile numbers are - included in written data. The data has to be 2082 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>/koneplus/roccatkoneplus<minor>/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 information about button layout. - When written, this file lets one write the respective profile - buttons back to the mouse. The data has to be 77 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>/koneplus/roccatkoneplus<minor>/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 information about button layout. - When read, these files return the respective profile buttons. - The returned data is 77 bytes in size. - 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>/koneplus/roccatkoneplus<minor>/profile_settings -Date: October 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 information 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>/koneplus/roccatkoneplus<minor>/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 information like resolution, sensitivity - and light effects. - When read, these files return the respective profile settings. - The returned data is 43 bytes in size. - 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>/koneplus/roccatkoneplus<minor>/sensor -Date: October 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The mouse has a tracking- and a distance-control-unit. These - can be activated/deactivated and the lift-off distance can be - set. The data has to be 6 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>/koneplus/roccatkoneplus<minor>/talk -Date: May 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: Used to active some easy* functions of the mouse from outside. - The data has to be 16 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>/koneplus/roccatkoneplus<minor>/tcu -Date: October 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When written a calibration process for the tracking control unit - can be initiated/cancelled. - 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>/koneplus/roccatkoneplus<minor>/tcu_image -Date: October 2010 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: When read the mouse returns a 30x30 pixel image of the - sampled underground. This works only in the course of a - calibration process initiated with tcu. - The returned data is 1028 bytes in size. - This file is readonly. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus b/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus deleted file mode 100644 index 20f937c9d84..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus +++ /dev/null @@ -1,100 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_cpi -Date: January 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 1-4. - When read, this attribute returns the number of the active - cpi level. - 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>/kovaplus/roccatkovaplus<minor>/actual_profile -Date: January 2011 -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 active - profile. - When written, the mouse activates this profile immediately. - The profile that's active when powered down is the same that's - active when the mouse is powered on. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x -Date: January 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 1-10. - When read, this attribute returns the number of the actual - sensitivity in x direction. - 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>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_y -Date: January 2011 -Contact: Stefan Achatz <erazor_de@users.sourceforge.net> -Description: The integer value of this attribute ranges from 1-10. - When read, this attribute returns the number of the actual - sensitivity in y direction. - 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>/kovaplus/roccatkovaplus<minor>/firmware_version -Date: January 2011 -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 121 means 1.21 - 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>/kovaplus/roccatkovaplus<minor>/profile_buttons -Date: January 2011 -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 information about button layout. - When written, this file lets one write the respective profile - buttons back to the mouse. The data has to be 23 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>/kovaplus/roccatkovaplus<minor>/profile[1-5]_buttons -Date: January 2011 -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 information about button layout. - When read, these files return the respective profile buttons. - The returned data is 23 bytes in size. - 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>/kovaplus/roccatkovaplus<minor>/profile_settings -Date: January 2011 -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 information 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 16 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>/kovaplus/roccatkovaplus<minor>/profile[1-5]_settings -Date: January 2011 -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 information like resolution, sensitivity - and light effects. - When read, these files return the respective profile settings. - The returned data is 16 bytes in size. - This file is readonly. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra b/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra deleted file mode 100644 index 3f8de50e4ff..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra +++ /dev/null @@ -1,107 +0,0 @@ -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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 information 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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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 information 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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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 information 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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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 information about button layout. - When read, these files return the respective profile buttons. - The returned data is 19 bytes in size. - 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>/pyra/roccatpyra<minor>/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. -Users: http://roccat.sourceforge.net - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/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. -Users: http://roccat.sourceforge.net diff --git a/Documentation/ABI/testing/sysfs-driver-hid-wiimote b/Documentation/ABI/testing/sysfs-driver-hid-wiimote deleted file mode 100644 index 3d98009f447..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-hid-wiimote +++ /dev/null @@ -1,22 +0,0 @@ -What: /sys/bus/hid/drivers/wiimote/<dev>/led1 -What: /sys/bus/hid/drivers/wiimote/<dev>/led2 -What: /sys/bus/hid/drivers/wiimote/<dev>/led3 -What: /sys/bus/hid/drivers/wiimote/<dev>/led4 -Date: July 2011 -KernelVersion: 3.1 -Contact: David Herrmann <dh.herrmann@googlemail.com> -Description: Make it possible to set/get current led state. Reading from it - returns 0 if led is off and 1 if it is on. Writing 0 to it - disables the led, writing 1 enables it. - -What: /sys/bus/hid/drivers/wiimote/<dev>/extension -Date: August 2011 -KernelVersion: 3.2 -Contact: David Herrmann <dh.herrmann@googlemail.com> -Description: This file contains the currently connected and initialized - extensions. It can be one of: none, motionp, nunchuck, classic, - motionp+nunchuck, motionp+classic - motionp is the official Nintendo Motion+ extension, nunchuck is - the official Nintendo Nunchuck extension and classic is the - Nintendo Classic Controller extension. The motionp extension can - be combined with the other two. diff --git a/Documentation/ABI/testing/sysfs-driver-samsung-laptop b/Documentation/ABI/testing/sysfs-driver-samsung-laptop deleted file mode 100644 index 678819a3f8b..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-samsung-laptop +++ /dev/null @@ -1,37 +0,0 @@ -What: /sys/devices/platform/samsung/performance_level -Date: January 1, 2010 -KernelVersion: 2.6.33 -Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Description: Some Samsung laptops have different "performance levels" - that are can be modified by a function key, and by this - sysfs file. These values don't always make a whole lot - of sense, but some users like to modify them to keep - their fans quiet at all costs. Reading from this file - will show the current performance level. Writing to the - file can change this value. - Valid options: - "silent" - "normal" - "overclock" - Note that not all laptops support all of these options. - Specifically, not all support the "overclock" option, - and it's still unknown if this value even changes - anything, other than making the user feel a bit better. - -What: /sys/devices/platform/samsung/battery_life_extender -Date: December 1, 2011 -KernelVersion: 3.3 -Contact: Corentin Chary <corentin.chary@gmail.com> -Description: Max battery charge level can be modified, battery cycle - life can be extended by reducing the max battery charge - level. - 0 means normal battery mode (100% charge) - 1 means battery life extender mode (80% charge) - -What: /sys/devices/platform/samsung/usb_charge -Date: December 1, 2011 -KernelVersion: 3.3 -Contact: Corentin Chary <corentin.chary@gmail.com> -Description: Use your USB ports to charge devices, even - when your laptop is powered off. - 1 means enabled, 0 means disabled. diff --git a/Documentation/ABI/testing/sysfs-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom deleted file mode 100644 index 8d55a83d692..00000000000 --- a/Documentation/ABI/testing/sysfs-driver-wacom +++ /dev/null @@ -1,82 +0,0 @@ -What: /sys/class/hidraw/hidraw*/device/speed -Date: April 2010 -Kernel Version: 2.6.35 -Contact: linux-bluetooth@vger.kernel.org -Description: - The /sys/class/hidraw/hidraw*/device/speed file controls - reporting speed of Wacom bluetooth tablet. Reading from - this file returns 1 if tablet reports in high speed mode - or 0 otherwise. Writing to this file one of these values - switches reporting speed. - -What: /sys/class/leds/0005\:056A\:00BD.0001\:selector\:*/ -Date: May 2012 -Kernel Version: 3.5 -Contact: linux-bluetooth@vger.kernel.org -Description: - LED selector for Intuos4 WL. There are 4 leds, but only one LED - can be lit at a time. Max brightness is 127. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - Attribute group for control of the status LEDs and the OLEDs. - This attribute group is only available for Intuos 4 M, L, - and XL (with LEDs and OLEDs), Intuos 5 (LEDs only), and Cintiq - 21UX2 and Cintiq 24HD (LEDs only). Therefore its presence - implicitly signifies the presence of said LEDs and OLEDs on the - tablet device. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - Writing to this file sets the status LED luminance (1..127) - when the stylus does not touch the tablet surface, and no - button is pressed on the stylus. This luminance level is - normally lower than the level when a button is pressed. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status1_luminance -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - Writing to this file sets the status LED luminance (1..127) - when the stylus touches the tablet surface, or any button is - pressed on the stylus. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led0_select -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - Writing to this file sets which one of the four (for Intuos 4 - and Intuos 5) or of the right four (for Cintiq 21UX2 and Cintiq - 24HD) status LEDs is active (0..3). The other three LEDs on the - same side are always inactive. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select -Date: September 2011 -Contact: linux-input@vger.kernel.org -Description: - Writing to this file sets which one of the left four (for Cintiq 21UX2 - and Cintiq 24HD) status LEDs is active (0..3). The other three LEDs on - the left are always inactive. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/buttons_luminance -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - Writing to this file sets the overall luminance level (0..15) - of all eight button OLED displays. - -What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/button<n>_rawimg -Date: August 2011 -Contact: linux-input@vger.kernel.org -Description: - When writing a 1024 byte raw image in Wacom Intuos 4 - interleaving format to the file, the image shows up on Button N - of the device. The image is a 64x32 pixel 4-bit gray image. The - 1024 byte binary is split up into 16x 64 byte chunks. Each 64 - byte chunk encodes the image data for two consecutive lines on - the display. The low nibble of each byte contains the first - line, and the high nibble contains the second line. diff --git a/Documentation/ABI/testing/sysfs-firmware-acpi b/Documentation/ABI/testing/sysfs-firmware-acpi deleted file mode 100644 index dd930c8db41..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-acpi +++ /dev/null @@ -1,170 +0,0 @@ -What: /sys/firmware/acpi/bgrt/ -Date: January 2012 -Contact: Matthew Garrett <mjg@redhat.com> -Description: - The BGRT is an ACPI 5.0 feature that allows the OS - to obtain a copy of the firmware boot splash and - some associated metadata. This is intended to be used - by boot splash applications in order to interact with - the firmware boot splash in order to avoid jarring - transitions. - - image: The image bitmap. Currently a 32-bit BMP. - status: 1 if the image is valid, 0 if firmware invalidated it. - type: 0 indicates image is in BMP format. - version: The version of the BGRT. Currently 1. - xoffset: The number of pixels between the left of the screen - and the left edge of the image. - yoffset: The number of pixels between the top of the screen - and the top edge of the image. - -What: /sys/firmware/acpi/interrupts/ -Date: February 2008 -Contact: Len Brown <lenb@kernel.org> -Description: - All ACPI interrupts are handled via a single IRQ, - the System Control Interrupt (SCI), which appears - as "acpi" in /proc/interrupts. - - However, one of the main functions of ACPI is to make - the platform understand random hardware without - special driver support. So while the SCI handles a few - well known (fixed feature) interrupts sources, such - as the power button, it can also handle a variable - number of a "General Purpose Events" (GPE). - - A GPE vectors to a specified handler in AML, which - can do a anything the BIOS writer wants from - OS context. GPE 0x12, for example, would vector - to a level or edge handler called _L12 or _E12. - The handler may do its business and return. - Or the handler may send send a Notify event - to a Linux device driver registered on an ACPI device, - such as a battery, or a processor. - - To figure out where all the SCI's are coming from, - /sys/firmware/acpi/interrupts contains a file listing - every possible source, and the count of how many - times it has triggered. - - $ cd /sys/firmware/acpi/interrupts - $ grep . * - error: 0 - ff_gbl_lock: 0 enable - ff_pmtimer: 0 invalid - ff_pwr_btn: 0 enable - ff_rt_clk: 2 disable - ff_slp_btn: 0 invalid - gpe00: 0 invalid - gpe01: 0 enable - gpe02: 108 enable - gpe03: 0 invalid - gpe04: 0 invalid - gpe05: 0 invalid - gpe06: 0 enable - gpe07: 0 enable - gpe08: 0 invalid - gpe09: 0 invalid - gpe0A: 0 invalid - gpe0B: 0 invalid - gpe0C: 0 invalid - gpe0D: 0 invalid - gpe0E: 0 invalid - gpe0F: 0 invalid - gpe10: 0 invalid - gpe11: 0 invalid - gpe12: 0 invalid - gpe13: 0 invalid - gpe14: 0 invalid - gpe15: 0 invalid - gpe16: 0 invalid - gpe17: 1084 enable - gpe18: 0 enable - gpe19: 0 invalid - gpe1A: 0 invalid - gpe1B: 0 invalid - gpe1C: 0 invalid - gpe1D: 0 invalid - gpe1E: 0 invalid - gpe1F: 0 invalid - gpe_all: 1192 - sci: 1194 - sci_not: 0 - - sci - The number of times the ACPI SCI - has been called and claimed an interrupt. - - sci_not - The number of times the ACPI SCI - has been called and NOT claimed an interrupt. - - gpe_all - count of SCI caused by GPEs. - - gpeXX - count for individual GPE source - - ff_gbl_lock - Global Lock - - ff_pmtimer - PM Timer - - ff_pwr_btn - Power Button - - ff_rt_clk - Real Time Clock - - ff_slp_btn - Sleep Button - - error - an interrupt that can't be accounted for above. - - invalid: it's either a GPE or a Fixed Event that - doesn't have an event handler. - - disable: the GPE/Fixed Event is valid but disabled. - - enable: the GPE/Fixed Event is valid and enabled. - - Root has permission to clear any of these counters. Eg. - # echo 0 > gpe11 - - All counters can be cleared by clearing the total "sci": - # echo 0 > sci - - None of these counters has an effect on the function - of the system, they are simply statistics. - - Besides this, user can also write specific strings to these files - to enable/disable/clear ACPI interrupts in user space, which can be - used to debug some ACPI interrupt storm issues. - - Note that only writting to VALID GPE/Fixed Event is allowed, - i.e. user can only change the status of runtime GPE and - Fixed Event with event handler installed. - - Let's take power button fixed event for example, please kill acpid - and other user space applications so that the machine won't shutdown - when pressing the power button. - # cat ff_pwr_btn - 0 enabled - # press the power button for 3 times; - # cat ff_pwr_btn - 3 enabled - # echo disable > ff_pwr_btn - # cat ff_pwr_btn - 3 disabled - # press the power button for 3 times; - # cat ff_pwr_btn - 3 disabled - # echo enable > ff_pwr_btn - # cat ff_pwr_btn - 4 enabled - /* - * this is because the status bit is set even if the enable bit is cleared, - * and it triggers an ACPI fixed event when the enable bit is set again - */ - # press the power button for 3 times; - # cat ff_pwr_btn - 7 enabled - # echo disable > ff_pwr_btn - # press the power button for 3 times; - # echo clear > ff_pwr_btn /* clear the status bit */ - # echo disable > ff_pwr_btn - # cat ff_pwr_btn - 7 enabled - diff --git a/Documentation/ABI/testing/sysfs-firmware-dmi b/Documentation/ABI/testing/sysfs-firmware-dmi deleted file mode 100644 index c78f9ab01e5..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-dmi +++ /dev/null @@ -1,110 +0,0 @@ -What: /sys/firmware/dmi/ -Date: February 2011 -Contact: Mike Waychison <mikew@google.com> -Description: - Many machines' firmware (x86 and ia64) export DMI / - SMBIOS tables to the operating system. Getting at this - information is often valuable to userland, especially in - cases where there are OEM extensions used. - - The kernel itself does not rely on the majority of the - information in these tables being correct. It equally - cannot ensure that the data as exported to userland is - without error either. - - DMI is structured as a large table of entries, where - each entry has a common header indicating the type and - length of the entry, as well as a firmware-provided - 'handle' that is supposed to be unique amongst all - entries. - - Some entries are required by the specification, but many - others are optional. In general though, users should - never expect to find a specific entry type on their - system unless they know for certain what their firmware - is doing. Machine to machine experiences will vary. - - Multiple entries of the same type are allowed. In order - to handle these duplicate entry types, each entry is - assigned by the operating system an 'instance', which is - derived from an entry type's ordinal position. That is - to say, if there are 'N' multiple entries with the same type - 'T' in the DMI tables (adjacent or spread apart, it - doesn't matter), they will be represented in sysfs as - entries "T-0" through "T-(N-1)": - - Example entry directories: - - /sys/firmware/dmi/entries/17-0 - /sys/firmware/dmi/entries/17-1 - /sys/firmware/dmi/entries/17-2 - /sys/firmware/dmi/entries/17-3 - ... - - Instance numbers are used in lieu of the firmware - assigned entry handles as the kernel itself makes no - guarantees that handles as exported are unique, and - there are likely firmware images that get this wrong in - the wild. - - Each DMI entry in sysfs has the common header values - exported as attributes: - - handle : The 16bit 'handle' that is assigned to this - entry by the firmware. This handle may be - referred to by other entries. - length : The length of the entry, as presented in the - entry itself. Note that this is _not the - total count of bytes associated with the - entry_. This value represents the length of - the "formatted" portion of the entry. This - "formatted" region is sometimes followed by - the "unformatted" region composed of nul - terminated strings, with termination signalled - by a two nul characters in series. - raw : The raw bytes of the entry. This includes the - "formatted" portion of the entry, the - "unformatted" strings portion of the entry, - and the two terminating nul characters. - type : The type of the entry. This value is the same - as found in the directory name. It indicates - how the rest of the entry should be interpreted. - instance: The instance ordinal of the entry for the - given type. This value is the same as found - in the parent directory name. - position: The ordinal position (zero-based) of the entry - within the entirety of the DMI entry table. - - === Entry Specialization === - - Some entry types may have other information available in - sysfs. Not all types are specialized. - - --- Type 15 - System Event Log --- - - This entry allows the firmware to export a log of - events the system has taken. This information is - typically backed by nvram, but the implementation - details are abstracted by this table. This entry's data - is exported in the directory: - - /sys/firmware/dmi/entries/15-0/system_event_log - - and has the following attributes (documented in the - SMBIOS / DMI specification under "System Event Log (Type 15)": - - area_length - header_start_offset - data_start_offset - access_method - status - change_token - access_method_address - header_format - per_log_type_descriptor_length - type_descriptors_supported_count - - As well, the kernel exports the binary attribute: - - raw_event_log : The raw binary bits of the event log - as described by the DMI entry. diff --git a/Documentation/ABI/testing/sysfs-firmware-gsmi b/Documentation/ABI/testing/sysfs-firmware-gsmi deleted file mode 100644 index 0faa0aaf4b6..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-gsmi +++ /dev/null @@ -1,58 +0,0 @@ -What: /sys/firmware/gsmi -Date: March 2011 -Contact: Mike Waychison <mikew@google.com> -Description: - Some servers used internally at Google have firmware - that provides callback functionality via explicit SMI - triggers. Some of the callbacks are similar to those - provided by the EFI runtime services page, but due to - historical reasons this different entry-point has been - used. - - The gsmi driver implements the kernel's abstraction for - these firmware callbacks. Currently, this functionality - is limited to handling the system event log and getting - access to EFI-style variables stored in nvram. - - Layout: - - /sys/firmware/gsmi/vars: - - This directory has the same layout (and - underlying implementation as /sys/firmware/efi/vars. - See Documentation/ABI/*/sysfs-firmware-efi-vars - for more information on how to interact with - this structure. - - /sys/firmware/gsmi/append_to_eventlog - write-only: - - This file takes a binary blob and passes it onto - the firmware to be timestamped and appended to - the system eventlog. The binary format is - interpreted by the firmware and may change from - platform to platform. The only kernel-enforced - requirement is that the blob be prefixed with a - 32bit host-endian type used as part of the - firmware call. - - /sys/firmware/gsmi/clear_config - write-only: - - Writing any value to this file will cause the - entire firmware configuration to be reset to - "factory defaults". Callers should assume that - a reboot is required for the configuration to be - cleared. - - /sys/firmware/gsmi/clear_eventlog - write-only: - - This file is used to clear out a portion/the - whole of the system event log. Values written - should be values between 1 and 100 inclusive (in - ASCII) representing the fraction of the log to - clear. Not all platforms support fractional - clearing though, and this writes to this file - will error out if the firmware doesn't like your - submitted fraction. - - Callers should assume that a reboot is needed - for this operation to complete. diff --git a/Documentation/ABI/testing/sysfs-firmware-log b/Documentation/ABI/testing/sysfs-firmware-log deleted file mode 100644 index 9b58e7c5365..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-log +++ /dev/null @@ -1,7 +0,0 @@ -What: /sys/firmware/log -Date: February 2011 -Contact: Mike Waychison <mikew@google.com> -Description: - The /sys/firmware/log is a binary file that represents a - read-only copy of the firmware's log if one is - available. diff --git a/Documentation/ABI/testing/sysfs-firmware-memmap b/Documentation/ABI/testing/sysfs-firmware-memmap deleted file mode 100644 index eca0d65087d..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-memmap +++ /dev/null @@ -1,71 +0,0 @@ -What: /sys/firmware/memmap/ -Date: June 2008 -Contact: Bernhard Walle <bernhard.walle@gmx.de> -Description: - On all platforms, the firmware provides a memory map which the - kernel reads. The resources from that memory map are registered - in the kernel resource tree and exposed to userspace via - /proc/iomem (together with other resources). - - However, on most architectures that firmware-provided memory - map is modified afterwards by the kernel itself, either because - the kernel merges that memory map with other information or - just because the user overwrites that memory map via command - line. - - kexec needs the raw firmware-provided memory map to setup the - parameter segment of the kernel that should be booted with - kexec. Also, the raw memory map is useful for debugging. For - that reason, /sys/firmware/memmap is an interface that provides - the raw memory map to userspace. - - The structure is as follows: Under /sys/firmware/memmap there - are subdirectories with the number of the entry as their name: - - /sys/firmware/memmap/0 - /sys/firmware/memmap/1 - /sys/firmware/memmap/2 - /sys/firmware/memmap/3 - ... - - The maximum depends on the number of memory map entries provided - by the firmware. The order is just the order that the firmware - provides. - - Each directory contains three files: - - start : The start address (as hexadecimal number with the - '0x' prefix). - end : The end address, inclusive (regardless whether the - firmware provides inclusive or exclusive ranges). - type : Type of the entry as string. See below for a list of - valid types. - - So, for example: - - /sys/firmware/memmap/0/start - /sys/firmware/memmap/0/end - /sys/firmware/memmap/0/type - /sys/firmware/memmap/1/start - ... - - Currently following types exist: - - - System RAM - - ACPI Tables - - ACPI Non-volatile Storage - - reserved - - Following shell snippet can be used to display that memory - map in a human-readable format: - - -------------------- 8< ---------------------------------------- - #!/bin/bash - cd /sys/firmware/memmap - for dir in * ; do - start=$(cat $dir/start) - end=$(cat $dir/end) - type=$(cat $dir/type) - printf "%016x-%016x (%s)\n" $start $[ $end +1] "$type" - done - -------------------- >8 ---------------------------------------- diff --git a/Documentation/ABI/testing/sysfs-firmware-sfi b/Documentation/ABI/testing/sysfs-firmware-sfi deleted file mode 100644 index 4be7d44aeac..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-sfi +++ /dev/null @@ -1,15 +0,0 @@ -What: /sys/firmware/sfi/tables/ -Date: May 2010 -Contact: Len Brown <lenb@kernel.org> -Description: - SFI defines a number of small static memory tables - so the kernel can get platform information from firmware. - - The tables are defined in the latest SFI specification: - http://simplefirmware.org/documentation - - While the tables are used by the kernel, user-space - can observe them this way: - - # cd /sys/firmware/sfi/tables - # cat $TABLENAME > $TABLENAME.bin diff --git a/Documentation/ABI/testing/sysfs-firmware-sgi_uv b/Documentation/ABI/testing/sysfs-firmware-sgi_uv deleted file mode 100644 index 4573fd4b787..00000000000 --- a/Documentation/ABI/testing/sysfs-firmware-sgi_uv +++ /dev/null @@ -1,27 +0,0 @@ -What: /sys/firmware/sgi_uv/ -Date: August 2008 -Contact: Russ Anderson <rja@sgi.com> -Description: - The /sys/firmware/sgi_uv directory contains information - about the SGI UV platform. - - Under that directory are a number of files: - - partition_id - coherence_id - - The partition_id entry contains the partition id. - SGI UV systems can be partitioned into multiple physical - machines, which each partition running a unique copy - of the operating system. Each partition will have a unique - partition id. To display the partition id, use the command: - - cat /sys/firmware/sgi_uv/partition_id - - The coherence_id entry contains the coherence id. - A partitioned SGI UV system can have one or more coherence - domain. The coherence id indicates which coherence domain - this partition is in. To display the coherence id, use the - command: - - cat /sys/firmware/sgi_uv/coherence_id diff --git a/Documentation/ABI/testing/sysfs-fs-ext4 b/Documentation/ABI/testing/sysfs-fs-ext4 deleted file mode 100644 index f22ac0872ae..00000000000 --- a/Documentation/ABI/testing/sysfs-fs-ext4 +++ /dev/null @@ -1,98 +0,0 @@ -What: /sys/fs/ext4/<disk>/mb_stats -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - Controls whether the multiblock allocator should - collect statistics, which are shown during the unmount. - 1 means to collect statistics, 0 means not to collect - statistics - -What: /sys/fs/ext4/<disk>/mb_group_prealloc -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - The multiblock allocator will round up allocation - requests to a multiple of this tuning parameter if the - stripe size is not set in the ext4 superblock - -What: /sys/fs/ext4/<disk>/mb_max_to_scan -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - The maximum number of extents the multiblock allocator - will search to find the best extent - -What: /sys/fs/ext4/<disk>/mb_min_to_scan -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - The minimum number of extents the multiblock allocator - will search to find the best extent - -What: /sys/fs/ext4/<disk>/mb_order2_req -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - Tuning parameter which controls the minimum size for - requests (as a power of 2) where the buddy cache is - used - -What: /sys/fs/ext4/<disk>/mb_stream_req -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - Files which have fewer blocks than this tunable - parameter will have their blocks allocated out of a - block group specific preallocation pool, so that small - files are packed closely together. Each large file - will have its blocks allocated out of its own unique - preallocation pool. - -What: /sys/fs/ext4/<disk>/inode_readahead_blks -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - Tuning parameter which controls the maximum number of - inode table blocks that ext4's inode table readahead - algorithm will pre-read into the buffer cache - -What: /sys/fs/ext4/<disk>/delayed_allocation_blocks -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - This file is read-only and shows the number of blocks - that are dirty in the page cache, but which do not - have their location in the filesystem allocated yet. - -What: /sys/fs/ext4/<disk>/lifetime_write_kbytes -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - This file is read-only and shows the number of kilobytes - of data that have been written to this filesystem since it was - created. - -What: /sys/fs/ext4/<disk>/session_write_kbytes -Date: March 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - This file is read-only and shows the number of - kilobytes of data that have been written to this - filesystem since it was mounted. - -What: /sys/fs/ext4/<disk>/inode_goal -Date: June 2008 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - Tuning parameter which (if non-zero) controls the goal - inode used by the inode allocator in preference to - all other allocation heuristics. This is intended for - debugging use only, and should be 0 on production - systems. - -What: /sys/fs/ext4/<disk>/max_writeback_mb_bump -Date: September 2009 -Contact: "Theodore Ts'o" <tytso@mit.edu> -Description: - The maximum number of megabytes the writeback code will - try to write out before move on to another inode. diff --git a/Documentation/ABI/testing/sysfs-gpio b/Documentation/ABI/testing/sysfs-gpio deleted file mode 100644 index 80f4c94c7be..00000000000 --- a/Documentation/ABI/testing/sysfs-gpio +++ /dev/null @@ -1,27 +0,0 @@ -What: /sys/class/gpio/ -Date: July 2008 -KernelVersion: 2.6.27 -Contact: David Brownell <dbrownell@users.sourceforge.net> -Description: - - As a Kconfig option, individual GPIO signals may be accessed from - userspace. GPIOs are only made available to userspace by an explicit - "export" operation. If a given GPIO is not claimed for use by - kernel code, it may be exported by userspace (and unexported later). - Kernel code may export it for complete or partial access. - - GPIOs are identified as they are inside the kernel, using integers in - the range 0..INT_MAX. See Documentation/gpio.txt for more information. - - /sys/class/gpio - /export ... asks the kernel to export a GPIO to userspace - /unexport ... to return a GPIO to the kernel - /gpioN ... for each exported GPIO #N - /value ... always readable, writes fail for input GPIOs - /direction ... r/w as: in, out (default low); write: high, low - /edge ... r/w as: none, falling, rising, both - /gpiochipN ... for each gpiochip; #N is its first GPIO - /base ... (r/o) same as N - /label ... (r/o) descriptive, not necessarily unique - /ngpio ... (r/o) number of GPIOs; numbered N to N + (ngpio - 1) - diff --git a/Documentation/ABI/testing/sysfs-i2c-bmp085 b/Documentation/ABI/testing/sysfs-i2c-bmp085 deleted file mode 100644 index 585962ad046..00000000000 --- a/Documentation/ABI/testing/sysfs-i2c-bmp085 +++ /dev/null @@ -1,31 +0,0 @@ -What: /sys/bus/i2c/devices/<busnum>-<devaddr>/pressure0_input -Date: June 2010 -Contact: Christoph Mair <christoph.mair@gmail.com> -Description: Start a pressure measurement and read the result. Values - represent the ambient air pressure in pascal (0.01 millibar). - - Reading: returns the current air pressure. - - -What: /sys/bus/i2c/devices/<busnum>-<devaddr>/temp0_input -Date: June 2010 -Contact: Christoph Mair <christoph.mair@gmail.com> -Description: Measure the ambient temperature. The returned value represents - the ambient temperature in units of 0.1 degree celsius. - - Reading: returns the current temperature. - - -What: /sys/bus/i2c/devices/<busnum>-<devaddr>/oversampling -Date: June 2010 -Contact: Christoph Mair <christoph.mair@gmail.com> -Description: Tell the bmp085 to use more samples to calculate a pressure - value. When writing to this file the chip will use 2^x samples - to calculate the next pressure value with x being the value - written. Using this feature will decrease RMS noise and - increase the measurement time. - - Reading: returns the current oversampling setting. - - Writing: sets a new oversampling setting. - Accepted values: 0..3. diff --git a/Documentation/ABI/testing/sysfs-ibft b/Documentation/ABI/testing/sysfs-ibft deleted file mode 100644 index c2b7d1154be..00000000000 --- a/Documentation/ABI/testing/sysfs-ibft +++ /dev/null @@ -1,23 +0,0 @@ -What: /sys/firmware/ibft/initiator -Date: November 2007 -Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> -Description: The /sys/firmware/ibft/initiator directory will contain - files that expose the iSCSI Boot Firmware Table initiator data. - Usually this contains the Initiator name. - -What: /sys/firmware/ibft/targetX -Date: November 2007 -Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> -Description: The /sys/firmware/ibft/targetX directory will contain - files that expose the iSCSI Boot Firmware Table target data. - Usually this contains the target's IP address, boot LUN, - target name, and what NIC it is associated with. It can also - contain the CHAP name (and password), the reverse CHAP - name (and password) - -What: /sys/firmware/ibft/ethernetX -Date: November 2007 -Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> -Description: The /sys/firmware/ibft/ethernetX directory will contain - files that expose the iSCSI Boot Firmware Table NIC data. - This can this can the IP address, MAC, and gateway of the NIC. diff --git a/Documentation/ABI/testing/sysfs-kernel-fscaps b/Documentation/ABI/testing/sysfs-kernel-fscaps deleted file mode 100644 index 50a3033b5e1..00000000000 --- a/Documentation/ABI/testing/sysfs-kernel-fscaps +++ /dev/null @@ -1,8 +0,0 @@ -What: /sys/kernel/fscaps -Date: February 2011 -KernelVersion: 2.6.38 -Contact: Ludwig Nussel <ludwig.nussel@suse.de> -Description - Shows whether file system capabilities are honored - when executing a binary - diff --git a/Documentation/ABI/testing/sysfs-kernel-mm b/Documentation/ABI/testing/sysfs-kernel-mm deleted file mode 100644 index 190d523ac15..00000000000 --- a/Documentation/ABI/testing/sysfs-kernel-mm +++ /dev/null @@ -1,6 +0,0 @@ -What: /sys/kernel/mm -Date: July 2008 -Contact: Nishanth Aravamudan <nacc@us.ibm.com>, VM maintainers -Description: - /sys/kernel/mm/ should contain any and all VM - related information in /sys/kernel/. diff --git a/Documentation/ABI/testing/sysfs-kernel-mm-hugepages b/Documentation/ABI/testing/sysfs-kernel-mm-hugepages deleted file mode 100644 index e21c00571cf..00000000000 --- a/Documentation/ABI/testing/sysfs-kernel-mm-hugepages +++ /dev/null @@ -1,15 +0,0 @@ -What: /sys/kernel/mm/hugepages/ -Date: June 2008 -Contact: Nishanth Aravamudan <nacc@us.ibm.com>, hugetlb maintainers -Description: - /sys/kernel/mm/hugepages/ contains a number of subdirectories - of the form hugepages-<size>kB, where <size> is the page size - of the hugepages supported by the kernel/CPU combination. - - Under these directories are a number of files: - nr_hugepages - nr_overcommit_hugepages - free_hugepages - surplus_hugepages - resv_hugepages - See Documentation/vm/hugetlbpage.txt for details. diff --git a/Documentation/ABI/testing/sysfs-kernel-slab b/Documentation/ABI/testing/sysfs-kernel-slab deleted file mode 100644 index 91bd6ca5440..00000000000 --- a/Documentation/ABI/testing/sysfs-kernel-slab +++ /dev/null @@ -1,490 +0,0 @@ -What: /sys/kernel/slab -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The /sys/kernel/slab directory contains a snapshot of the - internal state of the SLUB allocator for each cache. Certain - files may be modified to change the behavior of the cache (and - any cache it aliases, if any). -Users: kernel memory tuning tools - -What: /sys/kernel/slab/cache/aliases -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The aliases file is read-only and specifies how many caches - have merged into this cache. - -What: /sys/kernel/slab/cache/align -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The align file is read-only and specifies the cache's object - alignment in bytes. - -What: /sys/kernel/slab/cache/alloc_calls -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_calls file is read-only and lists the kernel code - locations from which allocations for this cache were performed. - The alloc_calls file only contains information if debugging is - enabled for that cache (see Documentation/vm/slub.txt). - -What: /sys/kernel/slab/cache/alloc_fastpath -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_fastpath file shows how many objects have been - allocated using the fast path. It can be written to clear the - current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/alloc_from_partial -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_from_partial file shows how many times a cpu slab has - been full and it has been refilled by using a slab from the list - of partially used slabs. It can be written to clear the current - count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/alloc_refill -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_refill file shows how many times the per-cpu freelist - was empty but there were objects available as the result of - remote cpu frees. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/alloc_slab -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_slab file is shows how many times a new slab had to - be allocated from the page allocator. It can be written to - clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/alloc_slowpath -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The alloc_slowpath file shows how many objects have been - allocated using the slow path because of a refill or - allocation from a partial or new slab. It can be written to - clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/cache_dma -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The cache_dma file is read-only and specifies whether objects - are from ZONE_DMA. - Available when CONFIG_ZONE_DMA is enabled. - -What: /sys/kernel/slab/cache/cpu_slabs -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The cpu_slabs file is read-only and displays how many cpu slabs - are active and their NUMA locality. - -What: /sys/kernel/slab/cache/cpuslab_flush -Date: April 2009 -KernelVersion: 2.6.31 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The file cpuslab_flush shows how many times a cache's cpu slabs - have been flushed as the result of destroying or shrinking a - cache, a cpu going offline, or as the result of forcing an - allocation from a certain node. It can be written to clear the - current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/ctor -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The ctor file is read-only and specifies the cache's object - constructor function, which is invoked for each object when a - new slab is allocated. - -What: /sys/kernel/slab/cache/deactivate_empty -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The deactivate_empty file shows how many times an empty cpu slab - was deactivated. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/deactivate_full -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The deactivate_full file shows how many times a full cpu slab - was deactivated. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/deactivate_remote_frees -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The deactivate_remote_frees file shows how many times a cpu slab - has been deactivated and contained free objects that were freed - remotely. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/deactivate_to_head -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The deactivate_to_head file shows how many times a partial cpu - slab was deactivated and added to the head of its node's partial - list. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/deactivate_to_tail -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The deactivate_to_tail file shows how many times a partial cpu - slab was deactivated and added to the tail of its node's partial - list. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/destroy_by_rcu -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The destroy_by_rcu file is read-only and specifies whether - slabs (not objects) are freed by rcu. - -What: /sys/kernel/slab/cache/free_add_partial -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_add_partial file shows how many times an object has - been freed in a full slab so that it had to added to its node's - partial list. It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/free_calls -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_calls file is read-only and lists the locations of - object frees if slab debugging is enabled (see - Documentation/vm/slub.txt). - -What: /sys/kernel/slab/cache/free_fastpath -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_fastpath file shows how many objects have been freed - using the fast path because it was an object from the cpu slab. - It can be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/free_frozen -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_frozen file shows how many objects have been freed to - a frozen slab (i.e. a remote cpu slab). It can be written to - clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/free_remove_partial -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_remove_partial file shows how many times an object has - been freed to a now-empty slab so that it had to be removed from - its node's partial list. It can be written to clear the current - count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/free_slab -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_slab file shows how many times an empty slab has been - freed back to the page allocator. It can be written to clear - the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/free_slowpath -Date: February 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The free_slowpath file shows how many objects have been freed - using the slow path (i.e. to a full or partial slab). It can - be written to clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/hwcache_align -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The hwcache_align file is read-only and specifies whether - objects are aligned on cachelines. - -What: /sys/kernel/slab/cache/min_partial -Date: February 2009 -KernelVersion: 2.6.30 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - David Rientjes <rientjes@google.com> -Description: - The min_partial file specifies how many empty slabs shall - remain on a node's partial list to avoid the overhead of - allocating new slabs. Such slabs may be reclaimed by utilizing - the shrink file. - -What: /sys/kernel/slab/cache/object_size -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The object_size file is read-only and specifies the cache's - object size. - -What: /sys/kernel/slab/cache/objects -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The objects file is read-only and displays how many objects are - active and from which nodes they are from. - -What: /sys/kernel/slab/cache/objects_partial -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The objects_partial file is read-only and displays how many - objects are on partial slabs and from which nodes they are - from. - -What: /sys/kernel/slab/cache/objs_per_slab -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The file objs_per_slab is read-only and specifies how many - objects may be allocated from a single slab of the order - specified in /sys/kernel/slab/cache/order. - -What: /sys/kernel/slab/cache/order -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The order file specifies the page order at which new slabs are - allocated. It is writable and can be changed to increase the - number of objects per slab. If a slab cannot be allocated - because of fragmentation, SLUB will retry with the minimum order - possible depending on its characteristics. - When debug_guardpage_minorder=N (N > 0) parameter is specified - (see Documentation/kernel-parameters.txt), the minimum possible - order is used and this sysfs entry can not be used to change - the order at run time. - -What: /sys/kernel/slab/cache/order_fallback -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The order_fallback file shows how many times an allocation of a - new slab has not been possible at the cache's order and instead - fallen back to its minimum possible order. It can be written to - clear the current count. - Available when CONFIG_SLUB_STATS is enabled. - -What: /sys/kernel/slab/cache/partial -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The partial file is read-only and displays how long many - partial slabs there are and how long each node's list is. - -What: /sys/kernel/slab/cache/poison -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The poison file specifies whether objects should be poisoned - when a new slab is allocated. - -What: /sys/kernel/slab/cache/reclaim_account -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The reclaim_account file specifies whether the cache's objects - are reclaimable (and grouped by their mobility). - -What: /sys/kernel/slab/cache/red_zone -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The red_zone file specifies whether the cache's objects are red - zoned. - -What: /sys/kernel/slab/cache/remote_node_defrag_ratio -Date: January 2008 -KernelVersion: 2.6.25 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The file remote_node_defrag_ratio specifies the percentage of - times SLUB will attempt to refill the cpu slab with a partial - slab from a remote node as opposed to allocating a new slab on - the local node. This reduces the amount of wasted memory over - the entire system but can be expensive. - Available when CONFIG_NUMA is enabled. - -What: /sys/kernel/slab/cache/sanity_checks -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The sanity_checks file specifies whether expensive checks - should be performed on free and, at minimum, enables double free - checks. Caches that enable sanity_checks cannot be merged with - caches that do not. - -What: /sys/kernel/slab/cache/shrink -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The shrink file is written when memory should be reclaimed from - a cache. Empty partial slabs are freed and the partial list is - sorted so the slabs with the fewest available objects are used - first. - -What: /sys/kernel/slab/cache/slab_size -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The slab_size file is read-only and specifies the object size - with metadata (debugging information and alignment) in bytes. - -What: /sys/kernel/slab/cache/slabs -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The slabs file is read-only and displays how long many slabs - there are (both cpu and partial) and from which nodes they are - from. - -What: /sys/kernel/slab/cache/store_user -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The store_user file specifies whether the location of - allocation or free should be tracked for a cache. - -What: /sys/kernel/slab/cache/total_objects -Date: April 2008 -KernelVersion: 2.6.26 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The total_objects file is read-only and displays how many total - objects a cache has and from which nodes they are from. - -What: /sys/kernel/slab/cache/trace -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - The trace file specifies whether object allocations and frees - should be traced. - -What: /sys/kernel/slab/cache/validate -Date: May 2007 -KernelVersion: 2.6.22 -Contact: Pekka Enberg <penberg@cs.helsinki.fi>, - Christoph Lameter <cl@linux-foundation.org> -Description: - Writing to the validate file causes SLUB to traverse all of its - cache's objects and check the validity of metadata. diff --git a/Documentation/ABI/testing/sysfs-kernel-uids b/Documentation/ABI/testing/sysfs-kernel-uids deleted file mode 100644 index 28f14695a85..00000000000 --- a/Documentation/ABI/testing/sysfs-kernel-uids +++ /dev/null @@ -1,14 +0,0 @@ -What: /sys/kernel/uids/<uid>/cpu_shares -Date: December 2007 -Contact: Dhaval Giani <dhaval@linux.vnet.ibm.com> - Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> -Description: - The /sys/kernel/uids/<uid>/cpu_shares tunable is used - to set the cpu bandwidth a user is allowed. This is a - propotional value. What that means is that if there - are two users logged in, each with an equal number of - shares, then they will get equal CPU bandwidth. Another - example would be, if User A has shares = 1024 and user - B has shares = 2048, User B will get twice the CPU - bandwidth user A will. For more details refer - Documentation/scheduler/sched-design-CFS.txt diff --git a/Documentation/ABI/testing/sysfs-memory-page-offline b/Documentation/ABI/testing/sysfs-memory-page-offline deleted file mode 100644 index e14703f12fd..00000000000 --- a/Documentation/ABI/testing/sysfs-memory-page-offline +++ /dev/null @@ -1,44 +0,0 @@ -What: /sys/devices/system/memory/soft_offline_page -Date: Sep 2009 -KernelVersion: 2.6.33 -Contact: andi@firstfloor.org -Description: - Soft-offline the memory page containing the physical address - written into this file. Input is a hex number specifying the - physical address of the page. The kernel will then attempt - to soft-offline it, by moving the contents elsewhere or - dropping it if possible. The kernel will then be placed - on the bad page list and never be reused. - - The offlining is done in kernel specific granuality. - Normally it's the base page size of the kernel, but - this might change. - - The page must be still accessible, not poisoned. The - kernel will never kill anything for this, but rather - fail the offline. Return value is the size of the - number, or a error when the offlining failed. Reading - the file is not allowed. - -What: /sys/devices/system/memory/hard_offline_page -Date: Sep 2009 -KernelVersion: 2.6.33 -Contact: andi@firstfloor.org -Description: - Hard-offline the memory page containing the physical - address written into this file. Input is a hex number - specifying the physical address of the page. The - kernel will then attempt to hard-offline the page, by - trying to drop the page or killing any owner or - triggering IO errors if needed. Note this may kill - any processes owning the page. The kernel will avoid - to access this page assuming it's poisoned by the - hardware. - - The offlining is done in kernel specific granuality. - Normally it's the base page size of the kernel, but - this might change. - - Return value is the size of the number, or a error when - the offlining failed. - Reading the file is not allowed. diff --git a/Documentation/ABI/testing/sysfs-module b/Documentation/ABI/testing/sysfs-module deleted file mode 100644 index 47064c2b1f7..00000000000 --- a/Documentation/ABI/testing/sysfs-module +++ /dev/null @@ -1,51 +0,0 @@ -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. - - -What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max -Date: July 2011 -KernelVersion: 3.1 -Contact: Kirill Smelkov <kirr@mns.spb.ru> -Description: Maximum time allowed for periodic transfers per microframe (μs) - - [ USB 2.0 sets maximum allowed time for periodic transfers per - microframe to be 80%, that is 100 microseconds out of 125 - microseconds (full microframe). - - However there are cases, when 80% max isochronous bandwidth is - too limiting. For example two video streams could require 110 - microseconds of isochronous bandwidth per microframe to work - together. ] - - Through this setting it is possible to raise the limit so that - the host controller would allow allocating more than 100 - microseconds of periodic bandwidth per microframe. - - Beware, non-standard modes are usually not thoroughly tested by - hardware designers, and the hardware can malfunction when this - setting differ from default 100. - -What: /sys/module/*/{coresize,initsize} -Date: Jan 2012 -KernelVersion:»·3.3 -Contact: Kay Sievers <kay.sievers@vrfy.org> -Description: Module size in bytes. - -What: /sys/module/*/taint -Date: Jan 2012 -KernelVersion:»·3.3 -Contact: Kay Sievers <kay.sievers@vrfy.org> -Description: Module taint flags: - P - proprietary module - O - out-of-tree module - F - force-loaded module - C - staging driver module diff --git a/Documentation/ABI/testing/sysfs-ocfs2 b/Documentation/ABI/testing/sysfs-ocfs2 deleted file mode 100644 index b7cc516a8a8..00000000000 --- a/Documentation/ABI/testing/sysfs-ocfs2 +++ /dev/null @@ -1,89 +0,0 @@ -What: /sys/fs/ocfs2/ -Date: April 2008 -Contact: ocfs2-devel@oss.oracle.com -Description: - The /sys/fs/ocfs2 directory contains knobs used by the - ocfs2-tools to interact with the filesystem. - -What: /sys/fs/ocfs2/max_locking_protocol -Date: April 2008 -Contact: ocfs2-devel@oss.oracle.com -Description: - The /sys/fs/ocfs2/max_locking_protocol file displays version - of ocfs2 locking supported by the filesystem. This version - covers how ocfs2 uses distributed locking between cluster - nodes. - - The protocol version has a major and minor number. Two - cluster nodes can interoperate if they have an identical - major number and an overlapping minor number - thus, - a node with version 1.10 can interoperate with a node - sporting version 1.8, as long as both use the 1.8 protocol. - - Reading from this file returns a single line, the major - number and minor number joined by a period, eg "1.10". - - This file is read-only. The value is compiled into the - driver. - -What: /sys/fs/ocfs2/loaded_cluster_plugins -Date: April 2008 -Contact: ocfs2-devel@oss.oracle.com -Description: - The /sys/fs/ocfs2/loaded_cluster_plugins file describes - the available plugins to support ocfs2 cluster operation. - A cluster plugin is required to use ocfs2 in a cluster. - There are currently two available plugins: - - * 'o2cb' - The classic o2cb cluster stack that ocfs2 has - used since its inception. - * 'user' - A plugin supporting userspace cluster software - in conjunction with fs/dlm. - - Reading from this file returns the names of all loaded - plugins, one per line. - - This file is read-only. Its contents may change as - plugins are loaded or removed. - -What: /sys/fs/ocfs2/active_cluster_plugin -Date: April 2008 -Contact: ocfs2-devel@oss.oracle.com -Description: - The /sys/fs/ocfs2/active_cluster_plugin displays which - cluster plugin is currently in use by the filesystem. - The active plugin will appear in the loaded_cluster_plugins - file as well. Only one plugin can be used at a time. - - Reading from this file returns the name of the active plugin - on a single line. - - This file is read-only. Which plugin is active depends on - the cluster stack in use. The contents may change - when all filesystems are unmounted and the cluster stack - is changed. - -What: /sys/fs/ocfs2/cluster_stack -Date: April 2008 -Contact: ocfs2-devel@oss.oracle.com -Description: - The /sys/fs/ocfs2/cluster_stack file contains the name - of current ocfs2 cluster stack. This value is set by - userspace tools when bringing the cluster stack online. - - Cluster stack names are 4 characters in length. - - When the 'o2cb' cluster stack is used, the 'o2cb' cluster - plugin is active. All other cluster stacks use the 'user' - cluster plugin. - - Reading from this file returns the name of the current - cluster stack on a single line. - - Writing a new stack name to this file changes the current - cluster stack unless there are mounted ocfs2 filesystems. - If there are mounted filesystems, attempts to change the - stack return an error. - -Users: - ocfs2-tools <ocfs2-tools-devel@oss.oracle.com> diff --git a/Documentation/ABI/testing/sysfs-platform-asus-laptop b/Documentation/ABI/testing/sysfs-platform-asus-laptop deleted file mode 100644 index cd9d667c3da..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-asus-laptop +++ /dev/null @@ -1,66 +0,0 @@ -What: /sys/devices/platform/asus_laptop/display -Date: January 2007 -KernelVersion: 2.6.20 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - This file allows display switching. The value - is composed by 4 bits and defined as follow: - 4321 - |||`- LCD - ||`-- CRT - |`--- TV - `---- DVI - Ex: - 0 (0000b) means no display - - 3 (0011b) CRT+LCD. - -What: /sys/devices/platform/asus_laptop/gps -Date: January 2007 -KernelVersion: 2.6.20 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the gps device. 1 means on, 0 means off. -Users: Lapsus - -What: /sys/devices/platform/asus_laptop/ledd -Date: January 2007 -KernelVersion: 2.6.20 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Some models like the W1N have a LED display that can be - used to display several items of information. - To control the LED display, use the following : - echo 0x0T000DDD > /sys/devices/platform/asus_laptop/ - where T control the 3 letters display, and DDD the 3 digits display. - The DDD table can be found in Documentation/laptops/asus-laptop.txt - -What: /sys/devices/platform/asus_laptop/bluetooth -Date: January 2007 -KernelVersion: 2.6.20 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the bluetooth device. 1 means on, 0 means off. - This may control the led, the device or both. -Users: Lapsus - -What: /sys/devices/platform/asus_laptop/wlan -Date: January 2007 -KernelVersion: 2.6.20 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the wlan device. 1 means on, 0 means off. - This may control the led, the device or both. -Users: Lapsus - -What: /sys/devices/platform/asus_laptop/wimax -Date: October 2010 -KernelVersion: 2.6.37 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the wimax device. 1 means on, 0 means off. - -What: /sys/devices/platform/asus_laptop/wwan -Date: October 2010 -KernelVersion: 2.6.37 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the wwan (3G) device. 1 means on, 0 means off. diff --git a/Documentation/ABI/testing/sysfs-platform-asus-wmi b/Documentation/ABI/testing/sysfs-platform-asus-wmi deleted file mode 100644 index 2e7df91620d..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-asus-wmi +++ /dev/null @@ -1,31 +0,0 @@ -What: /sys/devices/platform/<platform>/cpufv -Date: Oct 2010 -KernelVersion: 2.6.37 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Change CPU clock configuration (write-only). - There are three available clock configuration: - * 0 -> Super Performance Mode - * 1 -> High Performance Mode - * 2 -> Power Saving Mode - -What: /sys/devices/platform/<platform>/camera -Date: Jan 2010 -KernelVersion: 2.6.39 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the camera. 1 means on, 0 means off. - -What: /sys/devices/platform/<platform>/cardr -Date: Jan 2010 -KernelVersion: 2.6.39 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the card reader. 1 means on, 0 means off. - -What: /sys/devices/platform/<platform>/touchpad -Date: Jan 2010 -KernelVersion: 2.6.39 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the card touchpad. 1 means on, 0 means off. diff --git a/Documentation/ABI/testing/sysfs-platform-at91 b/Documentation/ABI/testing/sysfs-platform-at91 deleted file mode 100644 index 4cc6a865ae6..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-at91 +++ /dev/null @@ -1,25 +0,0 @@ -What: /sys/devices/platform/at91_can/net/<iface>/mb0_id -Date: January 2011 -KernelVersion: 2.6.38 -Contact: Marc Kleine-Budde <kernel@pengutronix.de> -Description: - Value representing the can_id of mailbox 0. - - Default: 0x7ff (standard frame) - - Due to a chip bug (errata 50.2.6.3 & 50.3.5.3 in - "AT91SAM9263 Preliminary 6249H-ATARM-27-Jul-09") the - contents of mailbox 0 may be send under certain - conditions (even if disabled or in rx mode). - - The workaround in the errata suggests not to use the - mailbox and load it with an unused identifier. - - In order to use an extended can_id add the - CAN_EFF_FLAG (0x80000000U) to the can_id. Example: - - - standard id 0x7ff: - echo 0x7ff > /sys/class/net/can0/mb0_id - - - extended id 0x1fffffff: - echo 0x9fffffff > /sys/class/net/can0/mb0_id diff --git a/Documentation/ABI/testing/sysfs-platform-eeepc-laptop b/Documentation/ABI/testing/sysfs-platform-eeepc-laptop deleted file mode 100644 index 5b026c69587..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-eeepc-laptop +++ /dev/null @@ -1,50 +0,0 @@ -What: /sys/devices/platform/eeepc/disp -Date: May 2008 -KernelVersion: 2.6.26 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - This file allows display switching. - - 1 = LCD - - 2 = CRT - - 3 = LCD+CRT - If you run X11, you should use xrandr instead. - -What: /sys/devices/platform/eeepc/camera -Date: May 2008 -KernelVersion: 2.6.26 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the camera. 1 means on, 0 means off. - -What: /sys/devices/platform/eeepc/cardr -Date: May 2008 -KernelVersion: 2.6.26 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Control the card reader. 1 means on, 0 means off. - -What: /sys/devices/platform/eeepc/cpufv -Date: Jun 2009 -KernelVersion: 2.6.31 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - Change CPU clock configuration. - On the Eee PC 1000H there are three available clock configuration: - * 0 -> Super Performance Mode - * 1 -> High Performance Mode - * 2 -> Power Saving Mode - On Eee PC 701 there is only 2 available clock configurations. - Available configuration are listed in available_cpufv file. - Reading this file will show the raw hexadecimal value which - is defined as follow: - | 8 bit | 8 bit | - | `---- Current mode - `------------ Availables modes - For example, 0x301 means: mode 1 selected, 3 available modes. - -What: /sys/devices/platform/eeepc/available_cpufv -Date: Jun 2009 -KernelVersion: 2.6.31 -Contact: "Corentin Chary" <corentincj@iksaif.net> -Description: - List available cpufv modes. diff --git a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop deleted file mode 100644 index 814b01354c4..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop +++ /dev/null @@ -1,8 +0,0 @@ -What: /sys/devices/platform/ideapad/camera_power -Date: Dec 2010 -KernelVersion: 2.6.37 -Contact: "Ike Panhc <ike.pan@canonical.com>" -Description: - Control the power of camera module. 1 means on, 0 means off. - - diff --git a/Documentation/ABI/testing/sysfs-platform-kim b/Documentation/ABI/testing/sysfs-platform-kim deleted file mode 100644 index c1653271872..00000000000 --- a/Documentation/ABI/testing/sysfs-platform-kim +++ /dev/null @@ -1,48 +0,0 @@ -What: /sys/devices/platform/kim/dev_name -Date: January 2010 -KernelVersion: 2.6.38 -Contact: "Pavan Savoy" <pavan_savoy@ti.com> -Description: - Name of the UART device at which the WL128x chip - is connected. example: "/dev/ttyS0". - The device name flows down to architecture specific board - initialization file from the SFI/ATAGS bootloader - firmware. The name exposed is read from the user-space - dameon and opens the device when install is requested. - -What: /sys/devices/platform/kim/baud_rate -Date: January 2010 -KernelVersion: 2.6.38 -Contact: "Pavan Savoy" <pavan_savoy@ti.com> -Description: - The maximum reliable baud-rate the host can support. - Different platforms tend to have different high-speed - UART configurations, so the baud-rate needs to be set - locally and also sent across to the WL128x via a HCI-VS - command. The entry is read and made use by the user-space - daemon when the ldisc install is requested. - -What: /sys/devices/platform/kim/flow_cntrl -Date: January 2010 -KernelVersion: 2.6.38 -Contact: "Pavan Savoy" <pavan_savoy@ti.com> -Description: - The WL128x makes use of flow control mechanism, and this - entry most often should be 1, the host's UART is required - to have the capability of flow-control, or else this - entry can be made use of for exceptions. - -What: /sys/devices/platform/kim/install -Date: January 2010 -KernelVersion: 2.6.38 -Contact: "Pavan Savoy" <pavan_savoy@ti.com> -Description: - When one of the protocols Bluetooth, FM or GPS wants to make - use of the shared UART transport, it registers to the shared - transport driver, which will signal the user-space for opening, - configuring baud and install line discipline via this sysfs - entry. This entry would be polled upon by the user-space - daemon managing the UART, and is notified about the change - by the sysfs_notify. The value would be '1' when UART needs - to be opened/ldisc installed, and would be '0' when UART - is no more required and needs to be closed. diff --git a/Documentation/ABI/testing/sysfs-power b/Documentation/ABI/testing/sysfs-power deleted file mode 100644 index 31725ffeeb3..00000000000 --- a/Documentation/ABI/testing/sysfs-power +++ /dev/null @@ -1,233 +0,0 @@ -What: /sys/power/ -Date: August 2006 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power directory will contain files that will - provide a unified interface to the power management - subsystem. - -What: /sys/power/state -Date: August 2006 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/state file controls the system power state. - Reading from this file returns what states are supported, - which is hard-coded to 'standby' (Power-On Suspend), 'mem' - (Suspend-to-RAM), and 'disk' (Suspend-to-Disk). - - Writing to this file one of these strings causes the system to - transition into that state. Please see the file - Documentation/power/states.txt for a description of each of - these states. - -What: /sys/power/disk -Date: September 2006 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/disk file controls the operating mode of the - suspend-to-disk mechanism. Reading from this file returns - the name of the method by which the system will be put to - sleep on the next suspend. There are four methods supported: - 'firmware' - means that the memory image will be saved to disk - by some firmware, in which case we also assume that the - firmware will handle the system suspend. - 'platform' - the memory image will be saved by the kernel and - the system will be put to sleep by the platform driver (e.g. - ACPI or other PM registers). - 'shutdown' - the memory image will be saved by the kernel and - the system will be powered off. - 'reboot' - the memory image will be saved by the kernel and - the system will be rebooted. - - Additionally, /sys/power/disk can be used to turn on one of the - two testing modes of the suspend-to-disk mechanism: 'testproc' - or 'test'. If the suspend-to-disk mechanism is in the - 'testproc' mode, writing 'disk' to /sys/power/state will cause - the kernel to disable nonboot CPUs and freeze tasks, wait for 5 - seconds, unfreeze tasks and enable nonboot CPUs. If it is in - the 'test' mode, writing 'disk' to /sys/power/state will cause - the kernel to disable nonboot CPUs and freeze tasks, shrink - memory, suspend devices, wait for 5 seconds, resume devices, - unfreeze tasks and enable nonboot CPUs. Then, we are able to - look in the log messages and work out, for example, which code - is being slow and which device drivers are misbehaving. - - The suspend-to-disk method may be chosen by writing to this - file one of the accepted strings: - - 'firmware' - 'platform' - 'shutdown' - 'reboot' - 'testproc' - 'test' - - It will only change to 'firmware' or 'platform' if the system - supports that. - -What: /sys/power/image_size -Date: August 2006 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/image_size file controls the size of the image - created by the suspend-to-disk mechanism. It can be written a - string representing a non-negative integer that will be used - as an upper limit of the image size, in bytes. The kernel's - suspend-to-disk code will do its best to ensure the image size - will not exceed this number. However, if it turns out to be - impossible, the kernel will try to suspend anyway using the - smallest image possible. In particular, if "0" is written to - this file, the suspend image will be as small as possible. - - Reading from this file will display the current image size - limit, which is set to 500 MB by default. - -What: /sys/power/pm_trace -Date: August 2006 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/pm_trace file controls the code which saves the - last PM event point in the RTC across reboots, so that you can - debug a machine that just hangs during suspend (or more - commonly, during resume). Namely, the RTC is only used to save - the last PM event point if this file contains '1'. Initially - it contains '0' which may be changed to '1' by writing a - string representing a nonzero integer into it. - - To use this debugging feature you should attempt to suspend - the machine, then reboot it and run - - 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> -Description: - The /sys/power/pm_async file controls the switch allowing the - user space to enable or disable asynchronous suspend and resume - of devices. If enabled, this feature will cause some device - drivers' suspend and resume callbacks to be executed in parallel - with each other and with the main suspend thread. It is enabled - if this file contains "1", which is the default. It may be - disabled by writing "0" to this file, in which case all devices - will be suspended and resumed synchronously. - -What: /sys/power/wakeup_count -Date: July 2010 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/wakeup_count file allows user space to put the - system into a sleep state while taking into account the - concurrent arrival of wakeup events. Reading from it returns - the current number of registered wakeup events and it blocks if - some wakeup events are being processed at the time the file is - read from. Writing to it will only succeed if the current - number of wakeup events is equal to the written value and, if - successful, will make the kernel abort a subsequent transition - to a sleep state if any wakeup events are reported after the - write has returned. - -What: /sys/power/reserved_size -Date: May 2011 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/reserved_size file allows user space to control - the amount of memory reserved for allocations made by device - drivers during the "device freeze" stage of hibernation. It can - be written a string representing a non-negative integer that - will be used as the amount of memory to reserve for allocations - made by device drivers' "freeze" callbacks, in bytes. - - Reading from this file will display the current value, which is - set to 1 MB by default. - -What: /sys/power/autosleep -Date: April 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/autosleep file can be written one of the strings - returned by reads from /sys/power/state. If that happens, a - work item attempting to trigger a transition of the system to - the sleep state represented by that string is queued up. This - attempt will only succeed if there are no active wakeup sources - in the system at that time. After every execution, regardless - of whether or not the attempt to put the system to sleep has - succeeded, the work item requeues itself until user space - writes "off" to /sys/power/autosleep. - - Reading from this file causes the last string successfully - written to it to be returned. - -What: /sys/power/wake_lock -Date: February 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/wake_lock file allows user space to create - wakeup source objects and activate them on demand (if one of - those wakeup sources is active, reads from the - /sys/power/wakeup_count file block or return false). When a - string without white space is written to /sys/power/wake_lock, - it will be assumed to represent a wakeup source name. If there - is a wakeup source object with that name, it will be activated - (unless active already). Otherwise, a new wakeup source object - will be registered, assigned the given name and activated. - If a string written to /sys/power/wake_lock contains white - space, the part of the string preceding the white space will be - regarded as a wakeup source name and handled as descrived above. - The other part of the string will be regarded as a timeout (in - nanoseconds) such that the wakeup source will be automatically - deactivated after it has expired. The timeout, if present, is - set regardless of the current state of the wakeup source object - in question. - - Reads from this file return a string consisting of the names of - wakeup sources created with the help of it that are active at - the moment, separated with spaces. - - -What: /sys/power/wake_unlock -Date: February 2012 -Contact: Rafael J. Wysocki <rjw@sisk.pl> -Description: - The /sys/power/wake_unlock file allows user space to deactivate - wakeup sources created with the help of /sys/power/wake_lock. - When a string is written to /sys/power/wake_unlock, it will be - assumed to represent the name of a wakeup source to deactivate. - If a wakeup source object of that name exists and is active at - the moment, it will be deactivated. - - 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. diff --git a/Documentation/ABI/testing/sysfs-pps b/Documentation/ABI/testing/sysfs-pps deleted file mode 100644 index 25028c7bc37..00000000000 --- a/Documentation/ABI/testing/sysfs-pps +++ /dev/null @@ -1,73 +0,0 @@ -What: /sys/class/pps/ -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ directory will contain files and - directories that will provide a unified interface to - the PPS sources. - -What: /sys/class/pps/ppsX/ -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/ directory is related to X-th - PPS source into the system. Each directory will - contain files to manage and control its PPS source. - -What: /sys/class/pps/ppsX/assert -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/assert file reports the assert events - and the assert sequence number of the X-th source in the form: - - <secs>.<nsec>#<sequence> - - If the source has no assert events the content of this file - is empty. - -What: /sys/class/pps/ppsX/clear -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/clear file reports the clear events - and the clear sequence number of the X-th source in the form: - - <secs>.<nsec>#<sequence> - - If the source has no clear events the content of this file - is empty. - -What: /sys/class/pps/ppsX/mode -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/mode file reports the functioning - mode of the X-th source in hexadecimal encoding. - - Please, refer to linux/include/linux/pps.h for further - info. - -What: /sys/class/pps/ppsX/echo -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/echo file reports if the X-th does - or does not support an "echo" function. - -What: /sys/class/pps/ppsX/name -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/name file reports the name of the - X-th source. - -What: /sys/class/pps/ppsX/path -Date: February 2008 -Contact: Rodolfo Giometti <giometti@linux.it> -Description: - The /sys/class/pps/ppsX/path file reports the path name of - the device connected with the X-th source. - - If the source is not connected with any device the content - of this file is empty. diff --git a/Documentation/ABI/testing/sysfs-profiling b/Documentation/ABI/testing/sysfs-profiling deleted file mode 100644 index b02d8b8c173..00000000000 --- a/Documentation/ABI/testing/sysfs-profiling +++ /dev/null @@ -1,13 +0,0 @@ -What: /sys/kernel/profile -Date: September 2008 -Contact: Dave Hansen <dave@linux.vnet.ibm.com> -Description: - /sys/kernel/profile is the runtime equivalent - of the boot-time profile= option. - - You can get the same effect running: - - echo 2 > /sys/kernel/profile - - as you would by issuing profile=2 on the boot - command line. diff --git a/Documentation/ABI/testing/sysfs-ptp b/Documentation/ABI/testing/sysfs-ptp deleted file mode 100644 index d40d2b55050..00000000000 --- a/Documentation/ABI/testing/sysfs-ptp +++ /dev/null @@ -1,98 +0,0 @@ -What: /sys/class/ptp/ -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This directory contains files and directories - providing a standardized interface to the ancillary - features of PTP hardware clocks. - -What: /sys/class/ptp/ptpN/ -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This directory contains the attributes of the Nth PTP - hardware clock registered into the PTP class driver - subsystem. - -What: /sys/class/ptp/ptpN/clock_name -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file contains the name of the PTP hardware clock - as a human readable string. - -What: /sys/class/ptp/ptpN/max_adjustment -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file contains the PTP hardware clock's maximum - frequency adjustment value (a positive integer) in - parts per billion. - -What: /sys/class/ptp/ptpN/n_alarms -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file contains the number of periodic or one shot - alarms offer by the PTP hardware clock. - -What: /sys/class/ptp/ptpN/n_external_timestamps -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file contains the number of external timestamp - channels offered by the PTP hardware clock. - -What: /sys/class/ptp/ptpN/n_periodic_outputs -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file contains the number of programmable periodic - output channels offered by the PTP hardware clock. - -What: /sys/class/ptp/ptpN/pps_avaiable -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file indicates whether the PTP hardware clock - supports a Pulse Per Second to the host CPU. Reading - "1" means that the PPS is supported, while "0" means - not supported. - -What: /sys/class/ptp/ptpN/extts_enable -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This write-only file enables or disables external - timestamps. To enable external timestamps, write the - channel index followed by a "1" into the file. - To disable external timestamps, write the channel - index followed by a "0" into the file. - -What: /sys/class/ptp/ptpN/fifo -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This file provides timestamps on external events, in - the form of three integers: channel index, seconds, - and nanoseconds. - -What: /sys/class/ptp/ptpN/period -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This write-only file enables or disables periodic - outputs. To enable a periodic output, write five - integers into the file: channel index, start time - seconds, start time nanoseconds, period seconds, and - period nanoseconds. To disable a periodic output, set - all the seconds and nanoseconds values to zero. - -What: /sys/class/ptp/ptpN/pps_enable -Date: September 2010 -Contact: Richard Cochran <richardcochran@gmail.com> -Description: - This write-only file enables or disables delivery of - PPS events to the Linux PPS subsystem. To enable PPS - events, write a "1" into the file. To disable events, - write a "0" into the file. diff --git a/Documentation/ABI/testing/sysfs-tty b/Documentation/ABI/testing/sysfs-tty deleted file mode 100644 index b138b663bf5..00000000000 --- a/Documentation/ABI/testing/sysfs-tty +++ /dev/null @@ -1,19 +0,0 @@ -What: /sys/class/tty/console/active -Date: Nov 2010 -Contact: Kay Sievers <kay.sievers@vrfy.org> -Description: - Shows the list of currently configured - console devices, like 'tty1 ttyS0'. - The last entry in the file is the active - device connected to /dev/console. - The file supports poll() to detect virtual - console switches. - -What: /sys/class/tty/tty0/active -Date: Nov 2010 -Contact: Kay Sievers <kay.sievers@vrfy.org> -Description: - Shows the currently active virtual console - device, like 'tty1'. - The file supports poll() to detect virtual - console switches. diff --git a/Documentation/ABI/testing/sysfs-wusb_cbaf b/Documentation/ABI/testing/sysfs-wusb_cbaf deleted file mode 100644 index a99c5f86a37..00000000000 --- a/Documentation/ABI/testing/sysfs-wusb_cbaf +++ /dev/null @@ -1,100 +0,0 @@ -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_* -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - Various files for managing Cable Based Association of - (wireless) USB devices. - - The sequence of operations should be: - - 1. Device is plugged in. - - 2. The connection manager (CM) sees a device with CBA capability. - (the wusb_chid etc. files in /sys/devices/blah/OURDEVICE). - - 3. The CM writes the host name, supported band groups, - and the CHID (host ID) into the wusb_host_name, - wusb_host_band_groups and wusb_chid files. These - get sent to the device and the CDID (if any) for - this host is requested. - - 4. The CM can verify that the device's supported band - groups (wusb_device_band_groups) are compatible - with the host. - - 5. The CM reads the wusb_cdid file. - - 6. The CM looks it up its database. - - - If it has a matching CHID,CDID entry, the device - has been authorized before and nothing further - needs to be done. - - - If the CDID is zero (or the CM doesn't find a - matching CDID in its database), the device is - assumed to be not known. The CM may associate - the host with device by: writing a randomly - generated CDID to wusb_cdid and then a random CK - to wusb_ck (this uploads the new CC to the - device). - - CMD may choose to prompt the user before - associating with a new device. - - 7. Device is unplugged. - - References: - [WUSB-AM] Association Models Supplement to the - Certified Wireless Universal Serial Bus - Specification, version 1.0. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_chid -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The CHID of the host formatted as 16 space-separated - hex octets. - - Writes fetches device's supported band groups and the - the CDID for any existing association with this host. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_name -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - A friendly name for the host as a UTF-8 encoded string. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_host_band_groups -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The band groups supported by the host, in the format - defined in [WUSB-AM]. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_device_band_groups -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The band groups supported by the device, in the format - defined in [WUSB-AM]. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_cdid -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - The device's CDID formatted as 16 space-separated hex - octets. - -What: /sys/bus/usb/drivers/wusb_cbaf/.../wusb_ck -Date: August 2008 -KernelVersion: 2.6.27 -Contact: David Vrabel <david.vrabel@csr.com> -Description: - Write 16 space-separated random, hex octets to - associate with the device. |