diff options
author | Anton Vorontsov <cbouatmailru@gmail.com> | 2012-01-04 00:09:35 -0500 |
---|---|---|
committer | Anton Vorontsov <cbouatmailru@gmail.com> | 2012-01-04 00:09:35 -0500 |
commit | 251f39fe42dae863bd24e30864e6b66076ba076d (patch) | |
tree | c804944bc17f3836d19cc8b5bc611dd1fb0ea915 /Documentation/ABI | |
parent | 9b8872273af6983b246252a6508fa7cf34c69d6e (diff) | |
parent | 35b4c01e29bdd9632dabf9784ed3486333f00427 (diff) |
Merge branch 'power-supply-scope' of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen
Diffstat (limited to 'Documentation/ABI')
-rw-r--r-- | Documentation/ABI/removed/o2cb | 2 | ||||
-rw-r--r-- | Documentation/ABI/removed/raw1394 | 2 | ||||
-rw-r--r-- | Documentation/ABI/stable/sysfs-acpi-pmprofile | 22 | ||||
-rw-r--r-- | Documentation/ABI/testing/debugfs-ideapad | 19 | ||||
-rw-r--r-- | Documentation/ABI/testing/evm | 23 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-block | 13 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-bcma | 8 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-pci-devices-cciss | 7 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd | 46 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-usb | 15 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 | 16 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-class-devfreq | 52 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-class-net-mesh | 8 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff | 7 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-driver-wacom | 72 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-platform-ideapad-laptop | 15 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-wacom | 10 |
17 files changed, 298 insertions, 39 deletions
diff --git a/Documentation/ABI/removed/o2cb b/Documentation/ABI/removed/o2cb index 7f5daa465093..20c91adca6d4 100644 --- a/Documentation/ABI/removed/o2cb +++ b/Documentation/ABI/removed/o2cb | |||
@@ -1,6 +1,6 @@ | |||
1 | What: /sys/o2cb symlink | 1 | What: /sys/o2cb symlink |
2 | Date: May 2011 | 2 | Date: May 2011 |
3 | KernelVersion: 2.6.40 | 3 | KernelVersion: 3.0 |
4 | Contact: ocfs2-devel@oss.oracle.com | 4 | Contact: ocfs2-devel@oss.oracle.com |
5 | Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is | 5 | Description: This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is |
6 | removed when new versions of ocfs2-tools which know to look | 6 | removed when new versions of ocfs2-tools which know to look |
diff --git a/Documentation/ABI/removed/raw1394 b/Documentation/ABI/removed/raw1394 index 490aa1efc4ae..ec333e676322 100644 --- a/Documentation/ABI/removed/raw1394 +++ b/Documentation/ABI/removed/raw1394 | |||
@@ -5,7 +5,7 @@ Description: | |||
5 | /dev/raw1394 was a character device file that allowed low-level | 5 | /dev/raw1394 was a character device file that allowed low-level |
6 | access to FireWire buses. Its major drawbacks were its inability | 6 | access to FireWire buses. Its major drawbacks were its inability |
7 | to implement sensible device security policies, and its low level | 7 | to implement sensible device security policies, and its low level |
8 | of abstraction that required userspace clients do duplicate much | 8 | of abstraction that required userspace clients to duplicate much |
9 | of the kernel's ieee1394 core functionality. | 9 | of the kernel's ieee1394 core functionality. |
10 | Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of | 10 | Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of |
11 | firewire-core. | 11 | firewire-core. |
diff --git a/Documentation/ABI/stable/sysfs-acpi-pmprofile b/Documentation/ABI/stable/sysfs-acpi-pmprofile new file mode 100644 index 000000000000..964c7a8afb26 --- /dev/null +++ b/Documentation/ABI/stable/sysfs-acpi-pmprofile | |||
@@ -0,0 +1,22 @@ | |||
1 | What: /sys/firmware/acpi/pm_profile | ||
2 | Date: 03-Nov-2011 | ||
3 | KernelVersion: v3.2 | ||
4 | Contact: linux-acpi@vger.kernel.org | ||
5 | Description: The ACPI pm_profile sysfs interface exports the platform | ||
6 | power management (and performance) requirement expectations | ||
7 | as provided by BIOS. The integer value is directly passed as | ||
8 | retrieved from the FADT ACPI table. | ||
9 | Values: For possible values see ACPI specification: | ||
10 | 5.2.9 Fixed ACPI Description Table (FADT) | ||
11 | Field: Preferred_PM_Profile | ||
12 | |||
13 | Currently these values are defined by spec: | ||
14 | 0 Unspecified | ||
15 | 1 Desktop | ||
16 | 2 Mobile | ||
17 | 3 Workstation | ||
18 | 4 Enterprise Server | ||
19 | 5 SOHO Server | ||
20 | 6 Appliance PC | ||
21 | 7 Performance Server | ||
22 | >7 Reserved | ||
diff --git a/Documentation/ABI/testing/debugfs-ideapad b/Documentation/ABI/testing/debugfs-ideapad new file mode 100644 index 000000000000..7079c0b21030 --- /dev/null +++ b/Documentation/ABI/testing/debugfs-ideapad | |||
@@ -0,0 +1,19 @@ | |||
1 | What: /sys/kernel/debug/ideapad/cfg | ||
2 | Date: Sep 2011 | ||
3 | KernelVersion: 3.2 | ||
4 | Contact: Ike Panhc <ike.pan@canonical.com> | ||
5 | Description: | ||
6 | |||
7 | cfg shows the return value of _CFG method in VPC2004 device. It tells machine | ||
8 | capability and what graphic component within the machine. | ||
9 | |||
10 | |||
11 | What: /sys/kernel/debug/ideapad/status | ||
12 | Date: Sep 2011 | ||
13 | KernelVersion: 3.2 | ||
14 | Contact: Ike Panhc <ike.pan@canonical.com> | ||
15 | Description: | ||
16 | |||
17 | status shows infos we can read and tells its meaning and value. | ||
18 | |||
19 | |||
diff --git a/Documentation/ABI/testing/evm b/Documentation/ABI/testing/evm new file mode 100644 index 000000000000..8374d4557e5d --- /dev/null +++ b/Documentation/ABI/testing/evm | |||
@@ -0,0 +1,23 @@ | |||
1 | What: security/evm | ||
2 | Date: March 2011 | ||
3 | Contact: Mimi Zohar <zohar@us.ibm.com> | ||
4 | Description: | ||
5 | EVM protects a file's security extended attributes(xattrs) | ||
6 | against integrity attacks. The initial method maintains an | ||
7 | HMAC-sha1 value across the extended attributes, storing the | ||
8 | value as the extended attribute 'security.evm'. | ||
9 | |||
10 | EVM depends on the Kernel Key Retention System to provide it | ||
11 | with a trusted/encrypted key for the HMAC-sha1 operation. | ||
12 | The key is loaded onto the root's keyring using keyctl. Until | ||
13 | EVM receives notification that the key has been successfully | ||
14 | loaded onto the keyring (echo 1 > <securityfs>/evm), EVM | ||
15 | can not create or validate the 'security.evm' xattr, but | ||
16 | returns INTEGRITY_UNKNOWN. Loading the key and signaling EVM | ||
17 | should be done as early as possible. Normally this is done | ||
18 | in the initramfs, which has already been measured as part | ||
19 | of the trusted boot. For more information on creating and | ||
20 | loading existing trusted/encrypted keys, refer to: | ||
21 | Documentation/keys-trusted-encrypted.txt. (A sample dracut | ||
22 | patch, which loads the trusted/encrypted key and enables | ||
23 | EVM, is available from http://linux-ima.sourceforge.net/#EVM.) | ||
diff --git a/Documentation/ABI/testing/sysfs-block b/Documentation/ABI/testing/sysfs-block index c1eb41cb9876..2b5d56127fce 100644 --- a/Documentation/ABI/testing/sysfs-block +++ b/Documentation/ABI/testing/sysfs-block | |||
@@ -206,3 +206,16 @@ Description: | |||
206 | when a discarded area is read the discard_zeroes_data | 206 | when a discarded area is read the discard_zeroes_data |
207 | parameter will be set to one. Otherwise it will be 0 and | 207 | parameter will be set to one. Otherwise it will be 0 and |
208 | the result of reading a discarded area is undefined. | 208 | the result of reading a discarded area is undefined. |
209 | What: /sys/block/<disk>/alias | ||
210 | Date: Aug 2011 | ||
211 | Contact: Nao Nishijima <nao.nishijima.xt@hitachi.com> | ||
212 | Description: | ||
213 | A raw device name of a disk does not always point a same disk | ||
214 | each boot-up time. Therefore, users have to use persistent | ||
215 | device names, which udev creates when the kernel finds a disk, | ||
216 | instead of raw device name. However, kernel doesn't show those | ||
217 | persistent names on its messages (e.g. dmesg). | ||
218 | This file can store an alias of the disk and it would be | ||
219 | appeared in kernel messages if it is set. A disk can have an | ||
220 | alias which length is up to 255bytes. Users can use alphabets, | ||
221 | numbers, "-" and "_" in alias name. This file is writeonce. | ||
diff --git a/Documentation/ABI/testing/sysfs-bus-bcma b/Documentation/ABI/testing/sysfs-bus-bcma index 06b62badddd1..721b4aea3020 100644 --- a/Documentation/ABI/testing/sysfs-bus-bcma +++ b/Documentation/ABI/testing/sysfs-bus-bcma | |||
@@ -1,6 +1,6 @@ | |||
1 | What: /sys/bus/bcma/devices/.../manuf | 1 | What: /sys/bus/bcma/devices/.../manuf |
2 | Date: May 2011 | 2 | Date: May 2011 |
3 | KernelVersion: 2.6.40 | 3 | KernelVersion: 3.0 |
4 | Contact: Rafał Miłecki <zajec5@gmail.com> | 4 | Contact: Rafał Miłecki <zajec5@gmail.com> |
5 | Description: | 5 | Description: |
6 | Each BCMA core has it's manufacturer id. See | 6 | Each BCMA core has it's manufacturer id. See |
@@ -8,7 +8,7 @@ Description: | |||
8 | 8 | ||
9 | What: /sys/bus/bcma/devices/.../id | 9 | What: /sys/bus/bcma/devices/.../id |
10 | Date: May 2011 | 10 | Date: May 2011 |
11 | KernelVersion: 2.6.40 | 11 | KernelVersion: 3.0 |
12 | Contact: Rafał Miłecki <zajec5@gmail.com> | 12 | Contact: Rafał Miłecki <zajec5@gmail.com> |
13 | Description: | 13 | Description: |
14 | There are a few types of BCMA cores, they can be identified by | 14 | There are a few types of BCMA cores, they can be identified by |
@@ -16,7 +16,7 @@ Description: | |||
16 | 16 | ||
17 | What: /sys/bus/bcma/devices/.../rev | 17 | What: /sys/bus/bcma/devices/.../rev |
18 | Date: May 2011 | 18 | Date: May 2011 |
19 | KernelVersion: 2.6.40 | 19 | KernelVersion: 3.0 |
20 | Contact: Rafał Miłecki <zajec5@gmail.com> | 20 | Contact: Rafał Miłecki <zajec5@gmail.com> |
21 | Description: | 21 | Description: |
22 | BCMA cores of the same type can still slightly differ depending | 22 | BCMA cores of the same type can still slightly differ depending |
@@ -24,7 +24,7 @@ Description: | |||
24 | 24 | ||
25 | What: /sys/bus/bcma/devices/.../class | 25 | What: /sys/bus/bcma/devices/.../class |
26 | Date: May 2011 | 26 | Date: May 2011 |
27 | KernelVersion: 2.6.40 | 27 | KernelVersion: 3.0 |
28 | Contact: Rafał Miłecki <zajec5@gmail.com> | 28 | Contact: Rafał Miłecki <zajec5@gmail.com> |
29 | Description: | 29 | Description: |
30 | Each BCMA core is identified by few fields, including class it | 30 | Each BCMA core is identified by few fields, including class it |
diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss index f5bb0a3bb8c0..53d99edd1d75 100644 --- a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss +++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss | |||
@@ -71,3 +71,10 @@ Description: Value of 1 indicates the controller can honor the reset_devices | |||
71 | a dump device, as kdump requires resetting the device in order | 71 | a dump device, as kdump requires resetting the device in order |
72 | to work reliably. | 72 | to work reliably. |
73 | 73 | ||
74 | Where: /sys/bus/pci/devices/<dev>/ccissX/transport_mode | ||
75 | Date: July 2011 | ||
76 | Kernel Version: 3.0 | ||
77 | Contact: iss_storagedev@hp.com | ||
78 | Description: Value of "simple" indicates that the controller has been placed | ||
79 | in "simple mode". Value of "performant" indicates that the | ||
80 | 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 new file mode 100644 index 000000000000..60c60fa624b2 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd | |||
@@ -0,0 +1,46 @@ | |||
1 | What: /sys/bus/pci/drivers/ehci_hcd/.../companion | ||
2 | /sys/bus/usb/devices/usbN/../companion | ||
3 | Date: January 2007 | ||
4 | KernelVersion: 2.6.21 | ||
5 | Contact: Alan Stern <stern@rowland.harvard.edu> | ||
6 | Description: | ||
7 | PCI-based EHCI USB controllers (i.e., high-speed USB-2.0 | ||
8 | controllers) are often implemented along with a set of | ||
9 | "companion" full/low-speed USB-1.1 controllers. When a | ||
10 | high-speed device is plugged in, the connection is routed | ||
11 | to the EHCI controller; when a full- or low-speed device | ||
12 | is plugged in, the connection is routed to the companion | ||
13 | controller. | ||
14 | |||
15 | Sometimes you want to force a high-speed device to connect | ||
16 | at full speed, which can be accomplished by forcing the | ||
17 | connection to be routed to the companion controller. | ||
18 | That's what this file does. Writing a port number to the | ||
19 | file causes connections on that port to be routed to the | ||
20 | companion controller, and writing the negative of a port | ||
21 | number returns the port to normal operation. | ||
22 | |||
23 | For example: To force the high-speed device attached to | ||
24 | port 4 on bus 2 to run at full speed: | ||
25 | |||
26 | echo 4 >/sys/bus/usb/devices/usb2/../companion | ||
27 | |||
28 | To return the port to high-speed operation: | ||
29 | |||
30 | echo -4 >/sys/bus/usb/devices/usb2/../companion | ||
31 | |||
32 | Reading the file gives the list of ports currently forced | ||
33 | to the companion controller. | ||
34 | |||
35 | Note: Some EHCI controllers do not have companions; they | ||
36 | may contain an internal "transaction translator" or they | ||
37 | may be attached directly to a "rate-matching hub". This | ||
38 | mechanism will not work with such controllers. Also, it | ||
39 | cannot be used to force a port on a high-speed hub to | ||
40 | connect at full speed. | ||
41 | |||
42 | Note: When this file was first added, it appeared in a | ||
43 | different sysfs directory. The location given above is | ||
44 | correct for 2.6.35 (and probably several earlier kernel | ||
45 | versions as well). | ||
46 | |||
diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb index 294aa864a60a..e647378e9e88 100644 --- a/Documentation/ABI/testing/sysfs-bus-usb +++ b/Documentation/ABI/testing/sysfs-bus-usb | |||
@@ -142,3 +142,18 @@ Description: | |||
142 | such devices. | 142 | such devices. |
143 | Users: | 143 | Users: |
144 | usb_modeswitch | 144 | usb_modeswitch |
145 | |||
146 | What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm | ||
147 | Date: September 2011 | ||
148 | Contact: Andiry Xu <andiry.xu@amd.com> | ||
149 | Description: | ||
150 | If CONFIG_USB_SUSPEND is set and a USB 2.0 lpm-capable device | ||
151 | is plugged in to a xHCI host which support link PM, it will | ||
152 | perform a LPM test; if the test is passed and host supports | ||
153 | USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will | ||
154 | be enabled for the device and the USB device directory will | ||
155 | contain a file named power/usb2_hardware_lpm. The file holds | ||
156 | a string value (enable or disable) indicating whether or not | ||
157 | USB2 hardware LPM is enabled for the device. Developer can | ||
158 | write y/Y/1 or n/N/0 to the file to enable/disable the | ||
159 | feature. | ||
diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 index aa11dbdd794b..4a9c545bda4b 100644 --- a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 +++ b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 | |||
@@ -4,8 +4,8 @@ What: /sys/class/backlight/<backlight>/l2_bright_max | |||
4 | What: /sys/class/backlight/<backlight>/l3_office_max | 4 | What: /sys/class/backlight/<backlight>/l3_office_max |
5 | What: /sys/class/backlight/<backlight>/l4_indoor_max | 5 | What: /sys/class/backlight/<backlight>/l4_indoor_max |
6 | What: /sys/class/backlight/<backlight>/l5_dark_max | 6 | What: /sys/class/backlight/<backlight>/l5_dark_max |
7 | Date: Mai 2011 | 7 | Date: May 2011 |
8 | KernelVersion: 2.6.40 | 8 | KernelVersion: 3.0 |
9 | Contact: device-drivers-devel@blackfin.uclinux.org | 9 | Contact: device-drivers-devel@blackfin.uclinux.org |
10 | Description: | 10 | Description: |
11 | Control the maximum brightness for <ambient light zone> | 11 | Control the maximum brightness for <ambient light zone> |
@@ -18,8 +18,8 @@ What: /sys/class/backlight/<backlight>/l2_bright_dim | |||
18 | What: /sys/class/backlight/<backlight>/l3_office_dim | 18 | What: /sys/class/backlight/<backlight>/l3_office_dim |
19 | What: /sys/class/backlight/<backlight>/l4_indoor_dim | 19 | What: /sys/class/backlight/<backlight>/l4_indoor_dim |
20 | What: /sys/class/backlight/<backlight>/l5_dark_dim | 20 | What: /sys/class/backlight/<backlight>/l5_dark_dim |
21 | Date: Mai 2011 | 21 | Date: May 2011 |
22 | KernelVersion: 2.6.40 | 22 | KernelVersion: 3.0 |
23 | Contact: device-drivers-devel@blackfin.uclinux.org | 23 | Contact: device-drivers-devel@blackfin.uclinux.org |
24 | Description: | 24 | Description: |
25 | Control the dim brightness for <ambient light zone> | 25 | Control the dim brightness for <ambient light zone> |
@@ -29,8 +29,8 @@ Description: | |||
29 | this <ambient light zone>. | 29 | this <ambient light zone>. |
30 | 30 | ||
31 | What: /sys/class/backlight/<backlight>/ambient_light_level | 31 | What: /sys/class/backlight/<backlight>/ambient_light_level |
32 | Date: Mai 2011 | 32 | Date: May 2011 |
33 | KernelVersion: 2.6.40 | 33 | KernelVersion: 3.0 |
34 | Contact: device-drivers-devel@blackfin.uclinux.org | 34 | Contact: device-drivers-devel@blackfin.uclinux.org |
35 | Description: | 35 | Description: |
36 | Get conversion value of the light sensor. | 36 | Get conversion value of the light sensor. |
@@ -39,8 +39,8 @@ Description: | |||
39 | 8000 (max ambient brightness) | 39 | 8000 (max ambient brightness) |
40 | 40 | ||
41 | What: /sys/class/backlight/<backlight>/ambient_light_zone | 41 | What: /sys/class/backlight/<backlight>/ambient_light_zone |
42 | Date: Mai 2011 | 42 | Date: May 2011 |
43 | KernelVersion: 2.6.40 | 43 | KernelVersion: 3.0 |
44 | Contact: device-drivers-devel@blackfin.uclinux.org | 44 | Contact: device-drivers-devel@blackfin.uclinux.org |
45 | Description: | 45 | Description: |
46 | Get/Set current ambient light zone. Reading returns | 46 | Get/Set current ambient light zone. Reading returns |
diff --git a/Documentation/ABI/testing/sysfs-class-devfreq b/Documentation/ABI/testing/sysfs-class-devfreq new file mode 100644 index 000000000000..23d78b5aab11 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-class-devfreq | |||
@@ -0,0 +1,52 @@ | |||
1 | What: /sys/class/devfreq/.../ | ||
2 | Date: September 2011 | ||
3 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
4 | Description: | ||
5 | Provide a place in sysfs for the devfreq objects. | ||
6 | This allows accessing various devfreq specific variables. | ||
7 | The name of devfreq object denoted as ... is same as the | ||
8 | name of device using devfreq. | ||
9 | |||
10 | What: /sys/class/devfreq/.../governor | ||
11 | Date: September 2011 | ||
12 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
13 | Description: | ||
14 | The /sys/class/devfreq/.../governor shows the name of the | ||
15 | governor used by the corresponding devfreq object. | ||
16 | |||
17 | What: /sys/class/devfreq/.../cur_freq | ||
18 | Date: September 2011 | ||
19 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
20 | Description: | ||
21 | The /sys/class/devfreq/.../cur_freq shows the current | ||
22 | frequency of the corresponding devfreq object. | ||
23 | |||
24 | What: /sys/class/devfreq/.../central_polling | ||
25 | Date: September 2011 | ||
26 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
27 | Description: | ||
28 | The /sys/class/devfreq/.../central_polling shows whether | ||
29 | the devfreq ojbect is using devfreq-provided central | ||
30 | polling mechanism or not. | ||
31 | |||
32 | What: /sys/class/devfreq/.../polling_interval | ||
33 | Date: September 2011 | ||
34 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
35 | Description: | ||
36 | The /sys/class/devfreq/.../polling_interval shows and sets | ||
37 | the requested polling interval of the corresponding devfreq | ||
38 | object. The values are represented in ms. If the value is | ||
39 | less than 1 jiffy, it is considered to be 0, which means | ||
40 | no polling. This value is meaningless if the governor is | ||
41 | not polling; thus. If the governor is not using | ||
42 | devfreq-provided central polling | ||
43 | (/sys/class/devfreq/.../central_polling is 0), this value | ||
44 | may be useless. | ||
45 | |||
46 | What: /sys/class/devfreq/.../userspace/set_freq | ||
47 | Date: September 2011 | ||
48 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | ||
49 | Description: | ||
50 | The /sys/class/devfreq/.../userspace/set_freq shows and | ||
51 | sets the requested frequency for the devfreq object if | ||
52 | userspace governor is in effect. | ||
diff --git a/Documentation/ABI/testing/sysfs-class-net-mesh b/Documentation/ABI/testing/sysfs-class-net-mesh index 748fe1701d25..b02001488eef 100644 --- a/Documentation/ABI/testing/sysfs-class-net-mesh +++ b/Documentation/ABI/testing/sysfs-class-net-mesh | |||
@@ -22,6 +22,14 @@ Description: | |||
22 | mesh will be fragmented or silently discarded if the | 22 | mesh will be fragmented or silently discarded if the |
23 | packet size exceeds the outgoing interface MTU. | 23 | packet size exceeds the outgoing interface MTU. |
24 | 24 | ||
25 | What: /sys/class/net/<mesh_iface>/mesh/ap_isolation | ||
26 | Date: May 2011 | ||
27 | Contact: Antonio Quartulli <ordex@autistici.org> | ||
28 | Description: | ||
29 | Indicates whether the data traffic going from a | ||
30 | wireless client to another wireless client will be | ||
31 | silently dropped. | ||
32 | |||
25 | What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth | 33 | What: /sys/class/net/<mesh_iface>/mesh/gw_bandwidth |
26 | Date: October 2010 | 34 | Date: October 2010 |
27 | Contact: Marek Lindner <lindner_marek@yahoo.de> | 35 | Contact: Marek Lindner <lindner_marek@yahoo.de> |
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff b/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff new file mode 100644 index 000000000000..9aec8ef228b0 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff | |||
@@ -0,0 +1,7 @@ | |||
1 | What: /sys/module/hid_logitech/drivers/hid:logitech/<dev>/range. | ||
2 | Date: July 2011 | ||
3 | KernelVersion: 3.2 | ||
4 | Contact: Michal Malý <madcatxster@gmail.com> | ||
5 | Description: Display minimum, maximum and current range of the steering | ||
6 | wheel. Writing a value within min and max boundaries sets the | ||
7 | range of the wheel. | ||
diff --git a/Documentation/ABI/testing/sysfs-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom new file mode 100644 index 000000000000..82d4df136444 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-driver-wacom | |||
@@ -0,0 +1,72 @@ | |||
1 | What: /sys/class/hidraw/hidraw*/device/speed | ||
2 | Date: April 2010 | ||
3 | Kernel Version: 2.6.35 | ||
4 | Contact: linux-bluetooth@vger.kernel.org | ||
5 | Description: | ||
6 | The /sys/class/hidraw/hidraw*/device/speed file controls | ||
7 | reporting speed of Wacom bluetooth tablet. Reading from | ||
8 | this file returns 1 if tablet reports in high speed mode | ||
9 | or 0 otherwise. Writing to this file one of these values | ||
10 | switches reporting speed. | ||
11 | |||
12 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led | ||
13 | Date: August 2011 | ||
14 | Contact: linux-input@vger.kernel.org | ||
15 | Description: | ||
16 | Attribute group for control of the status LEDs and the OLEDs. | ||
17 | This attribute group is only available for Intuos 4 M, L, | ||
18 | and XL (with LEDs and OLEDs) and Cintiq 21UX2 (LEDs only). | ||
19 | Therefore its presence implicitly signifies the presence of | ||
20 | said LEDs and OLEDs on the tablet device. | ||
21 | |||
22 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance | ||
23 | Date: August 2011 | ||
24 | Contact: linux-input@vger.kernel.org | ||
25 | Description: | ||
26 | Writing to this file sets the status LED luminance (1..127) | ||
27 | when the stylus does not touch the tablet surface, and no | ||
28 | button is pressed on the stylus. This luminance level is | ||
29 | normally lower than the level when a button is pressed. | ||
30 | |||
31 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status1_luminance | ||
32 | Date: August 2011 | ||
33 | Contact: linux-input@vger.kernel.org | ||
34 | Description: | ||
35 | Writing to this file sets the status LED luminance (1..127) | ||
36 | when the stylus touches the tablet surface, or any button is | ||
37 | pressed on the stylus. | ||
38 | |||
39 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led0_select | ||
40 | Date: August 2011 | ||
41 | Contact: linux-input@vger.kernel.org | ||
42 | Description: | ||
43 | Writing to this file sets which one of the four (for Intuos 4) | ||
44 | or of the right four (for Cintiq 21UX2) status LEDs is active (0..3). | ||
45 | The other three LEDs on the same side are always inactive. | ||
46 | |||
47 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select | ||
48 | Date: September 2011 | ||
49 | Contact: linux-input@vger.kernel.org | ||
50 | Description: | ||
51 | Writing to this file sets which one of the left four (for Cintiq 21UX2) | ||
52 | status LEDs is active (0..3). The other three LEDs on the left are always | ||
53 | inactive. | ||
54 | |||
55 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/buttons_luminance | ||
56 | Date: August 2011 | ||
57 | Contact: linux-input@vger.kernel.org | ||
58 | Description: | ||
59 | Writing to this file sets the overall luminance level (0..15) | ||
60 | of all eight button OLED displays. | ||
61 | |||
62 | What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/button<n>_rawimg | ||
63 | Date: August 2011 | ||
64 | Contact: linux-input@vger.kernel.org | ||
65 | Description: | ||
66 | When writing a 1024 byte raw image in Wacom Intuos 4 | ||
67 | interleaving format to the file, the image shows up on Button N | ||
68 | of the device. The image is a 64x32 pixel 4-bit gray image. The | ||
69 | 1024 byte binary is split up into 16x 64 byte chunks. Each 64 | ||
70 | byte chunk encodes the image data for two consecutive lines on | ||
71 | the display. The low nibble of each byte contains the first | ||
72 | line, and the high nibble contains the second line. | ||
diff --git a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop index ff53183c3848..814b01354c41 100644 --- a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop +++ b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop | |||
@@ -5,19 +5,4 @@ Contact: "Ike Panhc <ike.pan@canonical.com>" | |||
5 | Description: | 5 | Description: |
6 | Control the power of camera module. 1 means on, 0 means off. | 6 | Control the power of camera module. 1 means on, 0 means off. |
7 | 7 | ||
8 | What: /sys/devices/platform/ideapad/cfg | ||
9 | Date: Jun 2011 | ||
10 | KernelVersion: 3.1 | ||
11 | Contact: "Ike Panhc <ike.pan@canonical.com>" | ||
12 | Description: | ||
13 | Ideapad capability bits. | ||
14 | Bit 8-10: 1 - Intel graphic only | ||
15 | 2 - ATI graphic only | ||
16 | 3 - Nvidia graphic only | ||
17 | 4 - Intel and ATI graphic | ||
18 | 5 - Intel and Nvidia graphic | ||
19 | Bit 16: Bluetooth exist (1 for exist) | ||
20 | Bit 17: 3G exist (1 for exist) | ||
21 | Bit 18: Wifi exist (1 for exist) | ||
22 | Bit 19: Camera exist (1 for exist) | ||
23 | 8 | ||
diff --git a/Documentation/ABI/testing/sysfs-wacom b/Documentation/ABI/testing/sysfs-wacom deleted file mode 100644 index 1517976e25c4..000000000000 --- a/Documentation/ABI/testing/sysfs-wacom +++ /dev/null | |||
@@ -1,10 +0,0 @@ | |||
1 | What: /sys/class/hidraw/hidraw*/device/speed | ||
2 | Date: April 2010 | ||
3 | Kernel Version: 2.6.35 | ||
4 | Contact: linux-bluetooth@vger.kernel.org | ||
5 | Description: | ||
6 | The /sys/class/hidraw/hidraw*/device/speed file controls | ||
7 | reporting speed of wacom bluetooth tablet. Reading from | ||
8 | this file returns 1 if tablet reports in high speed mode | ||
9 | or 0 otherwise. Writing to this file one of these values | ||
10 | switches reporting speed. | ||