diff options
author | Arnd Bergmann <arnd@arndb.de> | 2011-07-28 11:25:46 -0400 |
---|---|---|
committer | Arnd Bergmann <arnd@arndb.de> | 2011-07-28 11:25:46 -0400 |
commit | 6124a4e430b64d1577438c8648c59e996d02e73e (patch) | |
tree | 49cfafad785d1c9e403a5b0d755298b9af2c260f /Documentation/ABI | |
parent | 8e267f3da5f117d2f1316cf6ddf740f93f1c73aa (diff) | |
parent | 580975d7f48d7d047e22bb0f42adf7557801d8d4 (diff) |
Merge branch 'imx/dt' into next/dt
Diffstat (limited to 'Documentation/ABI')
-rw-r--r-- | Documentation/ABI/obsolete/proc-pid-oom_adj | 2 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 | 21 | ||||
-rw-r--r-- | Documentation/ABI/testing/sysfs-module | 23 |
3 files changed, 45 insertions, 1 deletions
diff --git a/Documentation/ABI/obsolete/proc-pid-oom_adj b/Documentation/ABI/obsolete/proc-pid-oom_adj index cf63f264ce0f..9a3cb88ade47 100644 --- a/Documentation/ABI/obsolete/proc-pid-oom_adj +++ b/Documentation/ABI/obsolete/proc-pid-oom_adj | |||
@@ -14,7 +14,7 @@ Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's | |||
14 | 14 | ||
15 | A much more powerful interface, /proc/<pid>/oom_score_adj, was | 15 | A much more powerful interface, /proc/<pid>/oom_score_adj, was |
16 | introduced with the oom killer rewrite that allows users to increase or | 16 | introduced with the oom killer rewrite that allows users to increase or |
17 | decrease the badness() score linearly. This interface will replace | 17 | decrease the badness score linearly. This interface will replace |
18 | /proc/<pid>/oom_adj. | 18 | /proc/<pid>/oom_adj. |
19 | 19 | ||
20 | A warning will be emitted to the kernel log if an application uses this | 20 | A warning will be emitted to the kernel log if an application uses this |
diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 new file mode 100644 index 000000000000..9de269bb0ae5 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480 | |||
@@ -0,0 +1,21 @@ | |||
1 | What: /sys/bus/i2c/devices/.../device | ||
2 | Date: February 2011 | ||
3 | Contact: Minkyu Kang <mk7.kang@samsung.com> | ||
4 | Description: | ||
5 | show what device is attached | ||
6 | NONE - no device | ||
7 | USB - USB device is attached | ||
8 | UART - UART is attached | ||
9 | CHARGER - Charger is attaced | ||
10 | JIG - JIG is attached | ||
11 | |||
12 | What: /sys/bus/i2c/devices/.../switch | ||
13 | Date: February 2011 | ||
14 | Contact: Minkyu Kang <mk7.kang@samsung.com> | ||
15 | Description: | ||
16 | show or set the state of manual switch | ||
17 | VAUDIO - switch to VAUDIO path | ||
18 | UART - switch to UART path | ||
19 | AUDIO - switch to AUDIO path | ||
20 | DHOST - switch to DHOST path | ||
21 | AUTO - switch automatically by device | ||
diff --git a/Documentation/ABI/testing/sysfs-module b/Documentation/ABI/testing/sysfs-module index cfcec3bffc0a..9489ea8e294c 100644 --- a/Documentation/ABI/testing/sysfs-module +++ b/Documentation/ABI/testing/sysfs-module | |||
@@ -10,3 +10,26 @@ KernelVersion: 2.6.35 | |||
10 | Contact: masa-korg@dsn.okisemi.com | 10 | Contact: masa-korg@dsn.okisemi.com |
11 | Description: Write/read Option ROM data. | 11 | Description: Write/read Option ROM data. |
12 | 12 | ||
13 | |||
14 | What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max | ||
15 | Date: July 2011 | ||
16 | KernelVersion: 3.1 | ||
17 | Contact: Kirill Smelkov <kirr@mns.spb.ru> | ||
18 | Description: Maximum time allowed for periodic transfers per microframe (μs) | ||
19 | |||
20 | [ USB 2.0 sets maximum allowed time for periodic transfers per | ||
21 | microframe to be 80%, that is 100 microseconds out of 125 | ||
22 | microseconds (full microframe). | ||
23 | |||
24 | However there are cases, when 80% max isochronous bandwidth is | ||
25 | too limiting. For example two video streams could require 110 | ||
26 | microseconds of isochronous bandwidth per microframe to work | ||
27 | together. ] | ||
28 | |||
29 | Through this setting it is possible to raise the limit so that | ||
30 | the host controller would allow allocating more than 100 | ||
31 | microseconds of periodic bandwidth per microframe. | ||
32 | |||
33 | Beware, non-standard modes are usually not thoroughly tested by | ||
34 | hardware designers, and the hardware can malfunction when this | ||
35 | setting differ from default 100. | ||