diff options
Diffstat (limited to 'Documentation/ABI/stable')
| -rw-r--r-- | Documentation/ABI/stable/firewire-cdev | 103 | ||||
| -rw-r--r-- | Documentation/ABI/stable/o2cb | 10 | ||||
| -rw-r--r-- | Documentation/ABI/stable/syscalls | 10 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-acpi-pmprofile | 22 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-bus-firewire | 122 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-bus-xen-backend | 75 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-class-backlight | 56 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-class-rfkill | 67 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-class-ubi | 212 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-devices-node | 7 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-devices-system-xen_memory | 77 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-driver-qla2xxx | 8 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-driver-usb-usbtmc | 62 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-firmware-efi-vars | 75 | ||||
| -rw-r--r-- | Documentation/ABI/stable/sysfs-module | 30 | ||||
| -rw-r--r-- | Documentation/ABI/stable/thermal-notification | 4 | ||||
| -rw-r--r-- | Documentation/ABI/stable/vdso | 27 |
17 files changed, 0 insertions, 967 deletions
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 |