diff options
Diffstat (limited to 'Documentation/ABI/testing')
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-pci | 12 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-usb | 7 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-class-extcon | 22 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-class-regulator | 21 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-driver-wacom | 13 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-platform-ideapad-laptop | 11 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-tty | 9 |
7 files changed, 84 insertions, 11 deletions
diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci index 34f51100f02..dff1f48d252 100644 --- a/Documentation/ABI/testing/sysfs-bus-pci +++ b/Documentation/ABI/testing/sysfs-bus-pci | |||
@@ -210,3 +210,15 @@ Users: | |||
210 | firmware assigned instance number of the PCI | 210 | firmware assigned instance number of the PCI |
211 | device that can help in understanding the firmware | 211 | device that can help in understanding the firmware |
212 | intended order of the PCI device. | 212 | intended order of the PCI device. |
213 | |||
214 | What: /sys/bus/pci/devices/.../d3cold_allowed | ||
215 | Date: July 2012 | ||
216 | Contact: Huang Ying <ying.huang@intel.com> | ||
217 | Description: | ||
218 | d3cold_allowed is bit to control whether the corresponding PCI | ||
219 | device can be put into D3Cold state. If it is cleared, the | ||
220 | device will never be put into D3Cold state. If it is set, the | ||
221 | device may be put into D3Cold state if other requirements are | ||
222 | satisfied too. Reading this attribute will show the current | ||
223 | value of d3cold_allowed bit. Writing this attribute will set | ||
224 | the value of d3cold_allowed bit. | ||
diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb index 5f75f8f7df3..b6fbe514a86 100644 --- a/Documentation/ABI/testing/sysfs-bus-usb +++ b/Documentation/ABI/testing/sysfs-bus-usb | |||
@@ -220,3 +220,10 @@ Description: | |||
220 | If the device doesn't support LTM, the file will read "no". | 220 | If the device doesn't support LTM, the file will read "no". |
221 | The file will be present for all speeds of USB devices, and will | 221 | The file will be present for all speeds of USB devices, and will |
222 | always read "no" for USB 1.1 and USB 2.0 devices. | 222 | always read "no" for USB 1.1 and USB 2.0 devices. |
223 | |||
224 | What: /sys/bus/usb/devices/.../(hub interface)/portX | ||
225 | Date: August 2012 | ||
226 | Contact: Lan Tianyu <tianyu.lan@intel.com> | ||
227 | Description: | ||
228 | The /sys/bus/usb/devices/.../(hub interface)/portX | ||
229 | is usb port device's sysfs directory. | ||
diff --git a/Documentation/ABI/testing/sysfs-class-extcon b/Documentation/ABI/testing/sysfs-class-extcon index 20ab361bd8c..57a72623291 100644 --- a/Documentation/ABI/testing/sysfs-class-extcon +++ b/Documentation/ABI/testing/sysfs-class-extcon | |||
@@ -13,7 +13,7 @@ Description: | |||
13 | accessory cables have such capability. For example, | 13 | accessory cables have such capability. For example, |
14 | the 30-pin port of Nuri board (/arch/arm/mach-exynos) | 14 | the 30-pin port of Nuri board (/arch/arm/mach-exynos) |
15 | may have both HDMI and Charger attached, or analog audio, | 15 | may have both HDMI and Charger attached, or analog audio, |
16 | video, and USB cables attached simulteneously. | 16 | video, and USB cables attached simultaneously. |
17 | 17 | ||
18 | If there are cables mutually exclusive with each other, | 18 | If there are cables mutually exclusive with each other, |
19 | such binary relations may be expressed with extcon_dev's | 19 | such binary relations may be expressed with extcon_dev's |
@@ -35,7 +35,7 @@ Description: | |||
35 | The /sys/class/extcon/.../state shows and stores the cable | 35 | The /sys/class/extcon/.../state shows and stores the cable |
36 | attach/detach information of the corresponding extcon object. | 36 | attach/detach information of the corresponding extcon object. |
37 | If the extcon object has an optional callback "show_state" | 37 | If the extcon object has an optional callback "show_state" |
38 | defined, the showing function is overriden with the optional | 38 | defined, the showing function is overridden with the optional |
39 | callback. | 39 | callback. |
40 | 40 | ||
41 | If the default callback for showing function is used, the | 41 | If the default callback for showing function is used, the |
@@ -46,19 +46,19 @@ Description: | |||
46 | TA=1 | 46 | TA=1 |
47 | EAR_JACK=0 | 47 | EAR_JACK=0 |
48 | # | 48 | # |
49 | In this example, the extcon device have USB_OTG and TA | 49 | In this example, the extcon device has USB_OTG and TA |
50 | cables attached and HDMI and EAR_JACK cables detached. | 50 | cables attached and HDMI and EAR_JACK cables detached. |
51 | 51 | ||
52 | In order to update the state of an extcon device, enter a hex | 52 | In order to update the state of an extcon device, enter a hex |
53 | state number starting with 0x. | 53 | state number starting with 0x: |
54 | echo 0xHEX > state | 54 | # echo 0xHEX > state |
55 | 55 | ||
56 | This updates the whole state of the extcon dev. | 56 | This updates the whole state of the extcon device. |
57 | Inputs of all the methods are required to meet the | 57 | Inputs of all the methods are required to meet the |
58 | mutually_exclusive contidions if they exist. | 58 | mutually_exclusive conditions if they exist. |
59 | 59 | ||
60 | It is recommended to use this "global" state interface if | 60 | It is recommended to use this "global" state interface if |
61 | you need to enter the value atomically. The later state | 61 | you need to set the value atomically. The later state |
62 | interface associated with each cable cannot update | 62 | interface associated with each cable cannot update |
63 | multiple cable states of an extcon device simultaneously. | 63 | multiple cable states of an extcon device simultaneously. |
64 | 64 | ||
@@ -73,7 +73,7 @@ What: /sys/class/extcon/.../cable.x/state | |||
73 | Date: February 2012 | 73 | Date: February 2012 |
74 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | 74 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> |
75 | Description: | 75 | Description: |
76 | The /sys/class/extcon/.../cable.x/name shows and stores the | 76 | The /sys/class/extcon/.../cable.x/state shows and stores the |
77 | state of cable "x" (integer between 0 and 31) of an extcon | 77 | state of cable "x" (integer between 0 and 31) of an extcon |
78 | device. The state value is either 0 (detached) or 1 | 78 | device. The state value is either 0 (detached) or 1 |
79 | (attached). | 79 | (attached). |
@@ -83,8 +83,8 @@ Date: December 2011 | |||
83 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> | 83 | Contact: MyungJoo Ham <myungjoo.ham@samsung.com> |
84 | Description: | 84 | Description: |
85 | Shows the relations of mutually exclusiveness. For example, | 85 | Shows the relations of mutually exclusiveness. For example, |
86 | if the mutually_exclusive array of extcon_dev is | 86 | if the mutually_exclusive array of extcon device is |
87 | {0x3, 0x5, 0xC, 0x0}, the, the output is: | 87 | {0x3, 0x5, 0xC, 0x0}, then the output is: |
88 | # ls mutually_exclusive/ | 88 | # ls mutually_exclusive/ |
89 | 0x3 | 89 | 0x3 |
90 | 0x5 | 90 | 0x5 |
diff --git a/Documentation/ABI/testing/sysfs-class-regulator b/Documentation/ABI/testing/sysfs-class-regulator index e091fa87379..bc578bc6062 100644 --- a/Documentation/ABI/testing/sysfs-class-regulator +++ b/Documentation/ABI/testing/sysfs-class-regulator | |||
@@ -349,3 +349,24 @@ Description: | |||
349 | 349 | ||
350 | This will be one of the same strings reported by | 350 | This will be one of the same strings reported by |
351 | the "state" attribute. | 351 | the "state" attribute. |
352 | |||
353 | What: /sys/class/regulator/.../bypass | ||
354 | Date: September 2012 | ||
355 | KernelVersion: 3.7 | ||
356 | Contact: Mark Brown <broonie@opensource.wolfsonmicro.com> | ||
357 | Description: | ||
358 | Some regulator directories will contain a field called | ||
359 | bypass. This indicates if the device is in bypass mode. | ||
360 | |||
361 | This will be one of the following strings: | ||
362 | |||
363 | 'enabled' | ||
364 | 'disabled' | ||
365 | 'unknown' | ||
366 | |||
367 | 'enabled' means the regulator is in bypass mode. | ||
368 | |||
369 | 'disabled' means that the regulator is regulating. | ||
370 | |||
371 | 'unknown' means software cannot determine the state, or | ||
372 | the reported state is invalid. | ||
diff --git a/Documentation/ABI/testing/sysfs-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom index 8d55a83d692..7fc781048b7 100644 --- a/Documentation/ABI/testing/sysfs-driver-wacom +++ b/Documentation/ABI/testing/sysfs-driver-wacom | |||
@@ -1,3 +1,16 @@ | |||
1 | WWhat: /sys/class/hidraw/hidraw*/device/oled*_img | ||
2 | Date: June 2012 | ||
3 | Contact: linux-bluetooth@vger.kernel.org | ||
4 | Description: | ||
5 | The /sys/class/hidraw/hidraw*/device/oled*_img files control | ||
6 | OLED mocro displays on Intuos4 Wireless tablet. Accepted image | ||
7 | has to contain 256 bytes (64x32 px 1 bit colour). The format | ||
8 | is the same as PBM image 62x32px without header (64 bits per | ||
9 | horizontal line, 32 lines). An example of setting OLED No. 0: | ||
10 | dd bs=256 count=1 if=img_file of=[path to oled0_img]/oled0_img | ||
11 | The attribute is read only and no local copy of the image is | ||
12 | stored. | ||
13 | |||
1 | What: /sys/class/hidraw/hidraw*/device/speed | 14 | What: /sys/class/hidraw/hidraw*/device/speed |
2 | Date: April 2010 | 15 | Date: April 2010 |
3 | Kernel Version: 2.6.35 | 16 | Kernel Version: 2.6.35 |
diff --git a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop index 814b01354c4..b31e782bd98 100644 --- a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop +++ b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop | |||
@@ -5,4 +5,15 @@ 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/fan_mode | ||
9 | Date: June 2012 | ||
10 | KernelVersion: 3.6 | ||
11 | Contact: "Maxim Mikityanskiy <maxtram95@gmail.com>" | ||
12 | Description: | ||
13 | Change fan mode | ||
14 | There are four available modes: | ||
15 | * 0 -> Super Silent Mode | ||
16 | * 1 -> Standard Mode | ||
17 | * 2 -> Dust Cleaning | ||
18 | * 4 -> Efficient Thermal Dissipation Mode | ||
8 | 19 | ||
diff --git a/Documentation/ABI/testing/sysfs-tty b/Documentation/ABI/testing/sysfs-tty index b138b663bf5..0c430150d92 100644 --- a/Documentation/ABI/testing/sysfs-tty +++ b/Documentation/ABI/testing/sysfs-tty | |||
@@ -17,3 +17,12 @@ Description: | |||
17 | device, like 'tty1'. | 17 | device, like 'tty1'. |
18 | The file supports poll() to detect virtual | 18 | The file supports poll() to detect virtual |
19 | console switches. | 19 | console switches. |
20 | |||
21 | What: /sys/class/tty/ttyS0/uartclk | ||
22 | Date: Sep 2012 | ||
23 | Contact: Tomas Hlavacek <tmshlvck@gmail.com> | ||
24 | Description: | ||
25 | Shows the current uartclk value associated with the | ||
26 | UART port in serial_core, that is bound to TTY like ttyS0. | ||
27 | uartclk = 16 * baud_base | ||
28 | |||