aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing
diff options
context:
space:
mode:
authorJonathan Herman <hermanjl@cs.unc.edu>2013-01-17 16:15:55 -0500
committerJonathan Herman <hermanjl@cs.unc.edu>2013-01-17 16:15:55 -0500
commit8dea78da5cee153b8af9c07a2745f6c55057fe12 (patch)
treea8f4d49d63b1ecc92f2fddceba0655b2472c5bd9 /Documentation/ABI/testing
parent406089d01562f1e2bf9f089fd7637009ebaad589 (diff)
Patched in Tegra support.
Diffstat (limited to 'Documentation/ABI/testing')
-rw-r--r--Documentation/ABI/testing/debugfs-ideapad19
-rw-r--r--Documentation/ABI/testing/debugfs-olpc16
-rw-r--r--Documentation/ABI/testing/debugfs-pfo-nx-crypto45
-rw-r--r--Documentation/ABI/testing/dev-kmsg101
-rw-r--r--Documentation/ABI/testing/evm23
-rw-r--r--Documentation/ABI/testing/ima_policy28
-rw-r--r--Documentation/ABI/testing/sysfs-block14
-rw-r--r--Documentation/ABI/testing/sysfs-block-dm25
-rw-r--r--Documentation/ABI/testing/sysfs-block-rssd5
-rw-r--r--Documentation/ABI/testing/sysfs-block-zram2
-rw-r--r--Documentation/ABI/testing/sysfs-bus-bcma8
-rw-r--r--Documentation/ABI/testing/sysfs-bus-event_source-devices-format14
-rw-r--r--Documentation/ABI/testing/sysfs-bus-fcoe77
-rw-r--r--Documentation/ABI/testing/sysfs-bus-hsi19
-rw-r--r--Documentation/ABI/testing/sysfs-bus-i2c-devices-lm353315
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio794
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio-frequency-ad952337
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio-frequency-adf435021
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als61
-rw-r--r--Documentation/ABI/testing/sysfs-bus-mdio9
-rw-r--r--Documentation/ABI/testing/sysfs-bus-pci64
-rw-r--r--Documentation/ABI/testing/sysfs-bus-pci-devices-cciss7
-rw-r--r--Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd46
-rw-r--r--Documentation/ABI/testing/sysfs-bus-rbd43
-rw-r--r--Documentation/ABI/testing/sysfs-bus-rpmsg75
-rw-r--r--Documentation/ABI/testing/sysfs-bus-usb85
-rw-r--r--Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg2
-rw-r--r--Documentation/ABI/testing/sysfs-cfq-target-latency8
-rw-r--r--Documentation/ABI/testing/sysfs-class2
-rw-r--r--Documentation/ABI/testing/sysfs-class-backlight-driver-adp887018
-rw-r--r--Documentation/ABI/testing/sysfs-class-backlight-driver-lm353348
-rw-r--r--Documentation/ABI/testing/sysfs-class-devfreq80
-rw-r--r--Documentation/ABI/testing/sysfs-class-extcon97
-rw-r--r--Documentation/ABI/testing/sysfs-class-led-driver-lm353365
-rw-r--r--Documentation/ABI/testing/sysfs-class-mtd52
-rw-r--r--Documentation/ABI/testing/sysfs-class-net-batman-adv11
-rw-r--r--Documentation/ABI/testing/sysfs-class-net-grcan35
-rw-r--r--Documentation/ABI/testing/sysfs-class-net-mesh34
-rw-r--r--Documentation/ABI/testing/sysfs-class-regulator21
-rw-r--r--Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration12
-rw-r--r--Documentation/ABI/testing/sysfs-devices2
-rw-r--r--Documentation/ABI/testing/sysfs-devices-edac140
-rw-r--r--Documentation/ABI/testing/sysfs-devices-firmware_node17
-rw-r--r--Documentation/ABI/testing/sysfs-devices-platform-docg334
-rw-r--r--Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb44
-rw-r--r--Documentation/ABI/testing/sysfs-devices-power84
-rw-r--r--Documentation/ABI/testing/sysfs-devices-soc58
-rw-r--r--Documentation/ABI/testing/sysfs-devices-sun14
-rw-r--r--Documentation/ABI/testing/sysfs-devices-system-cpu36
-rw-r--r--Documentation/ABI/testing/sysfs-devices-system-xen_cpu20
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd38
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff7
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-multitouch9
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-isku143
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus48
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus69
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-lua7
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra76
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-roccat-savu76
-rw-r--r--Documentation/ABI/testing/sysfs-driver-hid-wiimote12
-rw-r--r--Documentation/ABI/testing/sysfs-driver-ppi70
-rw-r--r--Documentation/ABI/testing/sysfs-driver-samsung-laptop20
-rw-r--r--Documentation/ABI/testing/sysfs-driver-wacom95
-rw-r--r--Documentation/ABI/testing/sysfs-firmware-acpi20
-rw-r--r--Documentation/ABI/testing/sysfs-fs-ext413
-rw-r--r--Documentation/ABI/testing/sysfs-kernel-iommu_groups14
-rw-r--r--Documentation/ABI/testing/sysfs-kernel-slab4
-rw-r--r--Documentation/ABI/testing/sysfs-module16
-rw-r--r--Documentation/ABI/testing/sysfs-platform-asus-wmi7
-rw-r--r--Documentation/ABI/testing/sysfs-platform-ideapad-laptop24
-rw-r--r--Documentation/ABI/testing/sysfs-power72
-rw-r--r--Documentation/ABI/testing/sysfs-profiling6
-rw-r--r--Documentation/ABI/testing/sysfs-ptp6
-rw-r--r--Documentation/ABI/testing/sysfs-tty121
74 files changed, 263 insertions, 3297 deletions
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 @@
1What: /sys/kernel/debug/ideapad/cfg
2Date: Sep 2011
3KernelVersion: 3.2
4Contact: Ike Panhc <ike.pan@canonical.com>
5Description:
6
7cfg shows the return value of _CFG method in VPC2004 device. It tells machine
8capability and what graphic component within the machine.
9
10
11What: /sys/kernel/debug/ideapad/status
12Date: Sep 2011
13KernelVersion: 3.2
14Contact: Ike Panhc <ike.pan@canonical.com>
15Description:
16
17status shows infos we can read and tells its meaning and value.
18
19
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 @@
1What: /sys/kernel/debug/olpc-ec/cmd
2Date: Dec 2011
3KernelVersion: 3.4
4Contact: devel@lists.laptop.org
5Description:
6
7A generic interface for executing OLPC Embedded Controller commands and
8reading their responses.
9
10To execute a command, write data with the format: CC:N A A A A
11CC is the (hex) command, N is the count of expected reply bytes, and A A A A
12are optional (hex) arguments.
13
14To read the response (if any), read from the generic node after executing
15a command. Hex reply bytes will be returned, *whether or not* they came from
16the 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 @@
1What: /sys/kernel/debug/nx-crypto/*
2Date: March 2012
3KernelVersion: 3.4
4Contact: Kent Yoder <key@linux.vnet.ibm.com>
5Description:
6
7 These debugfs interfaces are built by the nx-crypto driver, built in
8arch/powerpc/crypto/nx.
9
10Error Detection
11===============
12
13errors:
14- A u32 providing a total count of errors since the driver was loaded. The
15only errors counted here are those returned from the hcall, H_COP_OP.
16
17last_error:
18- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19recorded here (the hcall will retry until -EBUSY goes away).
20
21last_error_pid:
22- The process ID of the process who received the most recent error from the
23hcall.
24
25Device Use
26==========
27
28aes_bytes:
29- The total number of bytes encrypted using AES in any of the driver's
30supported modes.
31
32aes_ops:
33- The total number of AES operations submitted to the hardware.
34
35sha256_bytes:
36- The total number of bytes hashed by the hardware using SHA-256.
37
38sha256_ops:
39- The total number of SHA-256 operations submitted to the hardware.
40
41sha512_bytes:
42- The total number of bytes hashed by the hardware using SHA-512.
43
44sha512_ops:
45- The total number of SHA-512 operations submitted to the hardware.
diff --git a/Documentation/ABI/testing/dev-kmsg b/Documentation/ABI/testing/dev-kmsg
deleted file mode 100644
index bb820be4817..00000000000
--- a/Documentation/ABI/testing/dev-kmsg
+++ /dev/null
@@ -1,101 +0,0 @@
1What: /dev/kmsg
2Date: Mai 2012
3KernelVersion: 3.5
4Contact: Kay Sievers <kay@vrfy.org>
5Description: The /dev/kmsg character device node provides userspace access
6 to the kernel's printk buffer.
7
8 Injecting messages:
9 Every write() to the opened device node places a log entry in
10 the kernel's printk buffer.
11
12 The logged line can be prefixed with a <N> syslog prefix, which
13 carries the syslog priority and facility. The single decimal
14 prefix number is composed of the 3 lowest bits being the syslog
15 priority and the higher bits the syslog facility number.
16
17 If no prefix is given, the priority number is the default kernel
18 log priority and the facility number is set to LOG_USER (1). It
19 is not possible to inject messages from userspace with the
20 facility number LOG_KERN (0), to make sure that the origin of
21 the messages can always be reliably determined.
22
23 Accessing the buffer:
24 Every read() from the opened device node receives one record
25 of the kernel's printk buffer.
26
27 The first read() directly following an open() always returns
28 first message in the buffer; there is no kernel-internal
29 persistent state; many readers can concurrently open the device
30 and read from it, without affecting other readers.
31
32 Every read() will receive the next available record. If no more
33 records are available read() will block, or if O_NONBLOCK is
34 used -EAGAIN returned.
35
36 Messages in the record ring buffer get overwritten as whole,
37 there are never partial messages received by read().
38
39 In case messages get overwritten in the circular buffer while
40 the device is kept open, the next read() will return -EPIPE,
41 and the seek position be updated to the next available record.
42 Subsequent reads() will return available records again.
43
44 Unlike the classic syslog() interface, the 64 bit record
45 sequence numbers allow to calculate the amount of lost
46 messages, in case the buffer gets overwritten. And they allow
47 to reconnect to the buffer and reconstruct the read position
48 if needed, without limiting the interface to a single reader.
49
50 The device supports seek with the following parameters:
51 SEEK_SET, 0
52 seek to the first entry in the buffer
53 SEEK_END, 0
54 seek after the last entry in the buffer
55 SEEK_DATA, 0
56 seek after the last record available at the time
57 the last SYSLOG_ACTION_CLEAR was issued.
58
59 The output format consists of a prefix carrying the syslog
60 prefix including priority and facility, the 64 bit message
61 sequence number and the monotonic timestamp in microseconds,
62 and a flag field. All fields are separated by a ','.
63
64 Future extensions might add more comma separated values before
65 the terminating ';'. Unknown fields and values should be
66 gracefully ignored.
67
68 The human readable text string starts directly after the ';'
69 and is terminated by a '\n'. Untrusted values derived from
70 hardware or other facilities are printed, therefore
71 all non-printable characters and '\' itself in the log message
72 are escaped by "\x00" C-style hex encoding.
73
74 A line starting with ' ', is a continuation line, adding
75 key/value pairs to the log message, which provide the machine
76 readable context of the message, for reliable processing in
77 userspace.
78
79 Example:
80 7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
81 SUBSYSTEM=acpi
82 DEVICE=+acpi:PNP0A03:00
83 6,339,5140900,-;NET: Registered protocol family 10
84 30,340,5690716,-;udevd[80]: starting version 181
85
86 The DEVICE= key uniquely identifies devices the following way:
87 b12:8 - block dev_t
88 c127:3 - char dev_t
89 n8 - netdev ifindex
90 +sound:card0 - subsystem:devname
91
92 The flags field carries '-' by default. A 'c' indicates a
93 fragment of a line. All following fragments are flagged with
94 '+'. Note, that these hints about continuation lines are not
95 necessarily correct, and the stream could be interleaved with
96 unrelated messages, but merging the lines in the output
97 usually produces better human readable results. A similar
98 logic is used internally when messages are printed to the
99 console, /proc/kmsg or the syslog() syscall.
100
101Users: 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 @@
1What: security/evm
2Date: March 2011
3Contact: Mimi Zohar <zohar@us.ibm.com>
4Description:
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/ima_policy b/Documentation/ABI/testing/ima_policy
index ec0a38ef314..6cd6daefaae 100644
--- a/Documentation/ABI/testing/ima_policy
+++ b/Documentation/ABI/testing/ima_policy
@@ -12,66 +12,48 @@ Description:
12 then closing the file. The new policy takes effect after 12 then closing the file. The new policy takes effect after
13 the file ima/policy is closed. 13 the file ima/policy is closed.
14 14
15 IMA appraisal, if configured, uses these file measurements
16 for local measurement appraisal.
17
18 rule format: action [condition ...] 15 rule format: action [condition ...]
19 16
20 action: measure | dont_measure | appraise | dont_appraise | audit 17 action: measure | dont_measure
21 condition:= base | lsm 18 condition:= base | lsm
22 base: [[func=] [mask=] [fsmagic=] [uid=] [fowner]] 19 base: [[func=] [mask=] [fsmagic=] [uid=]]
23 lsm: [[subj_user=] [subj_role=] [subj_type=] 20 lsm: [[subj_user=] [subj_role=] [subj_type=]
24 [obj_user=] [obj_role=] [obj_type=]] 21 [obj_user=] [obj_role=] [obj_type=]]
25 22
26 base: func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK][MODULE_CHECK] 23 base: func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK]
27 mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] 24 mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC]
28 fsmagic:= hex value 25 fsmagic:= hex value
29 uid:= decimal value 26 uid:= decimal value
30 fowner:=decimal value
31 lsm: are LSM specific 27 lsm: are LSM specific
32 28
33 default policy: 29 default policy:
34 # PROC_SUPER_MAGIC 30 # PROC_SUPER_MAGIC
35 dont_measure fsmagic=0x9fa0 31 dont_measure fsmagic=0x9fa0
36 dont_appraise fsmagic=0x9fa0
37 # SYSFS_MAGIC 32 # SYSFS_MAGIC
38 dont_measure fsmagic=0x62656572 33 dont_measure fsmagic=0x62656572
39 dont_appraise fsmagic=0x62656572
40 # DEBUGFS_MAGIC 34 # DEBUGFS_MAGIC
41 dont_measure fsmagic=0x64626720 35 dont_measure fsmagic=0x64626720
42 dont_appraise fsmagic=0x64626720
43 # TMPFS_MAGIC 36 # TMPFS_MAGIC
44 dont_measure fsmagic=0x01021994 37 dont_measure fsmagic=0x01021994
45 dont_appraise fsmagic=0x01021994
46 # RAMFS_MAGIC
47 dont_measure fsmagic=0x858458f6
48 dont_appraise fsmagic=0x858458f6
49 # SECURITYFS_MAGIC 38 # SECURITYFS_MAGIC
50 dont_measure fsmagic=0x73636673 39 dont_measure fsmagic=0x73636673
51 dont_appraise fsmagic=0x73636673
52 40
53 measure func=BPRM_CHECK 41 measure func=BPRM_CHECK
54 measure func=FILE_MMAP mask=MAY_EXEC 42 measure func=FILE_MMAP mask=MAY_EXEC
55 measure func=FILE_CHECK mask=MAY_READ uid=0 43 measure func=FILE_CHECK mask=MAY_READ uid=0
56 measure func=MODULE_CHECK uid=0
57 appraise fowner=0
58 44
59 The default policy measures all executables in bprm_check, 45 The default policy measures all executables in bprm_check,
60 all files mmapped executable in file_mmap, and all files 46 all files mmapped executable in file_mmap, and all files
61 open for read by root in do_filp_open. The default appraisal 47 open for read by root in do_filp_open.
62 policy appraises all files owned by root.
63 48
64 Examples of LSM specific definitions: 49 Examples of LSM specific definitions:
65 50
66 SELinux: 51 SELinux:
67 # SELINUX_MAGIC 52 # SELINUX_MAGIC
68 dont_measure fsmagic=0xf97cff8c 53 dont_measure fsmagic=0xF97CFF8C
69 dont_appraise fsmagic=0xf97cff8c
70 54
71 dont_measure obj_type=var_log_t 55 dont_measure obj_type=var_log_t
72 dont_appraise obj_type=var_log_t
73 dont_measure obj_type=auditd_log_t 56 dont_measure obj_type=auditd_log_t
74 dont_appraise obj_type=auditd_log_t
75 measure subj_user=system_u func=FILE_CHECK mask=MAY_READ 57 measure subj_user=system_u func=FILE_CHECK mask=MAY_READ
76 measure subj_role=system_r func=FILE_CHECK mask=MAY_READ 58 measure subj_role=system_r func=FILE_CHECK mask=MAY_READ
77 59
diff --git a/Documentation/ABI/testing/sysfs-block b/Documentation/ABI/testing/sysfs-block
index 279da08f754..c1eb41cb987 100644
--- a/Documentation/ABI/testing/sysfs-block
+++ b/Documentation/ABI/testing/sysfs-block
@@ -206,17 +206,3 @@ 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
210What: /sys/block/<disk>/queue/write_same_max_bytes
211Date: January 2012
212Contact: Martin K. Petersen <martin.petersen@oracle.com>
213Description:
214 Some devices support a write same operation in which a
215 single data block can be written to a range of several
216 contiguous blocks on storage. This can be used to wipe
217 areas on disk or to initialize drives in a RAID
218 configuration. write_same_max_bytes indicates how many
219 bytes can be written in a single write same command. If
220 write_same_max_bytes is 0, write same is not supported
221 by the device.
222
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 @@
1What: /sys/block/dm-<num>/dm/name
2Date: January 2009
3KernelVersion: 2.6.29
4Contact: dm-devel@redhat.com
5Description: Device-mapper device name.
6 Read-only string containing mapped device name.
7Users: util-linux, device-mapper udev rules
8
9What: /sys/block/dm-<num>/dm/uuid
10Date: January 2009
11KernelVersion: 2.6.29
12Contact: dm-devel@redhat.com
13Description: Device-mapper device UUID.
14 Read-only string containing DM-UUID or empty string
15 if DM-UUID is not set.
16Users: util-linux, device-mapper udev rules
17
18What: /sys/block/dm-<num>/dm/suspended
19Date: June 2009
20KernelVersion: 2.6.31
21Contact: dm-devel@redhat.com
22Description: Device-mapper device suspend state.
23 Contains the value 1 while the device is suspended.
24 Otherwise it contains 0. Read-only attribute.
25Users: 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 @@
1What: /sys/block/rssd*/status
2Date: April 2012
3KernelVersion: 3.4
4Contact: Asai Thambi S P <asamymuthupa@micron.com>
5Description: 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
index ec93fe33baa..c8b3b48ec62 100644
--- a/Documentation/ABI/testing/sysfs-block-zram
+++ b/Documentation/ABI/testing/sysfs-block-zram
@@ -96,4 +96,4 @@ Description:
96 overhead, allocated for this disk. So, allocator space 96 overhead, allocated for this disk. So, allocator space
97 efficiency can be calculated using compr_data_size and this 97 efficiency can be calculated using compr_data_size and this
98 statistic. 98 statistic.
99 Unit: bytes 99 Unit: bytes \ No newline at end of file
diff --git a/Documentation/ABI/testing/sysfs-bus-bcma b/Documentation/ABI/testing/sysfs-bus-bcma
index 721b4aea302..06b62badddd 100644
--- a/Documentation/ABI/testing/sysfs-bus-bcma
+++ b/Documentation/ABI/testing/sysfs-bus-bcma
@@ -1,6 +1,6 @@
1What: /sys/bus/bcma/devices/.../manuf 1What: /sys/bus/bcma/devices/.../manuf
2Date: May 2011 2Date: May 2011
3KernelVersion: 3.0 3KernelVersion: 2.6.40
4Contact: Rafał Miłecki <zajec5@gmail.com> 4Contact: Rafał Miłecki <zajec5@gmail.com>
5Description: 5Description:
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
9What: /sys/bus/bcma/devices/.../id 9What: /sys/bus/bcma/devices/.../id
10Date: May 2011 10Date: May 2011
11KernelVersion: 3.0 11KernelVersion: 2.6.40
12Contact: Rafał Miłecki <zajec5@gmail.com> 12Contact: Rafał Miłecki <zajec5@gmail.com>
13Description: 13Description:
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
17What: /sys/bus/bcma/devices/.../rev 17What: /sys/bus/bcma/devices/.../rev
18Date: May 2011 18Date: May 2011
19KernelVersion: 3.0 19KernelVersion: 2.6.40
20Contact: Rafał Miłecki <zajec5@gmail.com> 20Contact: Rafał Miłecki <zajec5@gmail.com>
21Description: 21Description:
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
25What: /sys/bus/bcma/devices/.../class 25What: /sys/bus/bcma/devices/.../class
26Date: May 2011 26Date: May 2011
27KernelVersion: 3.0 27KernelVersion: 2.6.40
28Contact: Rafał Miłecki <zajec5@gmail.com> 28Contact: Rafał Miłecki <zajec5@gmail.com>
29Description: 29Description:
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-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 @@
1Where: /sys/bus/event_source/devices/<dev>/format
2Date: January 2012
3Kernel Version: 3.3
4Contact: Jiri Olsa <jolsa@redhat.com>
5Description:
6 Attribute group to describe the magic bits that go into
7 perf_event_attr::config[012] for a particular pmu.
8 Each attribute of this group defines the 'hardware' bitmask
9 we want to export, so that userspace can deal with sane
10 name/value pairs.
11
12 Example: 'config1:1,6-10,44'
13 Defines contents of attribute that occupies bits 1,6-10,44 of
14 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 50e2a80ea28..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-fcoe
+++ /dev/null
@@ -1,77 +0,0 @@
1What: /sys/bus/fcoe/ctlr_X
2Date: March 2012
3KernelVersion: TBD
4Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
5Description: 'FCoE Controller' instances on the fcoe bus
6Attributes:
7
8 fcf_dev_loss_tmo: Device loss timeout peroid (see below). Changing
9 this value will change the dev_loss_tmo for all
10 FCFs discovered by this controller.
11
12 lesb/link_fail: Link Error Status Block (LESB) link failure count.
13
14 lesb/vlink_fail: Link Error Status Block (LESB) virtual link
15 failure count.
16
17 lesb/miss_fka: Link Error Status Block (LESB) missed FCoE
18 Initialization Protocol (FIP) Keep-Alives (FKA).
19
20 lesb/symb_err: Link Error Status Block (LESB) symbolic error count.
21
22 lesb/err_block: Link Error Status Block (LESB) block error count.
23
24 lesb/fcs_error: Link Error Status Block (LESB) Fibre Channel
25 Serivces error count.
26
27Notes: ctlr_X (global increment starting at 0)
28
29What: /sys/bus/fcoe/fcf_X
30Date: March 2012
31KernelVersion: TBD
32Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
33Description: 'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel
34 Forwarder, which is a FCoE switch that can accept FCoE
35 (Ethernet) packets, unpack them, and forward the embedded
36 Fibre Channel frames into a FC fabric. It can also take
37 outbound FC frames and pack them in Ethernet packets to
38 be sent to their destination on the Ethernet segment.
39Attributes:
40
41 fabric_name: Identifies the fabric that the FCF services.
42
43 switch_name: Identifies the FCF.
44
45 priority: The switch's priority amongst other FCFs on the same
46 fabric.
47
48 selected: 1 indicates that the switch has been selected for use;
49 0 indicates that the swich will not be used.
50
51 fc_map: The Fibre Channel MAP
52
53 vfid: The Virtual Fabric ID
54
55 mac: The FCF's MAC address
56
57 fka_peroid: The FIP Keep-Alive peroid
58
59 fabric_state: The internal kernel state
60 "Unknown" - Initialization value
61 "Disconnected" - No link to the FCF/fabric
62 "Connected" - Host is connected to the FCF
63 "Deleted" - FCF is being removed from the system
64
65 dev_loss_tmo: The device loss timeout peroid for this FCF.
66
67Notes: A device loss infrastructre similar to the FC Transport's
68 is present in fcoe_sysfs. It is nice to have so that a
69 link flapping adapter doesn't continually advance the count
70 used to identify the discovered FCF. FCFs will exist in a
71 "Disconnected" state until either the timer expires and the
72 FCF becomes "Deleted" or the FCF is rediscovered and becomes
73 "Connected."
74
75
76Users: The first user of this interface will be the fcoeadm application,
77 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 @@
1What: /sys/bus/hsi
2Date: April 2012
3KernelVersion: 3.4
4Contact: Carlos Chinea <carlos.chinea@nokia.com>
5Description:
6 High Speed Synchronous Serial Interface (HSI) is a
7 serial interface mainly used for connecting application
8 engines (APE) with cellular modem engines (CMT) in cellular
9 handsets.
10 The bus will be populated with devices (hsi_clients) representing
11 the protocols available in the system. Bus drivers implement
12 those protocols.
13
14What: /sys/bus/hsi/devices/.../modalias
15Date: April 2012
16KernelVersion: 3.4
17Contact: Carlos Chinea <carlos.chinea@nokia.com>
18Description: Stores the same MODALIAS value emitted by uevent
19 Format: hsi:<hsi_client device name>
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 @@
1What: /sys/bus/i2c/devices/.../output_hvled[n]
2Date: April 2012
3KernelVersion: 3.5
4Contact: Johan Hovold <jhovold@gmail.com>
5Description:
6 Set the controlling backlight device for high-voltage current
7 sink HVLED[n] (n = 1, 2) (0, 1).
8
9What: /sys/bus/i2c/devices/.../output_lvled[n]
10Date: April 2012
11KernelVersion: 3.5
12Contact: Johan Hovold <jhovold@gmail.com>
13Description:
14 Set the controlling led device for low-voltage current sink
15 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 2e33dc6b234..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ /dev/null
@@ -1,794 +0,0 @@
1What: /sys/bus/iio/devices/iio:deviceX
2KernelVersion: 2.6.35
3Contact: linux-iio@vger.kernel.org
4Description:
5 Hardware chip or device accessed by one communication port.
6 Corresponds to a grouping of sensor channels. X is the IIO
7 index of the device.
8
9What: /sys/bus/iio/devices/triggerX
10KernelVersion: 2.6.35
11Contact: linux-iio@vger.kernel.org
12Description:
13 An event driven driver of data capture to an in kernel buffer.
14 May be provided by a device driver that also has an IIO device
15 based on hardware generated events (e.g. data ready) or
16 provided by a separate driver for other hardware (e.g.
17 periodic timer, GPIO or high resolution timer).
18 Contains trigger type specific elements. These do not
19 generalize well and hence are not documented in this file.
20 X is the IIO index of the trigger.
21
22What: /sys/bus/iio/devices/iio:deviceX/buffer
23KernelVersion: 2.6.35
24Contact: linux-iio@vger.kernel.org
25Description:
26 Directory of attributes relating to the buffer for the device.
27
28What: /sys/bus/iio/devices/iio:deviceX/name
29KernelVersion: 2.6.35
30Contact: linux-iio@vger.kernel.org
31Description:
32 Description of the physical chip / device for device X.
33 Typically a part number.
34
35What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency
36What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency
37What: /sys/bus/iio/devices/triggerX/sampling_frequency
38KernelVersion: 2.6.35
39Contact: linux-iio@vger.kernel.org
40Description:
41 Some devices have internal clocks. This parameter sets the
42 resulting sampling frequency. In many devices this
43 parameter has an effect on input filters etc. rather than
44 simply controlling when the input is sampled. As this
45 effects data ready triggers, hardware buffers and the sysfs
46 direct access interfaces, it may be found in any of the
47 relevant directories. If it effects all of the above
48 then it is to be found in the base device directory.
49
50What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available
51What: /sys/.../iio:deviceX/buffer/sampling_frequency_available
52What: /sys/bus/iio/devices/triggerX/sampling_frequency_available
53KernelVersion: 2.6.35
54Contact: linux-iio@vger.kernel.org
55Description:
56 When the internal sampling clock can only take a small
57 discrete set of values, this file lists those available.
58
59What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio
60KernelVersion: 2.6.38
61Contact: linux-iio@vger.kernel.org
62Description:
63 Hardware dependent ADC oversampling. Controls the sampling ratio
64 of the digital filter if available.
65
66What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available
67KernelVersion: 2.6.38
68Contact: linux-iio@vger.kernel.org
69Description:
70 Hardware dependent values supported by the oversampling filter.
71
72What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw
73What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
74KernelVersion: 2.6.35
75Contact: linux-iio@vger.kernel.org
76Description:
77 Raw (unscaled no bias removal etc.) voltage measurement from
78 channel Y. In special cases where the channel does not
79 correspond to externally available input one of the named
80 versions may be used. The number must always be specified and
81 unique to allow association with event codes. Units after
82 application of scale and offset are microvolts.
83
84What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
85KernelVersion: 2.6.35
86Contact: linux-iio@vger.kernel.org
87Description:
88 Raw (unscaled) differential voltage measurement equivalent to
89 channel Y - channel Z where these channel numbers apply to the
90 physically equivalent inputs when non differential readings are
91 separately available. In differential only parts, then all that
92 is required is a consistent labeling. Units after application
93 of scale and offset are microvolts.
94
95What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw
96KernelVersion: 3.2
97Contact: linux-iio@vger.kernel.org
98Description:
99 Raw capacitance measurement from channel Y. Units after
100 application of scale and offset are nanofarads.
101
102What: /sys/.../iio:deviceX/in_capacitanceY-in_capacitanceZ_raw
103KernelVersion: 3.2
104Contact: linux-iio@vger.kernel.org
105Description:
106 Raw differential capacitance measurement equivalent to
107 channel Y - channel Z where these channel numbers apply to the
108 physically equivalent inputs when non differential readings are
109 separately available. In differential only parts, then all that
110 is required is a consistent labeling. Units after application
111 of scale and offset are nanofarads.
112
113What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw
114What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw
115What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw
116What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw
117What: /sys/bus/iio/devices/iio:deviceX/in_temp_z_raw
118KernelVersion: 2.6.35
119Contact: linux-iio@vger.kernel.org
120Description:
121 Raw (unscaled no bias removal etc.) temperature measurement.
122 If an axis is specified it generally means that the temperature
123 sensor is associated with one part of a compound device (e.g.
124 a gyroscope axis). Units after application of scale and offset
125 are milli degrees Celsius.
126
127What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
128KernelVersion: 2.6.38
129Contact: linux-iio@vger.kernel.org
130Description:
131 Scaled temperature measurement in milli degrees Celsius.
132
133What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw
134What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_raw
135What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_raw
136KernelVersion: 2.6.35
137Contact: linux-iio@vger.kernel.org
138Description:
139 Acceleration in direction x, y or z (may be arbitrarily assigned
140 but should match other such assignments on device).
141 Has all of the equivalent parameters as per voltageY. Units
142 after application of scale and offset are m/s^2.
143
144What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_raw
145What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_raw
146What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_raw
147KernelVersion: 2.6.35
148Contact: linux-iio@vger.kernel.org
149Description:
150 Angular velocity about axis x, y or z (may be arbitrarily
151 assigned). Has all the equivalent parameters as per voltageY.
152 Units after application of scale and offset are radians per
153 second.
154
155What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
156What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
157What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw
158KernelVersion: 2.6.35
159Contact: linux-iio@vger.kernel.org
160Description:
161 Inclination raw reading about axis x, y or z (may be
162 arbitrarily assigned). Data converted by application of offset
163 and scale to degrees.
164
165What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
166What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
167What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw
168KernelVersion: 2.6.35
169Contact: linux-iio@vger.kernel.org
170Description:
171 Magnetic field along axis x, y or z (may be arbitrarily
172 assigned). Data converted by application of offset
173 then scale to Gauss.
174
175What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw
176What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw
177What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw
178KernelVersion: 2.6.36
179Contact: linux-iio@vger.kernel.org
180Description:
181 Highest value since some reset condition. These
182 attributes allow access to this and are otherwise
183 the direct equivalent of the <type>Y[_name]_raw attributes.
184
185What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw
186KernelVersion: 2.6.36
187Contact: linux-iio@vger.kernel.org
188Description:
189 A computed peak value based on the sum squared magnitude of
190 the underlying value in the specified directions.
191
192What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_raw
193What: /sys/bus/iio/devices/iio:deviceX/in_pressure_raw
194KernelVersion: 3.8
195Contact: linux-iio@vger.kernel.org
196Description:
197 Raw pressure measurement from channel Y. Units after
198 application of scale and offset are kilopascal.
199
200What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
201What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
202What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
203What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
204What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
205What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
206What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
207What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
208What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
209What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset
210KernelVersion: 2.6.35
211Contact: linux-iio@vger.kernel.org
212Description:
213 If known for a device, offset to be added to <type>[Y]_raw prior
214 to scaling by <type>[Y]_scale in order to obtain value in the
215 <type> units as specified in <type>[Y]_raw documentation.
216 Not present if the offset is always 0 or unknown. If Y or
217 axis <x|y|z> is not present, then the offset applies to all
218 in channels of <type>.
219 May be writable if a variable offset can be applied on the
220 device. Note that this is different to calibbias which
221 is for devices (or drivers) that apply offsets to compensate
222 for variation between different instances of the part, typically
223 adjusted by using some hardware supported calibration procedure.
224 Calibbias is applied internally, offset is applied in userspace
225 to the _raw output.
226
227What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
228What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
229What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
230What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
231What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
232What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
233What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
234What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
235What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
236What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
237What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
238What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale
239What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
240What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
241KernelVersion: 2.6.35
242Contact: linux-iio@vger.kernel.org
243Description:
244 If known for a device, scale to be applied to <type>Y[_name]_raw
245 post addition of <type>[Y][_name]_offset in order to obtain the
246 measured value in <type> units as specified in
247 <type>[Y][_name]_raw documentation. If shared across all in
248 channels then Y and <x|y|z> are not present and the value is
249 called <type>[Y][_name]_scale. The peak modifier means this
250 value is applied to <type>Y[_name]_peak_raw values.
251
252What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias
253What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias
254What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias
255What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias
256What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias
257What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias
258What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias
259What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
260What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibbias
261What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibbias
262KernelVersion: 2.6.35
263Contact: linux-iio@vger.kernel.org
264Description:
265 Hardware applied calibration offset (assumed to fix production
266 inaccuracies).
267
268What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
269What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
270What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
271What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
272What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
273What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
274What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
275What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
276What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
277what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
278what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
279What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale
280What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale
281KernelVersion: 2.6.35
282Contact: linux-iio@vger.kernel.org
283Description:
284 Hardware applied calibration scale factor (assumed to fix
285 production inaccuracies). If shared across all channels,
286 <type>_calibscale is used.
287
288What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
289What: /sys/.../iio:deviceX/in_voltageX_scale_available
290What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
291What: /sys/.../iio:deviceX/out_voltageX_scale_available
292What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
293What: /sys/.../iio:deviceX/in_capacitance_scale_available
294What: /sys/.../iio:deviceX/in_pressure_scale_available
295What: /sys/.../iio:deviceX/in_pressureY_scale_available
296KernelVersion: 2.6.35
297Contact: linux-iio@vger.kernel.org
298Description:
299 If a discrete set of scale values is available, they
300 are listed in this attribute.
301
302What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
303KernelVersion: 2.6.35
304Contact: linux-iio@vger.kernel.org
305Description:
306 Hardware applied gain factor. If shared across all channels,
307 <type>_hardwaregain is used.
308
309What: /sys/.../in_accel_filter_low_pass_3db_frequency
310What: /sys/.../in_magn_filter_low_pass_3db_frequency
311What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
312KernelVersion: 3.2
313Contact: linux-iio@vger.kernel.org
314Description:
315 If a known or controllable low pass filter is applied
316 to the underlying data channel, then this parameter
317 gives the 3dB frequency of the filter in Hz.
318
319What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
320What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
321KernelVersion: 2.6.37
322Contact: linux-iio@vger.kernel.org
323Description:
324 Raw (unscaled, no bias etc.) output voltage for
325 channel Y. The number must always be specified and
326 unique if the output corresponds to a single channel.
327 While DAC like devices typically use out_voltage,
328 a continuous frequency generating device, such as
329 a DDS or PLL should use out_altvoltage.
330
331What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
332What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw
333KernelVersion: 2.6.37
334Contact: linux-iio@vger.kernel.org
335Description:
336 Raw (unscaled, no bias etc.) output voltage for an aggregate of
337 channel Y, channel Z, etc. This interface is available in cases
338 where a single output sets the value for multiple channels
339 simultaneously.
340
341What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
342What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
343What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode
344What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode
345KernelVersion: 2.6.38
346Contact: linux-iio@vger.kernel.org
347Description:
348 Specifies the output powerdown mode.
349 DAC output stage is disconnected from the amplifier and
350 1kohm_to_gnd: connected to ground via an 1kOhm resistor,
351 6kohm_to_gnd: connected to ground via a 6kOhm resistor,
352 20kohm_to_gnd: connected to ground via a 20kOhm resistor,
353 100kohm_to_gnd: connected to ground via an 100kOhm resistor,
354 three_state: left floating.
355 For a list of available output power down options read
356 outX_powerdown_mode_available. If Y is not present the
357 mode is shared across all outputs.
358
359What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
360What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
361What: /sys/.../iio:deviceX/out_altvotlageY_powerdown_mode_available
362What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available
363KernelVersion: 2.6.38
364Contact: linux-iio@vger.kernel.org
365Description:
366 Lists all available output power down modes.
367 If Y is not present the mode is shared across all outputs.
368
369What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
370What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
371What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
372What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown
373KernelVersion: 2.6.38
374Contact: linux-iio@vger.kernel.org
375Description:
376 Writing 1 causes output Y to enter the power down mode specified
377 by the corresponding outY_powerdown_mode. DAC output stage is
378 disconnected from the amplifier. Clearing returns to normal
379 operation. Y may be suppressed if all outputs are controlled
380 together.
381
382What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
383KernelVersion: 3.4.0
384Contact: linux-iio@vger.kernel.org
385Description:
386 Output frequency for channel Y in Hz. The number must always be
387 specified and unique if the output corresponds to a single
388 channel.
389
390What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase
391KernelVersion: 3.4.0
392Contact: linux-iio@vger.kernel.org
393Description:
394 Phase in radians of one frequency/clock output Y
395 (out_altvoltageY) relative to another frequency/clock output
396 (out_altvoltageZ) of the device X. The number must always be
397 specified and unique if the output corresponds to a single
398 channel.
399
400What: /sys/bus/iio/devices/iio:deviceX/events
401KernelVersion: 2.6.35
402Contact: linux-iio@vger.kernel.org
403Description:
404 Configuration of which hardware generated events are passed up
405 to user-space.
406
407What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
408What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
409What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
410What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
411What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
412What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
413What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
414What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
415What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
416What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
417What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
418What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
419What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
420What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
421What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
422What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
423What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
424What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
425What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
426What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
427What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
428What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
429What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
430What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
431KernelVersion: 2.6.37
432Contact: linux-iio@vger.kernel.org
433Description:
434 Event generated when channel passes a threshold in the specified
435 (_rising|_falling) direction. If the direction is not specified,
436 then either the device will report an event which ever direction
437 a single threshold value is passed in (e.g.
438 <type>[Y][_name]_<raw|input>_thresh_value) or
439 <type>[Y][_name]_<raw|input>_thresh_rising_value and
440 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
441 different values, but the device can only enable both thresholds
442 or neither.
443 Note the driver will assume the last p events requested are
444 to be enabled where p is how many it supports (which may vary
445 depending on the exact set requested. So if you want to be
446 sure you have set what you think you have, check the contents of
447 these attributes after everything is configured. Drivers may
448 have to buffer any parameters so that they are consistent when
449 a given event type is enabled at a future point (and not those for
450 whatever event was previously enabled).
451
452What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
453What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
454What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
455What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
456What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
457What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
458What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
459What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
460What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
461What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
462What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
463What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
464What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
465What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
466What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
467What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
468What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
469What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
470What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
471What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
472What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
473What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
474What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
475What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
476KernelVersion: 2.6.37
477Contact: linux-iio@vger.kernel.org
478Description:
479 Event generated when channel passes a threshold on the rate of
480 change (1st differential) in the specified (_rising|_falling)
481 direction. If the direction is not specified, then either the
482 device will report an event which ever direction a single
483 threshold value is passed in (e.g.
484 <type>[Y][_name]_<raw|input>_roc_value) or
485 <type>[Y][_name]_<raw|input>_roc_rising_value and
486 <type>[Y][_name]_<raw|input>_roc_falling_value may take
487 different values, but the device can only enable both rate of
488 change thresholds or neither.
489 Note the driver will assume the last p events requested are
490 to be enabled where p is however many it supports (which may
491 vary depending on the exact set requested. So if you want to be
492 sure you have set what you think you have, check the contents of
493 these attributes after everything is configured. Drivers may
494 have to buffer any parameters so that they are consistent when
495 a given event type is enabled a future point (and not those for
496 whatever event was previously enabled).
497
498What: /sys/.../events/in_accel_x_raw_thresh_rising_value
499What: /sys/.../events/in_accel_x_raw_thresh_falling_value
500What: /sys/.../events/in_accel_y_raw_thresh_rising_value
501What: /sys/.../events/in_accel_y_raw_thresh_falling_value
502What: /sys/.../events/in_accel_z_raw_thresh_rising_value
503What: /sys/.../events/in_accel_z_raw_thresh_falling_value
504What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
505What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
506What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
507What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
508What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
509What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
510What: /sys/.../events/in_magn_x_raw_thresh_rising_value
511What: /sys/.../events/in_magn_x_raw_thresh_falling_value
512What: /sys/.../events/in_magn_y_raw_thresh_rising_value
513What: /sys/.../events/in_magn_y_raw_thresh_falling_value
514What: /sys/.../events/in_magn_z_raw_thresh_rising_value
515What: /sys/.../events/in_magn_z_raw_thresh_falling_value
516What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
517What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
518What: /sys/.../events/in_voltageY_raw_thresh_rising_value
519What: /sys/.../events/in_voltageY_raw_thresh_falling_value
520What: /sys/.../events/in_tempY_raw_thresh_rising_value
521What: /sys/.../events/in_tempY_raw_thresh_falling_value
522What: /sys/.../events/in_illuminance0_thresh_falling_value
523what: /sys/.../events/in_illuminance0_thresh_rising_value
524what: /sys/.../events/in_proximity0_thresh_falling_value
525what: /sys/.../events/in_proximity0_thresh_rising_value
526KernelVersion: 2.6.37
527Contact: linux-iio@vger.kernel.org
528Description:
529 Specifies the value of threshold that the device is comparing
530 against for the events enabled by
531 <type>Y[_name]_thresh[_rising|falling]_en.
532 If separate attributes exist for the two directions, but
533 direction is not specified for this attribute, then a single
534 threshold value applies to both directions.
535 The raw or input element of the name indicates whether the
536 value is in raw device units or in processed units (as _raw
537 and _input do on sysfs direct channel read attributes).
538
539What: /sys/.../events/in_accel_x_raw_roc_rising_value
540What: /sys/.../events/in_accel_x_raw_roc_falling_value
541What: /sys/.../events/in_accel_y_raw_roc_rising_value
542What: /sys/.../events/in_accel_y_raw_roc_falling_value
543What: /sys/.../events/in_accel_z_raw_roc_rising_value
544What: /sys/.../events/in_accel_z_raw_roc_falling_value
545What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
546What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
547What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
548What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
549What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
550What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
551What: /sys/.../events/in_magn_x_raw_roc_rising_value
552What: /sys/.../events/in_magn_x_raw_roc_falling_value
553What: /sys/.../events/in_magn_y_raw_roc_rising_value
554What: /sys/.../events/in_magn_y_raw_roc_falling_value
555What: /sys/.../events/in_magn_z_raw_roc_rising_value
556What: /sys/.../events/in_magn_z_raw_roc_falling_value
557What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
558What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
559What: /sys/.../events/in_voltageY_raw_roc_rising_value
560What: /sys/.../events/in_voltageY_raw_roc_falling_value
561What: /sys/.../events/in_tempY_raw_roc_rising_value
562What: /sys/.../events/in_tempY_raw_roc_falling_value
563KernelVersion: 2.6.37
564Contact: linux-iio@vger.kernel.org
565Description:
566 Specifies the value of rate of change threshold that the
567 device is comparing against for the events enabled by
568 <type>[Y][_name]_roc[_rising|falling]_en.
569 If separate attributes exist for the two directions,
570 but direction is not specified for this attribute,
571 then a single threshold value applies to both directions.
572 The raw or input element of the name indicates whether the
573 value is in raw device units or in processed units (as _raw
574 and _input do on sysfs direct channel read attributes).
575
576What: /sys/.../events/in_accel_x_thresh_rising_period
577What: /sys/.../events/in_accel_x_thresh_falling_period
578hat: /sys/.../events/in_accel_x_roc_rising_period
579What: /sys/.../events/in_accel_x_roc_falling_period
580What: /sys/.../events/in_accel_y_thresh_rising_period
581What: /sys/.../events/in_accel_y_thresh_falling_period
582What: /sys/.../events/in_accel_y_roc_rising_period
583What: /sys/.../events/in_accel_y_roc_falling_period
584What: /sys/.../events/in_accel_z_thresh_rising_period
585What: /sys/.../events/in_accel_z_thresh_falling_period
586What: /sys/.../events/in_accel_z_roc_rising_period
587What: /sys/.../events/in_accel_z_roc_falling_period
588What: /sys/.../events/in_anglvel_x_thresh_rising_period
589What: /sys/.../events/in_anglvel_x_thresh_falling_period
590What: /sys/.../events/in_anglvel_x_roc_rising_period
591What: /sys/.../events/in_anglvel_x_roc_falling_period
592What: /sys/.../events/in_anglvel_y_thresh_rising_period
593What: /sys/.../events/in_anglvel_y_thresh_falling_period
594What: /sys/.../events/in_anglvel_y_roc_rising_period
595What: /sys/.../events/in_anglvel_y_roc_falling_period
596What: /sys/.../events/in_anglvel_z_thresh_rising_period
597What: /sys/.../events/in_anglvel_z_thresh_falling_period
598What: /sys/.../events/in_anglvel_z_roc_rising_period
599What: /sys/.../events/in_anglvel_z_roc_falling_period
600What: /sys/.../events/in_magn_x_thresh_rising_period
601What: /sys/.../events/in_magn_x_thresh_falling_period
602What: /sys/.../events/in_magn_x_roc_rising_period
603What: /sys/.../events/in_magn_x_roc_falling_period
604What: /sys/.../events/in_magn_y_thresh_rising_period
605What: /sys/.../events/in_magn_y_thresh_falling_period
606What: /sys/.../events/in_magn_y_roc_rising_period
607What: /sys/.../events/in_magn_y_roc_falling_period
608What: /sys/.../events/in_magn_z_thresh_rising_period
609What: /sys/.../events/in_magn_z_thresh_falling_period
610What: /sys/.../events/in_magn_z_roc_rising_period
611What: /sys/.../events/in_magn_z_roc_falling_period
612What: /sys/.../events/in_voltageY_supply_thresh_rising_period
613What: /sys/.../events/in_voltageY_supply_thresh_falling_period
614What: /sys/.../events/in_voltageY_supply_roc_rising_period
615What: /sys/.../events/in_voltageY_supply_roc_falling_period
616What: /sys/.../events/in_voltageY_thresh_rising_period
617What: /sys/.../events/in_voltageY_thresh_falling_period
618What: /sys/.../events/in_voltageY_roc_rising_period
619What: /sys/.../events/in_voltageY_roc_falling_period
620What: /sys/.../events/in_tempY_thresh_rising_period
621What: /sys/.../events/in_tempY_thresh_falling_period
622What: /sys/.../events/in_tempY_roc_rising_period
623What: /sys/.../events/in_tempY_roc_falling_period
624What: /sys/.../events/in_accel_x&y&z_mag_falling_period
625What: /sys/.../events/in_intensity0_thresh_period
626What: /sys/.../events/in_proximity0_thresh_period
627KernelVersion: 2.6.37
628Contact: linux-iio@vger.kernel.org
629Description:
630 Period of time (in seconds) for which the condition must be
631 met before an event is generated. If direction is not
632 specified then this period applies to both directions.
633
634What: /sys/.../iio:deviceX/events/in_accel_mag_en
635What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
636What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
637What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
638What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
639What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
640What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
641What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
642What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
643What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
644What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
645What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
646What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
647What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
648KernelVersion: 2.6.37
649Contact: linux-iio@vger.kernel.org
650Description:
651 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
652 magnitude of the channel is compared to the threshold, not its
653 signed value.
654
655What: /sys/.../events/in_accel_raw_mag_value
656What: /sys/.../events/in_accel_x_raw_mag_rising_value
657What: /sys/.../events/in_accel_y_raw_mag_rising_value
658What: /sys/.../events/in_accel_z_raw_mag_rising_value
659KernelVersion: 2.6.37
660Contact: linux-iio@vger.kernel.org
661Description:
662 The value to which the magnitude of the channel is compared. If
663 number or direction is not specified, applies to all channels of
664 this type.
665
666What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
667KernelVersion: 2.6.35
668Contact: linux-iio@vger.kernel.org
669Description:
670 The name of the trigger source being used, as per string given
671 in /sys/class/iio/triggerY/name.
672
673What: /sys/bus/iio/devices/iio:deviceX/buffer/length
674KernelVersion: 2.6.35
675Contact: linux-iio@vger.kernel.org
676Description:
677 Number of scans contained by the buffer.
678
679What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum
680KernelVersion: 2.6.37
681Contact: linux-iio@vger.kernel.org
682Description:
683 Bytes per scan. Due to alignment fun, the scan may be larger
684 than implied directly by the scan_element parameters.
685
686What: /sys/bus/iio/devices/iio:deviceX/buffer/enable
687KernelVersion: 2.6.35
688Contact: linux-iio@vger.kernel.org
689Description:
690 Actually start the buffer capture up. Will start trigger
691 if first device and appropriate.
692
693What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements
694KernelVersion: 2.6.37
695Contact: linux-iio@vger.kernel.org
696Description:
697 Directory containing interfaces for elements that will be
698 captured for a single triggered sample set in the buffer.
699
700What: /sys/.../buffer/scan_elements/in_accel_x_en
701What: /sys/.../buffer/scan_elements/in_accel_y_en
702What: /sys/.../buffer/scan_elements/in_accel_z_en
703What: /sys/.../buffer/scan_elements/in_anglvel_x_en
704What: /sys/.../buffer/scan_elements/in_anglvel_y_en
705What: /sys/.../buffer/scan_elements/in_anglvel_z_en
706What: /sys/.../buffer/scan_elements/in_magn_x_en
707What: /sys/.../buffer/scan_elements/in_magn_y_en
708What: /sys/.../buffer/scan_elements/in_magn_z_en
709What: /sys/.../buffer/scan_elements/in_timestamp_en
710What: /sys/.../buffer/scan_elements/in_voltageY_supply_en
711What: /sys/.../buffer/scan_elements/in_voltageY_en
712What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en
713What: /sys/.../buffer/scan_elements/in_incli_x_en
714What: /sys/.../buffer/scan_elements/in_incli_y_en
715What: /sys/.../buffer/scan_elements/in_pressureY_en
716What: /sys/.../buffer/scan_elements/in_pressure_en
717KernelVersion: 2.6.37
718Contact: linux-iio@vger.kernel.org
719Description:
720 Scan element control for triggered data capture.
721
722What: /sys/.../buffer/scan_elements/in_accel_type
723What: /sys/.../buffer/scan_elements/in_anglvel_type
724What: /sys/.../buffer/scan_elements/in_magn_type
725What: /sys/.../buffer/scan_elements/in_incli_type
726What: /sys/.../buffer/scan_elements/in_voltageY_type
727What: /sys/.../buffer/scan_elements/in_voltage_type
728What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
729What: /sys/.../buffer/scan_elements/in_timestamp_type
730What: /sys/.../buffer/scan_elements/in_pressureY_type
731What: /sys/.../buffer/scan_elements/in_pressure_type
732KernelVersion: 2.6.37
733Contact: linux-iio@vger.kernel.org
734Description:
735 Description of the scan element data storage within the buffer
736 and hence the form in which it is read from user-space.
737 Form is [be|le]:[s|u]bits/storagebits[>>shift].
738 be or le specifies big or little endian. s or u specifies if
739 signed (2's complement) or unsigned. bits is the number of bits
740 of data and storagebits is the space (after padding) that it
741 occupies in the buffer. shift if specified, is the shift that
742 needs to be applied prior to masking out unused bits. Some
743 devices put their data in the middle of the transferred elements
744 with additional information on both sides. Note that some
745 devices will have additional information in the unused bits
746 so to get a clean value, the bits value must be used to mask
747 the buffer output value appropriately. The storagebits value
748 also specifies the data alignment. So s48/64>>2 will be a
749 signed 48 bit integer stored in a 64 bit location aligned to
750 a 64 bit boundary. To obtain the clean value, shift right 2
751 and apply a mask to zero the top 16 bits of the result.
752 For other storage combinations this attribute will be extended
753 appropriately.
754
755What: /sys/.../buffer/scan_elements/in_accel_type_available
756KernelVersion: 2.6.37
757Contact: linux-iio@vger.kernel.org
758Description:
759 If the type parameter can take one of a small set of values,
760 this attribute lists them.
761
762What: /sys/.../buffer/scan_elements/in_voltageY_index
763What: /sys/.../buffer/scan_elements/in_voltageY_supply_index
764What: /sys/.../buffer/scan_elements/in_accel_x_index
765What: /sys/.../buffer/scan_elements/in_accel_y_index
766What: /sys/.../buffer/scan_elements/in_accel_z_index
767What: /sys/.../buffer/scan_elements/in_anglvel_x_index
768What: /sys/.../buffer/scan_elements/in_anglvel_y_index
769What: /sys/.../buffer/scan_elements/in_anglvel_z_index
770What: /sys/.../buffer/scan_elements/in_magn_x_index
771What: /sys/.../buffer/scan_elements/in_magn_y_index
772What: /sys/.../buffer/scan_elements/in_magn_z_index
773What: /sys/.../buffer/scan_elements/in_incli_x_index
774What: /sys/.../buffer/scan_elements/in_incli_y_index
775What: /sys/.../buffer/scan_elements/in_timestamp_index
776What: /sys/.../buffer/scan_elements/in_pressureY_index
777What: /sys/.../buffer/scan_elements/in_pressure_index
778KernelVersion: 2.6.37
779Contact: linux-iio@vger.kernel.org
780Description:
781 A single positive integer specifying the position of this
782 scan element in the buffer. Note these are not dependent on
783 what is enabled and may not be contiguous. Thus for user-space
784 to establish the full layout these must be used in conjunction
785 with all _en attributes to establish which channels are present,
786 and the relevant _type attributes to establish the data storage
787 format.
788
789What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
790KernelVersion: 2.6.38
791Contact: linux-iio@vger.kernel.org
792Description:
793 This attribute is used to read the amount of quadrature error
794 present in the device at a given time.
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
deleted file mode 100644
index 2ce9c3f68ee..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
+++ /dev/null
@@ -1,37 +0,0 @@
1What: /sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present
2What: /sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present
3What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present
4What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present
5What: /sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present
6What: /sys/bus/iio/devices/iio:deviceX/vcxo_clk_present
7KernelVersion: 3.4.0
8Contact: linux-iio@vger.kernel.org
9Description:
10 Reading returns either '1' or '0'.
11 '1' means that the clock in question is present.
12 '0' means that the clock is missing.
13
14What: /sys/bus/iio/devices/iio:deviceX/pllY_locked
15KernelVersion: 3.4.0
16Contact: linux-iio@vger.kernel.org
17Description:
18 Reading returns either '1' or '0'. '1' means that the
19 pllY is locked.
20
21What: /sys/bus/iio/devices/iio:deviceX/store_eeprom
22KernelVersion: 3.4.0
23Contact: linux-iio@vger.kernel.org
24Description:
25 Writing '1' stores the current device configuration into
26 on-chip EEPROM. After power-up or chip reset the device will
27 automatically load the saved configuration.
28
29What: /sys/bus/iio/devices/iio:deviceX/sync_dividers
30KernelVersion: 3.4.0
31Contact: linux-iio@vger.kernel.org
32Description:
33 Writing '1' triggers the clock distribution synchronization
34 functionality. All dividers are reset and the channels start
35 with their predefined phase offsets (out_altvoltageY_phase).
36 Writing this file has the effect as driving the external
37 /SYNC pin low.
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
deleted file mode 100644
index d89aded01c5..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
+++ /dev/null
@@ -1,21 +0,0 @@
1What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution
2KernelVersion: 3.4.0
3Contact: linux-iio@vger.kernel.org
4Description:
5 Stores channel Y frequency resolution/channel spacing in Hz.
6 The value given directly influences the MODULUS used by
7 the fractional-N PLL. It is assumed that the algorithm
8 that is used to compute the various dividers, is able to
9 generate proper values for multiples of channel spacing.
10
11What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency
12KernelVersion: 3.4.0
13Contact: linux-iio@vger.kernel.org
14Description:
15 Sets channel Y REFin frequency in Hz. In some clock chained
16 applications, the reference frequency used by the PLL may
17 change during runtime. This attribute allows the user to
18 adjust the reference frequency accordingly.
19 The value written has no effect until out_altvoltageY_frequency
20 is updated. Consider to use out_altvoltageY_powerdown to power
21 down the PLL and it's RFOut buffers during REFin changes.
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
deleted file mode 100644
index 22c5ea67097..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
+++ /dev/null
@@ -1,61 +0,0 @@
1What: /sys/.../events/in_illuminance0_thresh_either_en
2Date: April 2012
3KernelVersion: 3.5
4Contact: Johan Hovold <jhovold@gmail.com>
5Description:
6 Event generated when channel passes one of the four thresholds
7 in each direction (rising|falling) and a zone change occurs.
8 The corresponding light zone can be read from
9 in_illuminance0_zone.
10
11What: /sys/.../events/in_illuminance0_threshY_hysteresis
12Date: May 2012
13KernelVersion: 3.5
14Contact: Johan Hovold <jhovold@gmail.com>
15Description:
16 Get the hysteresis for thresholds Y, that is,
17 threshY_hysteresis = threshY_raising - threshY_falling
18
19What: /sys/.../events/illuminance_threshY_falling_value
20What: /sys/.../events/illuminance_threshY_raising_value
21Date: April 2012
22KernelVersion: 3.5
23Contact: Johan Hovold <jhovold@gmail.com>
24Description:
25 Specifies the value of threshold that the device is comparing
26 against for the events enabled by
27 in_illuminance0_thresh_either_en (0..255), where Y in 0..3.
28
29 Note that threshY_falling must be less than or equal to
30 threshY_raising.
31
32 These thresholds correspond to the eight zone-boundary
33 registers (boundaryY_{low,high}) and define the five light
34 zones.
35
36What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone
37Date: April 2012
38KernelVersion: 3.5
39Contact: Johan Hovold <jhovold@gmail.com>
40Description:
41 Get the current light zone (0..4) as defined by the
42 in_illuminance0_threshY_{falling,rising} thresholds.
43
44What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw
45Date: May 2012
46KernelVersion: 3.5
47Contact: Johan Hovold <jhovold@gmail.com>
48Description:
49 Get output current for channel Y (0..255), that is,
50 out_currentY_currentZ_raw, where Z is the current zone.
51
52What: /sys/bus/iio/devices/iio:deviceX/out_currentY_currentZ_raw
53Date: May 2012
54KernelVersion: 3.5
55Contact: Johan Hovold <jhovold@gmail.com>
56Description:
57 Set the output current for channel out_currentY when in zone
58 Z (0..255), where Y in 0..2 and Z in 0..4.
59
60 These values correspond to the ALS-mapper target registers for
61 ALS-mapper Y + 1.
diff --git a/Documentation/ABI/testing/sysfs-bus-mdio b/Documentation/ABI/testing/sysfs-bus-mdio
deleted file mode 100644
index 6349749ebc2..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-mdio
+++ /dev/null
@@ -1,9 +0,0 @@
1What: /sys/bus/mdio_bus/devices/.../phy_id
2Date: November 2012
3KernelVersion: 3.8
4Contact: netdev@vger.kernel.org
5Description:
6 This attribute contains the 32-bit PHY Identifier as reported
7 by the device during bus enumeration, encoded in hexadecimal.
8 This ID is used to match the device with the appropriate
9 driver.
diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
index 1ce5ae329c0..349ecf26ce1 100644
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@@ -66,24 +66,6 @@ Description:
66 re-discover previously removed devices. 66 re-discover previously removed devices.
67 Depends on CONFIG_HOTPLUG. 67 Depends on CONFIG_HOTPLUG.
68 68
69What: /sys/bus/pci/devices/.../msi_irqs/
70Date: September, 2011
71Contact: Neil Horman <nhorman@tuxdriver.com>
72Description:
73 The /sys/devices/.../msi_irqs directory contains a variable set
74 of sub-directories, with each sub-directory being named after a
75 corresponding msi irq vector allocated to that device. Each
76 numbered sub-directory N contains attributes of that irq.
77 Note that this directory is not created for device drivers which
78 do not support msi irqs
79
80What: /sys/bus/pci/devices/.../msi_irqs/<N>/mode
81Date: September 2011
82Contact: Neil Horman <nhorman@tuxdriver.com>
83Description:
84 This attribute indicates the mode that the irq vector named by
85 the parent directory is in (msi vs. msix)
86
87What: /sys/bus/pci/devices/.../remove 69What: /sys/bus/pci/devices/.../remove
88Date: January 2009 70Date: January 2009
89Contact: Linux PCI developers <linux-pci@vger.kernel.org> 71Contact: Linux PCI developers <linux-pci@vger.kernel.org>
@@ -210,49 +192,3 @@ Users:
210 firmware assigned instance number of the PCI 192 firmware assigned instance number of the PCI
211 device that can help in understanding the firmware 193 device that can help in understanding the firmware
212 intended order of the PCI device. 194 intended order of the PCI device.
213
214What: /sys/bus/pci/devices/.../d3cold_allowed
215Date: July 2012
216Contact: Huang Ying <ying.huang@intel.com>
217Description:
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.
225
226What: /sys/bus/pci/devices/.../sriov_totalvfs
227Date: November 2012
228Contact: Donald Dutile <ddutile@redhat.com>
229Description:
230 This file appears when a physical PCIe device supports SR-IOV.
231 Userspace applications can read this file to determine the
232 maximum number of Virtual Functions (VFs) a PCIe physical
233 function (PF) can support. Typically, this is the value reported
234 in the PF's SR-IOV extended capability structure's TotalVFs
235 element. Drivers have the ability at probe time to reduce the
236 value read from this file via the pci_sriov_set_totalvfs()
237 function.
238
239What: /sys/bus/pci/devices/.../sriov_numvfs
240Date: November 2012
241Contact: Donald Dutile <ddutile@redhat.com>
242Description:
243 This file appears when a physical PCIe device supports SR-IOV.
244 Userspace applications can read and write to this file to
245 determine and control the enablement or disablement of Virtual
246 Functions (VFs) on the physical function (PF). A read of this
247 file will return the number of VFs that are enabled on this PF.
248 A number written to this file will enable the specified
249 number of VFs. A userspace application would typically read the
250 file and check that the value is zero, and then write the number
251 of VFs that should be enabled on the PF; the value written
252 should be less than or equal to the value in the sriov_totalvfs
253 file. A userspace application wanting to disable the VFs would
254 write a zero to this file. The core ensures that valid values
255 are written to this file, and returns errors when values are not
256 valid. For example, writing a 2 to this file when sriov_numvfs
257 is not 0 and not 2 already will return an error. Writing a 10
258 when the value of sriov_totalvfs is 8 will return an error.
diff --git a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss
index 53d99edd1d7..f5bb0a3bb8c 100644
--- a/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss
+++ b/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss
@@ -71,10 +71,3 @@ 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
74Where: /sys/bus/pci/devices/<dev>/ccissX/transport_mode
75Date: July 2011
76Kernel Version: 3.0
77Contact: iss_storagedev@hp.com
78Description: 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
deleted file mode 100644
index 60c60fa624b..00000000000
--- a/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd
+++ /dev/null
@@ -1,46 +0,0 @@
1What: /sys/bus/pci/drivers/ehci_hcd/.../companion
2 /sys/bus/usb/devices/usbN/../companion
3Date: January 2007
4KernelVersion: 2.6.21
5Contact: Alan Stern <stern@rowland.harvard.edu>
6Description:
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-rbd b/Documentation/ABI/testing/sysfs-bus-rbd
index cd9213ccf3d..fa72ccb2282 100644
--- a/Documentation/ABI/testing/sysfs-bus-rbd
+++ b/Documentation/ABI/testing/sysfs-bus-rbd
@@ -25,10 +25,6 @@ client_id
25 25
26 The ceph unique client id that was assigned for this specific session. 26 The ceph unique client id that was assigned for this specific session.
27 27
28features
29
30 A hexadecimal encoding of the feature bits for this image.
31
32major 28major
33 29
34 The block device major number. 30 The block device major number.
@@ -37,21 +33,10 @@ name
37 33
38 The name of the rbd image. 34 The name of the rbd image.
39 35
40image_id
41
42 The unique id for the rbd image. (For rbd image format 1
43 this is empty.)
44
45pool 36pool
46 37
47 The name of the storage pool where this rbd image resides. 38 The pool where this rbd image resides. The pool-name pair is unique
48 An rbd image name is unique within its pool. 39 per rados system.
49
50pool_id
51
52 The unique identifier for the rbd image's pool. This is
53 a permanent attribute of the pool. A pool's id will never
54 change.
55 40
56size 41size
57 42
@@ -66,27 +51,33 @@ current_snap
66 51
67 The current snapshot for which the device is mapped. 52 The current snapshot for which the device is mapped.
68 53
54create_snap
55
56 Create a snapshot:
57
58 $ echo <snap-name> > /sys/bus/rbd/devices/<dev-id>/snap_create
59
60rollback_snap
61
62 Rolls back data to the specified snapshot. This goes over the entire
63 list of rados blocks and sends a rollback command to each.
64
65 $ echo <snap-name> > /sys/bus/rbd/devices/<dev-id>/snap_rollback
66
69snap_* 67snap_*
70 68
71 A directory per each snapshot 69 A directory per each snapshot
72 70
73parent
74
75 Information identifying the pool, image, and snapshot id for
76 the parent image in a layered rbd image (format 2 only).
77 71
78Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name> 72Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name>
79------------------------------------------------------------- 73-------------------------------------------------------------
80 74
81snap_id 75id
82 76
83 The rados internal snapshot id assigned for this snapshot 77 The rados internal snapshot id assigned for this snapshot
84 78
85snap_size 79size
86 80
87 The size of the image when this snapshot was taken. 81 The size of the image when this snapshot was taken.
88 82
89snap_features
90
91 A hexadecimal encoding of the feature bits for this snapshot.
92 83
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 @@
1What: /sys/bus/rpmsg/devices/.../name
2Date: June 2011
3KernelVersion: 3.3
4Contact: Ohad Ben-Cohen <ohad@wizery.com>
5Description:
6 Every rpmsg device is a communication channel with a remote
7 processor. Channels are identified with a (textual) name,
8 which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in
9 rpmsg.h).
10
11 This sysfs entry contains the name of this channel.
12
13What: /sys/bus/rpmsg/devices/.../src
14Date: June 2011
15KernelVersion: 3.3
16Contact: Ohad Ben-Cohen <ohad@wizery.com>
17Description:
18 Every rpmsg device is a communication channel with a remote
19 processor. Channels have a local ("source") rpmsg address,
20 and remote ("destination") rpmsg address. When an entity
21 starts listening on one end of a channel, it assigns it with
22 a unique rpmsg address (a 32 bits integer). This way when
23 inbound messages arrive to this address, the rpmsg core
24 dispatches them to the listening entity (a kernel driver).
25
26 This sysfs entry contains the src (local) rpmsg address
27 of this channel. If it contains 0xffffffff, then an address
28 wasn't assigned (can happen if no driver exists for this
29 channel).
30
31What: /sys/bus/rpmsg/devices/.../dst
32Date: June 2011
33KernelVersion: 3.3
34Contact: Ohad Ben-Cohen <ohad@wizery.com>
35Description:
36 Every rpmsg device is a communication channel with a remote
37 processor. Channels have a local ("source") rpmsg address,
38 and remote ("destination") rpmsg address. When an entity
39 starts listening on one end of a channel, it assigns it with
40 a unique rpmsg address (a 32 bits integer). This way when
41 inbound messages arrive to this address, the rpmsg core
42 dispatches them to the listening entity.
43
44 This sysfs entry contains the dst (remote) rpmsg address
45 of this channel. If it contains 0xffffffff, then an address
46 wasn't assigned (can happen if the kernel driver that
47 is attached to this channel is exposing a service to the
48 remote processor. This make it a local rpmsg server,
49 and it is listening for inbound messages that may be sent
50 from any remote rpmsg client; it is not bound to a single
51 remote entity).
52
53What: /sys/bus/rpmsg/devices/.../announce
54Date: June 2011
55KernelVersion: 3.3
56Contact: Ohad Ben-Cohen <ohad@wizery.com>
57Description:
58 Every rpmsg device is a communication channel with a remote
59 processor. Channels are identified by a textual name (see
60 /sys/bus/rpmsg/devices/.../name above) and have a local
61 ("source") rpmsg address, and remote ("destination") rpmsg
62 address.
63
64 A channel is first created when an entity, whether local
65 or remote, starts listening on it for messages (and is thus
66 called an rpmsg server).
67
68 When that happens, a "name service" announcement is sent
69 to the other processor, in order to let it know about the
70 creation of the channel (this way remote clients know they
71 can start sending messages).
72
73 This sysfs entry tells us whether the channel is a local
74 server channel that is announced (values are either
75 true or false).
diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb
index b6fbe514a86..294aa864a60 100644
--- a/Documentation/ABI/testing/sysfs-bus-usb
+++ b/Documentation/ABI/testing/sysfs-bus-usb
@@ -119,42 +119,6 @@ Description:
119 Write a 1 to force the device to disconnect 119 Write a 1 to force the device to disconnect
120 (equivalent to unplugging a wired USB device). 120 (equivalent to unplugging a wired USB device).
121 121
122What: /sys/bus/usb/drivers/.../new_id
123Date: October 2011
124Contact: linux-usb@vger.kernel.org
125Description:
126 Writing a device ID to this file will attempt to
127 dynamically add a new device ID to a USB device driver.
128 This may allow the driver to support more hardware than
129 was included in the driver's static device ID support
130 table at compile time. The format for the device ID is:
131 idVendor idProduct bInterfaceClass.
132 The vendor ID and device ID fields are required, the
133 interface class is optional.
134 Upon successfully adding an ID, the driver will probe
135 for the device and attempt to bind to it. For example:
136 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
137
138 Reading from this file will list all dynamically added
139 device IDs in the same format, with one entry per
140 line. For example:
141 # cat /sys/bus/usb/drivers/foo/new_id
142 8086 10f5
143 dead beef 06
144 f00d cafe
145
146 The list will be truncated at PAGE_SIZE bytes due to
147 sysfs restrictions.
148
149What: /sys/bus/usb-serial/drivers/.../new_id
150Date: October 2011
151Contact: linux-usb@vger.kernel.org
152Description:
153 For serial USB drivers, this attribute appears under the
154 extra bus folder "usb-serial" in sysfs; apart from that
155 difference, all descriptions from the entry
156 "/sys/bus/usb/drivers/.../new_id" apply.
157
158What: /sys/bus/usb/drivers/.../remove_id 122What: /sys/bus/usb/drivers/.../remove_id
159Date: November 2009 123Date: November 2009
160Contact: CHENG Renquan <rqcheng@smu.edu.sg> 124Contact: CHENG Renquan <rqcheng@smu.edu.sg>
@@ -168,10 +132,6 @@ Description:
168 match the driver to the device. For example: 132 match the driver to the device. For example:
169 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id 133 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
170 134
171 Reading from this file will list the dynamically added
172 device IDs, exactly like reading from the entry
173 "/sys/bus/usb/drivers/.../new_id"
174
175What: /sys/bus/usb/device/.../avoid_reset_quirk 135What: /sys/bus/usb/device/.../avoid_reset_quirk
176Date: December 2009 136Date: December 2009
177Contact: Oliver Neukum <oliver@neukum.org> 137Contact: Oliver Neukum <oliver@neukum.org>
@@ -182,48 +142,3 @@ Description:
182 such devices. 142 such devices.
183Users: 143Users:
184 usb_modeswitch 144 usb_modeswitch
185
186What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm
187Date: September 2011
188Contact: Andiry Xu <andiry.xu@amd.com>
189Description:
190 If CONFIG_USB_SUSPEND is set and a USB 2.0 lpm-capable device
191 is plugged in to a xHCI host which support link PM, it will
192 perform a LPM test; if the test is passed and host supports
193 USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will
194 be enabled for the device and the USB device directory will
195 contain a file named power/usb2_hardware_lpm. The file holds
196 a string value (enable or disable) indicating whether or not
197 USB2 hardware LPM is enabled for the device. Developer can
198 write y/Y/1 or n/N/0 to the file to enable/disable the
199 feature.
200
201What: /sys/bus/usb/devices/.../removable
202Date: February 2012
203Contact: Matthew Garrett <mjg@redhat.com>
204Description:
205 Some information about whether a given USB device is
206 physically fixed to the platform can be inferred from a
207 combination of hub descriptor bits and platform-specific data
208 such as ACPI. This file will read either "removable" or
209 "fixed" if the information is available, and "unknown"
210 otherwise.
211
212What: /sys/bus/usb/devices/.../ltm_capable
213Date: July 2012
214Contact: Sarah Sharp <sarah.a.sharp@linux.intel.com>
215Description:
216 USB 3.0 devices may optionally support Latency Tolerance
217 Messaging (LTM). They indicate their support by setting a bit
218 in the bmAttributes field of their SuperSpeed BOS descriptors.
219 If that bit is set for the device, ltm_capable will read "yes".
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
222 always read "no" for USB 1.1 and USB 2.0 devices.
223
224What: /sys/bus/usb/devices/.../(hub interface)/portX
225Date: August 2012
226Contact: Lan Tianyu <tianyu.lan@intel.com>
227Description:
228 The /sys/bus/usb/devices/.../(hub interface)/portX
229 is usb port device's sysfs directory.
diff --git a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
index 70d00dfa443..cb830df8777 100644
--- a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
+++ b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
@@ -40,4 +40,4 @@ Description: Controls the decimal places on the device.
40 the value of 10 ** n. Assume this field has 40 the value of 10 ** n. Assume this field has
41 the value k and has 1 or more decimal places set, 41 the value k and has 1 or more decimal places set,
42 to set the mth place (where m is not already set), 42 to set the mth place (where m is not already set),
43 change this fields value to k + 10 ** m. 43 change this fields value to k + 10 ** m. \ No newline at end of file
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 @@
1What: /sys/block/<device>/iosched/target_latency
2Date: March 2012
3contact: Tao Ma <boyu.mt@taobao.com>
4Description:
5 The /sys/block/<device>/iosched/target_latency only exists
6 when the user sets cfq to /sys/block/<device>/scheduler.
7 It contains an estimated latency time for the cfq. cfq will
8 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
index 676530fcf74..4b0cb891e46 100644
--- a/Documentation/ABI/testing/sysfs-class
+++ b/Documentation/ABI/testing/sysfs-class
@@ -1,6 +1,6 @@
1What: /sys/class/ 1What: /sys/class/
2Date: Febuary 2006 2Date: Febuary 2006
3Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 3Contact: Greg Kroah-Hartman <gregkh@suse.de>
4Description: 4Description:
5 The /sys/class directory will consist of a group of 5 The /sys/class directory will consist of a group of
6 subdirectories describing individual classes of devices 6 subdirectories describing individual classes of devices
diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
index 33e64880811..aa11dbdd794 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
4What: /sys/class/backlight/<backlight>/l3_office_max 4What: /sys/class/backlight/<backlight>/l3_office_max
5What: /sys/class/backlight/<backlight>/l4_indoor_max 5What: /sys/class/backlight/<backlight>/l4_indoor_max
6What: /sys/class/backlight/<backlight>/l5_dark_max 6What: /sys/class/backlight/<backlight>/l5_dark_max
7Date: May 2011 7Date: Mai 2011
8KernelVersion: 3.0 8KernelVersion: 2.6.40
9Contact: device-drivers-devel@blackfin.uclinux.org 9Contact: device-drivers-devel@blackfin.uclinux.org
10Description: 10Description:
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
18What: /sys/class/backlight/<backlight>/l3_office_dim 18What: /sys/class/backlight/<backlight>/l3_office_dim
19What: /sys/class/backlight/<backlight>/l4_indoor_dim 19What: /sys/class/backlight/<backlight>/l4_indoor_dim
20What: /sys/class/backlight/<backlight>/l5_dark_dim 20What: /sys/class/backlight/<backlight>/l5_dark_dim
21Date: May 2011 21Date: Mai 2011
22KernelVersion: 3.0 22KernelVersion: 2.6.40
23Contact: device-drivers-devel@blackfin.uclinux.org 23Contact: device-drivers-devel@blackfin.uclinux.org
24Description: 24Description:
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
31What: /sys/class/backlight/<backlight>/ambient_light_level 31What: /sys/class/backlight/<backlight>/ambient_light_level
32Date: May 2011 32Date: Mai 2011
33KernelVersion: 3.0 33KernelVersion: 2.6.40
34Contact: device-drivers-devel@blackfin.uclinux.org 34Contact: device-drivers-devel@blackfin.uclinux.org
35Description: 35Description:
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
41What: /sys/class/backlight/<backlight>/ambient_light_zone 41What: /sys/class/backlight/<backlight>/ambient_light_zone
42Date: May 2011 42Date: Mai 2011
43KernelVersion: 3.0 43KernelVersion: 2.6.40
44Contact: device-drivers-devel@blackfin.uclinux.org 44Contact: device-drivers-devel@blackfin.uclinux.org
45Description: 45Description:
46 Get/Set current ambient light zone. Reading returns 46 Get/Set current ambient light zone. Reading returns
@@ -53,4 +53,4 @@ Description:
53 Documentation/ABI/stable/sysfs-class-backlight. 53 Documentation/ABI/stable/sysfs-class-backlight.
54 It can be enabled by writing the value stored in 54 It can be enabled by writing the value stored in
55 /sys/class/backlight/<backlight>/max_brightness to 55 /sys/class/backlight/<backlight>/max_brightness to
56 /sys/class/backlight/<backlight>/brightness. 56 /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 @@
1What: /sys/class/backlight/<backlight>/als_channel
2Date: May 2012
3KernelVersion: 3.5
4Contact: Johan Hovold <jhovold@gmail.com>
5Description:
6 Get the ALS output channel used as input in
7 ALS-current-control mode (0, 1), where
8
9 0 - out_current0 (backlight 0)
10 1 - out_current1 (backlight 1)
11
12What: /sys/class/backlight/<backlight>/als_en
13Date: May 2012
14KernelVersion: 3.5
15Contact: Johan Hovold <jhovold@gmail.com>
16Description:
17 Enable ALS-current-control mode (0, 1).
18
19What: /sys/class/backlight/<backlight>/id
20Date: April 2012
21KernelVersion: 3.5
22Contact: Johan Hovold <jhovold@gmail.com>
23Description:
24 Get the id of this backlight (0, 1).
25
26What: /sys/class/backlight/<backlight>/linear
27Date: April 2012
28KernelVersion: 3.5
29Contact: Johan Hovold <jhovold@gmail.com>
30Description:
31 Set the brightness-mapping mode (0, 1), where
32
33 0 - exponential mode
34 1 - linear mode
35
36What: /sys/class/backlight/<backlight>/pwm
37Date: April 2012
38KernelVersion: 3.5
39Contact: Johan Hovold <jhovold@gmail.com>
40Description:
41 Set the PWM-input control mask (5 bits), where
42
43 bit 5 - PWM-input enabled in Zone 4
44 bit 4 - PWM-input enabled in Zone 3
45 bit 3 - PWM-input enabled in Zone 2
46 bit 2 - PWM-input enabled in Zone 1
47 bit 1 - PWM-input enabled in Zone 0
48 bit 0 - PWM-input enabled
diff --git a/Documentation/ABI/testing/sysfs-class-devfreq b/Documentation/ABI/testing/sysfs-class-devfreq
deleted file mode 100644
index 0ba6ea2f89d..00000000000
--- a/Documentation/ABI/testing/sysfs-class-devfreq
+++ /dev/null
@@ -1,80 +0,0 @@
1What: /sys/class/devfreq/.../
2Date: September 2011
3Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
4Description:
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
10What: /sys/class/devfreq/.../governor
11Date: September 2011
12Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
13Description:
14 The /sys/class/devfreq/.../governor show or set the name of the
15 governor used by the corresponding devfreq object.
16
17What: /sys/class/devfreq/.../cur_freq
18Date: September 2011
19Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
20Description:
21 The /sys/class/devfreq/.../cur_freq shows the current
22 frequency of the corresponding devfreq object. Same as
23 target_freq when get_cur_freq() is not implemented by
24 devfreq driver.
25
26What: /sys/class/devfreq/.../target_freq
27Date: September 2012
28Contact: Rajagopal Venkat <rajagopal.venkat@linaro.org>
29Description:
30 The /sys/class/devfreq/.../target_freq shows the next governor
31 predicted target frequency of the corresponding devfreq object.
32
33What: /sys/class/devfreq/.../polling_interval
34Date: September 2011
35Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
36Description:
37 The /sys/class/devfreq/.../polling_interval shows and sets
38 the requested polling interval of the corresponding devfreq
39 object. The values are represented in ms. If the value is
40 less than 1 jiffy, it is considered to be 0, which means
41 no polling. This value is meaningless if the governor is
42 not polling; thus. If the governor is not using
43 devfreq-provided central polling
44 (/sys/class/devfreq/.../central_polling is 0), this value
45 may be useless.
46
47What: /sys/class/devfreq/.../trans_stat
48Date: October 2012
49Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
50Descrtiption:
51 This ABI shows the statistics of devfreq behavior on a
52 specific device. It shows the time spent in each state and
53 the number of transitions between states.
54 In order to activate this ABI, the devfreq target device
55 driver should provide the list of available frequencies
56 with its profile.
57
58What: /sys/class/devfreq/.../userspace/set_freq
59Date: September 2011
60Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
61Description:
62 The /sys/class/devfreq/.../userspace/set_freq shows and
63 sets the requested frequency for the devfreq object if
64 userspace governor is in effect.
65
66What: /sys/class/devfreq/.../available_frequencies
67Date: October 2012
68Contact: Nishanth Menon <nm@ti.com>
69Description:
70 The /sys/class/devfreq/.../available_frequencies shows
71 the available frequencies of the corresponding devfreq object.
72 This is a snapshot of available frequencies and not limited
73 by the min/max frequency restrictions.
74
75What: /sys/class/devfreq/.../available_governors
76Date: October 2012
77Contact: Nishanth Menon <nm@ti.com>
78Description:
79 The /sys/class/devfreq/.../available_governors shows
80 currently available governors in the system.
diff --git a/Documentation/ABI/testing/sysfs-class-extcon b/Documentation/ABI/testing/sysfs-class-extcon
deleted file mode 100644
index 57a72623291..00000000000
--- a/Documentation/ABI/testing/sysfs-class-extcon
+++ /dev/null
@@ -1,97 +0,0 @@
1What: /sys/class/extcon/.../
2Date: February 2012
3Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
4Description:
5 Provide a place in sysfs for the extcon objects.
6 This allows accessing extcon specific variables.
7 The name of extcon object denoted as ... is the name given
8 with extcon_dev_register.
9
10 One extcon device denotes a single external connector
11 port. An external connector may have multiple cables
12 attached simultaneously. Many of docks, cradles, and
13 accessory cables have such capability. For example,
14 the 30-pin port of Nuri board (/arch/arm/mach-exynos)
15 may have both HDMI and Charger attached, or analog audio,
16 video, and USB cables attached simultaneously.
17
18 If there are cables mutually exclusive with each other,
19 such binary relations may be expressed with extcon_dev's
20 mutually_exclusive array.
21
22What: /sys/class/extcon/.../name
23Date: February 2012
24Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
25Description:
26 The /sys/class/extcon/.../name shows the name of the extcon
27 object. If the extcon object has an optional callback
28 "show_name" defined, the callback will provide the name with
29 this sysfs node.
30
31What: /sys/class/extcon/.../state
32Date: February 2012
33Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
34Description:
35 The /sys/class/extcon/.../state shows and stores the cable
36 attach/detach information of the corresponding extcon object.
37 If the extcon object has an optional callback "show_state"
38 defined, the showing function is overridden with the optional
39 callback.
40
41 If the default callback for showing function is used, the
42 format is like this:
43 # cat state
44 USB_OTG=1
45 HDMI=0
46 TA=1
47 EAR_JACK=0
48 #
49 In this example, the extcon device has USB_OTG and TA
50 cables attached and HDMI and EAR_JACK cables detached.
51
52 In order to update the state of an extcon device, enter a hex
53 state number starting with 0x:
54 # echo 0xHEX > state
55
56 This updates the whole state of the extcon device.
57 Inputs of all the methods are required to meet the
58 mutually_exclusive conditions if they exist.
59
60 It is recommended to use this "global" state interface if
61 you need to set the value atomically. The later state
62 interface associated with each cable cannot update
63 multiple cable states of an extcon device simultaneously.
64
65What: /sys/class/extcon/.../cable.x/name
66Date: February 2012
67Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
68Description:
69 The /sys/class/extcon/.../cable.x/name shows the name of cable
70 "x" (integer between 0 and 31) of an extcon device.
71
72What: /sys/class/extcon/.../cable.x/state
73Date: February 2012
74Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
75Description:
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
78 device. The state value is either 0 (detached) or 1
79 (attached).
80
81What: /sys/class/extcon/.../mutually_exclusive/...
82Date: December 2011
83Contact: MyungJoo Ham <myungjoo.ham@samsung.com>
84Description:
85 Shows the relations of mutually exclusiveness. For example,
86 if the mutually_exclusive array of extcon device is
87 {0x3, 0x5, 0xC, 0x0}, then the output is:
88 # ls mutually_exclusive/
89 0x3
90 0x5
91 0xc
92 #
93
94 Note that mutually_exclusive is a sub-directory of the extcon
95 device and the file names under the mutually_exclusive
96 directory show the mutually-exclusive sets, not the contents
97 of the files.
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 @@
1What: /sys/class/leds/<led>/als_channel
2Date: May 2012
3KernelVersion: 3.5
4Contact: Johan Hovold <jhovold@gmail.com>
5Description:
6 Set the ALS output channel to use as input in
7 ALS-current-control mode (1, 2), where
8
9 1 - out_current1
10 2 - out_current2
11
12What: /sys/class/leds/<led>/als_en
13Date: May 2012
14KernelVersion: 3.5
15Contact: Johan Hovold <jhovold@gmail.com>
16Description:
17 Enable ALS-current-control mode (0, 1).
18
19What: /sys/class/leds/<led>/falltime
20What: /sys/class/leds/<led>/risetime
21Date: April 2012
22KernelVersion: 3.5
23Contact: Johan Hovold <jhovold@gmail.com>
24Description:
25 Set the pattern generator fall and rise times (0..7), where
26
27 0 - 2048 us
28 1 - 262 ms
29 2 - 524 ms
30 3 - 1.049 s
31 4 - 2.097 s
32 5 - 4.194 s
33 6 - 8.389 s
34 7 - 16.78 s
35
36What: /sys/class/leds/<led>/id
37Date: April 2012
38KernelVersion: 3.5
39Contact: Johan Hovold <jhovold@gmail.com>
40Description:
41 Get the id of this led (0..3).
42
43What: /sys/class/leds/<led>/linear
44Date: April 2012
45KernelVersion: 3.5
46Contact: Johan Hovold <jhovold@gmail.com>
47Description:
48 Set the brightness-mapping mode (0, 1), where
49
50 0 - exponential mode
51 1 - linear mode
52
53What: /sys/class/leds/<led>/pwm
54Date: April 2012
55KernelVersion: 3.5
56Contact: Johan Hovold <jhovold@gmail.com>
57Description:
58 Set the PWM-input control mask (5 bits), where
59
60 bit 5 - PWM-input enabled in Zone 4
61 bit 4 - PWM-input enabled in Zone 3
62 bit 3 - PWM-input enabled in Zone 2
63 bit 2 - PWM-input enabled in Zone 1
64 bit 1 - PWM-input enabled in Zone 0
65 bit 0 - PWM-input enabled
diff --git a/Documentation/ABI/testing/sysfs-class-mtd b/Documentation/ABI/testing/sysfs-class-mtd
index 938ef71e203..4d55a188898 100644
--- a/Documentation/ABI/testing/sysfs-class-mtd
+++ b/Documentation/ABI/testing/sysfs-class-mtd
@@ -123,55 +123,3 @@ Description:
123 half page, or a quarter page). 123 half page, or a quarter page).
124 124
125 In the case of ECC NOR, it is the ECC block size. 125 In the case of ECC NOR, it is the ECC block size.
126
127What: /sys/class/mtd/mtdX/ecc_strength
128Date: April 2012
129KernelVersion: 3.4
130Contact: linux-mtd@lists.infradead.org
131Description:
132 Maximum number of bit errors that the device is capable of
133 correcting within each region covering an ecc step. This will
134 always be a non-negative integer. Note that some devices will
135 have multiple ecc steps within each writesize region.
136
137 In the case of devices lacking any ECC capability, it is 0.
138
139What: /sys/class/mtd/mtdX/bitflip_threshold
140Date: April 2012
141KernelVersion: 3.4
142Contact: linux-mtd@lists.infradead.org
143Description:
144 This allows the user to examine and adjust the criteria by which
145 mtd returns -EUCLEAN from mtd_read() and mtd_read_oob(). If the
146 maximum number of bit errors that were corrected on any single
147 region comprising an ecc step (as reported by the driver) equals
148 or exceeds this value, -EUCLEAN is returned. Otherwise, absent
149 an error, 0 is returned. Higher layers (e.g., UBI) use this
150 return code as an indication that an erase block may be
151 degrading and should be scrutinized as a candidate for being
152 marked as bad.
153
154 The initial value may be specified by the flash device driver.
155 If not, then the default value is ecc_strength.
156
157 The introduction of this feature brings a subtle change to the
158 meaning of the -EUCLEAN return code. Previously, it was
159 interpreted to mean simply "one or more bit errors were
160 corrected". Its new interpretation can be phrased as "a
161 dangerously high number of bit errors were corrected on one or
162 more regions comprising an ecc step". The precise definition of
163 "dangerously high" can be adjusted by the user with
164 bitflip_threshold. Users are discouraged from doing this,
165 however, unless they know what they are doing and have intimate
166 knowledge of the properties of their device. Broadly speaking,
167 bitflip_threshold should be low enough to detect genuine erase
168 block degradation, but high enough to avoid the consequences of
169 a persistent return value of -EUCLEAN on devices where sticky
170 bitflips occur. Note that if bitflip_threshold exceeds
171 ecc_strength, -EUCLEAN is never returned by the read operations.
172 Conversely, if bitflip_threshold is zero, -EUCLEAN is always
173 returned, absent a hard error.
174
175 This is generally applicable only to NAND flash devices with ECC
176 capability. It is ignored on devices lacking ECC capability;
177 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
index bdc00707c75..38dd762def4 100644
--- a/Documentation/ABI/testing/sysfs-class-net-batman-adv
+++ b/Documentation/ABI/testing/sysfs-class-net-batman-adv
@@ -1,10 +1,4 @@
1 1
2What: /sys/class/net/<iface>/batman-adv/iface_status
3Date: May 2010
4Contact: Marek Lindner <lindner_marek@yahoo.de>
5Description:
6 Indicates the status of <iface> as it is seen by batman.
7
8What: /sys/class/net/<iface>/batman-adv/mesh_iface 2What: /sys/class/net/<iface>/batman-adv/mesh_iface
9Date: May 2010 3Date: May 2010
10Contact: Marek Lindner <lindner_marek@yahoo.de> 4Contact: Marek Lindner <lindner_marek@yahoo.de>
@@ -13,3 +7,8 @@ Description:
13 displays the batman mesh interface this <iface> 7 displays the batman mesh interface this <iface>
14 currently is associated with. 8 currently is associated with.
15 9
10What: /sys/class/net/<iface>/batman-adv/iface_status
11Date: May 2010
12Contact: Marek Lindner <lindner_marek@yahoo.de>
13Description:
14 Indicates the status of <iface> as it is seen by batman.
diff --git a/Documentation/ABI/testing/sysfs-class-net-grcan b/Documentation/ABI/testing/sysfs-class-net-grcan
deleted file mode 100644
index f418c92ca55..00000000000
--- a/Documentation/ABI/testing/sysfs-class-net-grcan
+++ /dev/null
@@ -1,35 +0,0 @@
1
2What: /sys/class/net/<iface>/grcan/enable0
3Date: October 2012
4KernelVersion: 3.8
5Contact: Andreas Larsson <andreas@gaisler.com>
6Description:
7 Hardware configuration of physical interface 0. This file reads
8 and writes the "Enable 0" bit of the configuration register.
9 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
10 core library documentation for details. The default value is 0
11 or set by the module parameter grcan.enable0 and can be read at
12 /sys/module/grcan/parameters/enable0.
13
14What: /sys/class/net/<iface>/grcan/enable1
15Date: October 2012
16KernelVersion: 3.8
17Contact: Andreas Larsson <andreas@gaisler.com>
18Description:
19 Hardware configuration of physical interface 1. This file reads
20 and writes the "Enable 1" bit of the configuration register.
21 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
22 core library documentation for details. The default value is 0
23 or set by the module parameter grcan.enable1 and can be read at
24 /sys/module/grcan/parameters/enable1.
25
26What: /sys/class/net/<iface>/grcan/select
27Date: October 2012
28KernelVersion: 3.8
29Contact: Andreas Larsson <andreas@gaisler.com>
30Description:
31 Configuration of which physical interface to be used. Possible
32 values: 0 or 1. See the GRCAN chapter of the GRLIB IP core
33 library documentation for details. The default value is 0 or is
34 set by the module parameter grcan.select and can be read at
35 /sys/module/grcan/parameters/select.
diff --git a/Documentation/ABI/testing/sysfs-class-net-mesh b/Documentation/ABI/testing/sysfs-class-net-mesh
index bc41da61608..748fe1701d2 100644
--- a/Documentation/ABI/testing/sysfs-class-net-mesh
+++ b/Documentation/ABI/testing/sysfs-class-net-mesh
@@ -6,14 +6,6 @@ Description:
6 Indicates whether the batman protocol messages of the 6 Indicates whether the batman protocol messages of the
7 mesh <mesh_iface> shall be aggregated or not. 7 mesh <mesh_iface> shall be aggregated or not.
8 8
9What: /sys/class/net/<mesh_iface>/mesh/ap_isolation
10Date: May 2011
11Contact: Antonio Quartulli <ordex@autistici.org>
12Description:
13 Indicates whether the data traffic going from a
14 wireless client to another wireless client will be
15 silently dropped.
16
17What: /sys/class/net/<mesh_iface>/mesh/bonding 9What: /sys/class/net/<mesh_iface>/mesh/bonding
18Date: June 2010 10Date: June 2010
19Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de> 11Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
@@ -22,15 +14,6 @@ Description:
22 mesh will be sent using multiple interfaces at the 14 mesh will be sent using multiple interfaces at the
23 same time (if available). 15 same time (if available).
24 16
25What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
26Date: November 2011
27Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
28Description:
29 Indicates whether the bridge loop avoidance feature
30 is enabled. This feature detects and avoids loops
31 between the mesh and devices bridged with the soft
32 interface <mesh_iface>.
33
34What: /sys/class/net/<mesh_iface>/mesh/fragmentation 17What: /sys/class/net/<mesh_iface>/mesh/fragmentation
35Date: October 2010 18Date: October 2010
36Contact: Andreas Langer <an.langer@gmx.de> 19Contact: Andreas Langer <an.langer@gmx.de>
@@ -60,13 +43,6 @@ Description:
60 Defines the selection criteria this node will use 43 Defines the selection criteria this node will use
61 to choose a gateway if gw_mode was set to 'client'. 44 to choose a gateway if gw_mode was set to 'client'.
62 45
63What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
64Date: Oct 2010
65Contact: Linus Lüssing <linus.luessing@web.de>
66Description:
67 Defines the penalty which will be applied to an
68 originator message's tq-field on every hop.
69
70What: /sys/class/net/<mesh_iface>/mesh/orig_interval 46What: /sys/class/net/<mesh_iface>/mesh/orig_interval
71Date: May 2010 47Date: May 2010
72Contact: Marek Lindner <lindner_marek@yahoo.de> 48Contact: Marek Lindner <lindner_marek@yahoo.de>
@@ -74,12 +50,12 @@ Description:
74 Defines the interval in milliseconds in which batman 50 Defines the interval in milliseconds in which batman
75 sends its protocol messages. 51 sends its protocol messages.
76 52
77What: /sys/class/net/<mesh_iface>/mesh/routing_algo 53What: /sys/class/net/<mesh_iface>/mesh/hop_penalty
78Date: Dec 2011 54Date: Oct 2010
79Contact: Marek Lindner <lindner_marek@yahoo.de> 55Contact: Linus Lüssing <linus.luessing@web.de>
80Description: 56Description:
81 Defines the routing procotol this mesh instance 57 Defines the penalty which will be applied to an
82 uses to find the optimal paths through the mesh. 58 originator message's tq-field on every hop.
83 59
84What: /sys/class/net/<mesh_iface>/mesh/vis_mode 60What: /sys/class/net/<mesh_iface>/mesh/vis_mode
85Date: May 2010 61Date: May 2010
diff --git a/Documentation/ABI/testing/sysfs-class-regulator b/Documentation/ABI/testing/sysfs-class-regulator
index bc578bc6062..e091fa87379 100644
--- a/Documentation/ABI/testing/sysfs-class-regulator
+++ b/Documentation/ABI/testing/sysfs-class-regulator
@@ -349,24 +349,3 @@ 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
353What: /sys/class/regulator/.../bypass
354Date: September 2012
355KernelVersion: 3.7
356Contact: Mark Brown <broonie@opensource.wolfsonmicro.com>
357Description:
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-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 @@
1What: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock
2Date: Oct 2011
3KernelVersion: 3.0
4Contact: Mark Godfrey <mark.godfrey@stericsson.com>
5Description: The rtc_calibration attribute allows the userspace to
6 calibrate the AB8500.s 32KHz Real Time Clock.
7 Every 60 seconds the AB8500 will correct the RTC's value
8 by adding to it the value of this attribute.
9 The range of the attribute is -127 to +127 in units of
10 30.5 micro-seconds (half-parts-per-million of the 32KHz clock)
11Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration
12 daemon uses this interface.
diff --git a/Documentation/ABI/testing/sysfs-devices b/Documentation/ABI/testing/sysfs-devices
index 5fcc94358b8..6a25671ee5f 100644
--- a/Documentation/ABI/testing/sysfs-devices
+++ b/Documentation/ABI/testing/sysfs-devices
@@ -1,6 +1,6 @@
1What: /sys/devices 1What: /sys/devices
2Date: February 2006 2Date: February 2006
3Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 3Contact: Greg Kroah-Hartman <gregkh@suse.de>
4Description: 4Description:
5 The /sys/devices tree contains a snapshot of the 5 The /sys/devices tree contains a snapshot of the
6 internal state of the kernel device tree. Devices will 6 internal state of the kernel device tree. Devices will
diff --git a/Documentation/ABI/testing/sysfs-devices-edac b/Documentation/ABI/testing/sysfs-devices-edac
deleted file mode 100644
index 30ee78aaed7..00000000000
--- a/Documentation/ABI/testing/sysfs-devices-edac
+++ /dev/null
@@ -1,140 +0,0 @@
1What: /sys/devices/system/edac/mc/mc*/reset_counters
2Date: January 2006
3Contact: linux-edac@vger.kernel.org
4Description: This write-only control file will zero all the statistical
5 counters for UE and CE errors on the given memory controller.
6 Zeroing the counters will also reset the timer indicating how
7 long since the last counter were reset. This is useful for
8 computing errors/time. Since the counters are always reset
9 at driver initialization time, no module/kernel parameter
10 is available.
11
12What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
13Date: January 2006
14Contact: linux-edac@vger.kernel.org
15Description: This attribute file displays how many seconds have elapsed
16 since the last counter reset. This can be used with the error
17 counters to measure error rates.
18
19What: /sys/devices/system/edac/mc/mc*/mc_name
20Date: January 2006
21Contact: linux-edac@vger.kernel.org
22Description: This attribute file displays the type of memory controller
23 that is being utilized.
24
25What: /sys/devices/system/edac/mc/mc*/size_mb
26Date: January 2006
27Contact: linux-edac@vger.kernel.org
28Description: This attribute file displays, in count of megabytes, of memory
29 that this memory controller manages.
30
31What: /sys/devices/system/edac/mc/mc*/ue_count
32Date: January 2006
33Contact: linux-edac@vger.kernel.org
34Description: This attribute file displays the total count of uncorrectable
35 errors that have occurred on this memory controller. If
36 panic_on_ue is set, this counter will not have a chance to
37 increment, since EDAC will panic the system
38
39What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count
40Date: January 2006
41Contact: linux-edac@vger.kernel.org
42Description: This attribute file displays the number of UEs that have
43 occurred on this memory controller with no information as to
44 which DIMM slot is having errors.
45
46What: /sys/devices/system/edac/mc/mc*/ce_count
47Date: January 2006
48Contact: linux-edac@vger.kernel.org
49Description: This attribute file displays the total count of correctable
50 errors that have occurred on this memory controller. This
51 count is very important to examine. CEs provide early
52 indications that a DIMM is beginning to fail. This count
53 field should be monitored for non-zero values and report
54 such information to the system administrator.
55
56What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count
57Date: January 2006
58Contact: linux-edac@vger.kernel.org
59Description: This attribute file displays the number of CEs that
60 have occurred on this memory controller wherewith no
61 information as to which DIMM slot is having errors. Memory is
62 handicapped, but operational, yet no information is available
63 to indicate which slot the failing memory is in. This count
64 field should be also be monitored for non-zero values.
65
66What: /sys/devices/system/edac/mc/mc*/sdram_scrub_rate
67Date: February 2007
68Contact: linux-edac@vger.kernel.org
69Description: Read/Write attribute file that controls memory scrubbing.
70 The scrubbing rate used by the memory controller is set by
71 writing a minimum bandwidth in bytes/sec to the attribute file.
72 The rate will be translated to an internal value that gives at
73 least the specified rate.
74 Reading the file will return the actual scrubbing rate employed.
75 If configuration fails or memory scrubbing is not implemented,
76 the value of the attribute file will be -1.
77
78What: /sys/devices/system/edac/mc/mc*/max_location
79Date: April 2012
80Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
81 linux-edac@vger.kernel.org
82Description: This attribute file displays the information about the last
83 available memory slot in this memory controller. It is used by
84 userspace tools in order to display the memory filling layout.
85
86What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/size
87Date: April 2012
88Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
89 linux-edac@vger.kernel.org
90Description: This attribute file will display the size of dimm or rank.
91 For dimm*/size, this is the size, in MB of the DIMM memory
92 stick. For rank*/size, this is the size, in MB for one rank
93 of the DIMM memory stick. On single rank memories (1R), this
94 is also the total size of the dimm. On dual rank (2R) memories,
95 this is half the size of the total DIMM memories.
96
97What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_dev_type
98Date: April 2012
99Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
100 linux-edac@vger.kernel.org
101Description: This attribute file will display what type of DRAM device is
102 being utilized on this DIMM (x1, x2, x4, x8, ...).
103
104What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_edac_mode
105Date: April 2012
106Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
107 linux-edac@vger.kernel.org
108Description: This attribute file will display what type of Error detection
109 and correction is being utilized. For example: S4ECD4ED would
110 mean a Chipkill with x4 DRAM.
111
112What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_label
113Date: April 2012
114Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
115 linux-edac@vger.kernel.org
116Description: This control file allows this DIMM to have a label assigned
117 to it. With this label in the module, when errors occur
118 the output can provide the DIMM label in the system log.
119 This becomes vital for panic events to isolate the
120 cause of the UE event.
121 DIMM Labels must be assigned after booting, with information
122 that correctly identifies the physical slot with its
123 silk screen label. This information is currently very
124 motherboard specific and determination of this information
125 must occur in userland at this time.
126
127What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_location
128Date: April 2012
129Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
130 linux-edac@vger.kernel.org
131Description: This attribute file will display the location (csrow/channel,
132 branch/channel/slot or channel/slot) of the dimm or rank.
133
134What: /sys/devices/system/edac/mc/mc*/(dimm|rank)*/dimm_mem_type
135Date: April 2012
136Contact: Mauro Carvalho Chehab <mchehab@redhat.com>
137 linux-edac@vger.kernel.org
138Description: This attribute file will display what type of memory is
139 currently on this csrow. Normally, either buffered or
140 unbuffered memory (for example, Unbuffered-DDR3).
diff --git a/Documentation/ABI/testing/sysfs-devices-firmware_node b/Documentation/ABI/testing/sysfs-devices-firmware_node
deleted file mode 100644
index 46badc9ea28..00000000000
--- a/Documentation/ABI/testing/sysfs-devices-firmware_node
+++ /dev/null
@@ -1,17 +0,0 @@
1What: /sys/devices/.../firmware_node/
2Date: September 2012
3Contact: <>
4Description:
5 The /sys/devices/.../firmware_node directory contains attributes
6 allowing the user space to check and modify some firmware
7 related properties of given device.
8
9What: /sys/devices/.../firmware_node/description
10Date: September 2012
11Contact: Lance Ortiz <lance.ortiz@hp.com>
12Description:
13 The /sys/devices/.../firmware/description attribute contains a string
14 that describes the device as provided by the _STR method in the ACPI
15 namespace. This attribute is read-only. If the device does not have
16 an _STR method associated with it in the ACPI namespace, this
17 attribute is not present.
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 @@
1What: /sys/devices/platform/docg3/f[0-3]_dps[01]_is_keylocked
2Date: November 2011
3KernelVersion: 3.3
4Contact: Robert Jarzmik <robert.jarzmik@free.fr>
5Description:
6 Show whether the floor (0 to 4), protection area (0 or 1) is
7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
8 which can cover any part of it, block aligned, called DPS.
9 The protection has information embedded whether it blocks reads,
10 writes or both.
11 The result is:
12 0 -> the DPS is not keylocked
13 1 -> the DPS is keylocked
14Users: None identified so far.
15
16What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key
17Date: November 2011
18KernelVersion: 3.3
19Contact: Robert Jarzmik <robert.jarzmik@free.fr>
20Description:
21 Enter the protection key for the floor (0 to 4), protection area
22 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
23 which can cover any part of it, block aligned, called DPS.
24 The protection has information embedded whether it blocks reads,
25 writes or both.
26 The protection key is a string of 8 bytes (value 0-255).
27 Entering the correct value toggle the lock, and can be observed
28 through f[0-3]_dps[01]_is_keylocked.
29 Possible values are:
30 - 8 bytes
31 Typical values are:
32 - "00000000"
33 - "12345678"
34Users: None identified so far.
diff --git a/Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb b/Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb
deleted file mode 100644
index 2107082426d..00000000000
--- a/Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb
+++ /dev/null
@@ -1,44 +0,0 @@
1What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha
2Date: May 2012
3Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
4Description:
5 This file is only available on fb[0-9] devices corresponding
6 to overlay planes.
7
8 Stores the alpha blending value for the overlay. Values range
9 from 0 (transparent) to 255 (opaque). The value is ignored if
10 the mode is not set to Alpha Blending.
11
12What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode
13Date: May 2012
14Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
15Description:
16 This file is only available on fb[0-9] devices corresponding
17 to overlay planes.
18
19 Selects the composition mode for the overlay. Possible values
20 are
21
22 0 - Alpha Blending
23 1 - ROP3
24
25What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position
26Date: May 2012
27Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
28Description:
29 This file is only available on fb[0-9] devices corresponding
30 to overlay planes.
31
32 Stores the x,y overlay position on the display in pixels. The
33 position format is `[0-9]+,[0-9]+'.
34
35What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3
36Date: May 2012
37Contact: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
38Description:
39 This file is only available on fb[0-9] devices corresponding
40 to overlay planes.
41
42 Stores the raster operation (ROP3) for the overlay. Values
43 range from 0 to 255. The value is ignored if the mode is not
44 set to ROP3.
diff --git a/Documentation/ABI/testing/sysfs-devices-power b/Documentation/ABI/testing/sysfs-devices-power
index 9d43e767084..8ffbc25376a 100644
--- a/Documentation/ABI/testing/sysfs-devices-power
+++ b/Documentation/ABI/testing/sysfs-devices-power
@@ -96,26 +96,16 @@ Description:
96 is read-only. If the device is not enabled to wake up the 96 is read-only. If the device is not enabled to wake up the
97 system from sleep states, this attribute is not present. 97 system from sleep states, this attribute is not present.
98 98
99What: /sys/devices/.../power/wakeup_abort_count 99What: /sys/devices/.../power/wakeup_hit_count
100Date: February 2012 100Date: September 2010
101Contact: Rafael J. Wysocki <rjw@sisk.pl> 101Contact: Rafael J. Wysocki <rjw@sisk.pl>
102Description: 102Description:
103 The /sys/devices/.../wakeup_abort_count attribute contains the 103 The /sys/devices/.../wakeup_hit_count attribute contains the
104 number of times the processing of a wakeup event associated with 104 number of times the processing of a wakeup event associated with
105 the device might have aborted system transition into a sleep 105 the device might prevent the system from entering a sleep state.
106 state in progress. This attribute is read-only. If the device 106 This attribute is read-only. If the device is not enabled to
107 is not enabled to wake up the system from sleep states, this 107 wake up the system from sleep states, this attribute is not
108 attribute is not present. 108 present.
109
110What: /sys/devices/.../power/wakeup_expire_count
111Date: February 2012
112Contact: Rafael J. Wysocki <rjw@sisk.pl>
113Description:
114 The /sys/devices/.../wakeup_expire_count attribute contains the
115 number of times a wakeup event associated with the device has
116 been reported with a timeout that expired. This attribute is
117 read-only. If the device is not enabled to wake up the system
118 from sleep states, this attribute is not present.
119 109
120What: /sys/devices/.../power/wakeup_active 110What: /sys/devices/.../power/wakeup_active
121Date: September 2010 111Date: September 2010
@@ -158,17 +148,6 @@ Description:
158 not enabled to wake up the system from sleep states, this 148 not enabled to wake up the system from sleep states, this
159 attribute is not present. 149 attribute is not present.
160 150
161What: /sys/devices/.../power/wakeup_prevent_sleep_time_ms
162Date: February 2012
163Contact: Rafael J. Wysocki <rjw@sisk.pl>
164Description:
165 The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute
166 contains the total time the device has been preventing
167 opportunistic transitions to sleep states from occurring.
168 This attribute is read-only. If the device is not enabled to
169 wake up the system from sleep states, this attribute is not
170 present.
171
172What: /sys/devices/.../power/autosuspend_delay_ms 151What: /sys/devices/.../power/autosuspend_delay_ms
173Date: September 2010 152Date: September 2010
174Contact: Alan Stern <stern@rowland.harvard.edu> 153Contact: Alan Stern <stern@rowland.harvard.edu>
@@ -186,52 +165,3 @@ Description:
186 165
187 Not all drivers support this attribute. If it isn't supported, 166 Not all drivers support this attribute. If it isn't supported,
188 attempts to read or write it will yield I/O errors. 167 attempts to read or write it will yield I/O errors.
189
190What: /sys/devices/.../power/pm_qos_latency_us
191Date: March 2012
192Contact: Rafael J. Wysocki <rjw@sisk.pl>
193Description:
194 The /sys/devices/.../power/pm_qos_resume_latency_us attribute
195 contains the PM QoS resume latency limit for the given device,
196 which is the maximum allowed time it can take to resume the
197 device, after it has been suspended at run time, from a resume
198 request to the moment the device will be ready to process I/O,
199 in microseconds. If it is equal to 0, however, this means that
200 the PM QoS resume latency may be arbitrary.
201
202 Not all drivers support this attribute. If it isn't supported,
203 it is not present.
204
205 This attribute has no effect on system-wide suspend/resume and
206 hibernation.
207
208What: /sys/devices/.../power/pm_qos_no_power_off
209Date: September 2012
210Contact: Rafael J. Wysocki <rjw@sisk.pl>
211Description:
212 The /sys/devices/.../power/pm_qos_no_power_off attribute
213 is used for manipulating the PM QoS "no power off" flag. If
214 set, this flag indicates to the kernel that power should not
215 be removed entirely from the device.
216
217 Not all drivers support this attribute. If it isn't supported,
218 it is not present.
219
220 This attribute has no effect on system-wide suspend/resume and
221 hibernation.
222
223What: /sys/devices/.../power/pm_qos_remote_wakeup
224Date: September 2012
225Contact: Rafael J. Wysocki <rjw@sisk.pl>
226Description:
227 The /sys/devices/.../power/pm_qos_remote_wakeup attribute
228 is used for manipulating the PM QoS "remote wakeup required"
229 flag. If set, this flag indicates to the kernel that the
230 device is a source of user events that have to be signaled from
231 its low-power states.
232
233 Not all drivers support this attribute. If it isn't supported,
234 it is not present.
235
236 This attribute has no effect on system-wide suspend/resume and
237 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 @@
1What: /sys/devices/socX
2Date: January 2012
3contact: Lee Jones <lee.jones@linaro.org>
4Description:
5 The /sys/devices/ directory contains a sub-directory for each
6 System-on-Chip (SoC) device on a running platform. Information
7 regarding each SoC can be obtained by reading sysfs files. This
8 functionality is only available if implemented by the platform.
9
10 The directory created for each SoC will also house information
11 about devices which are commonly contained in /sys/devices/platform.
12 It has been agreed that if an SoC device exists, its supported
13 devices would be better suited to appear as children of that SoC.
14
15What: /sys/devices/socX/machine
16Date: January 2012
17contact: Lee Jones <lee.jones@linaro.org>
18Description:
19 Read-only attribute common to all SoCs. Contains the SoC machine
20 name (e.g. Ux500).
21
22What: /sys/devices/socX/family
23Date: January 2012
24contact: Lee Jones <lee.jones@linaro.org>
25Description:
26 Read-only attribute common to all SoCs. Contains SoC family name
27 (e.g. DB8500).
28
29What: /sys/devices/socX/soc_id
30Date: January 2012
31contact: Lee Jones <lee.jones@linaro.org>
32Description:
33 Read-only attribute supported by most SoCs. In the case of
34 ST-Ericsson's chips this contains the SoC serial number.
35
36What: /sys/devices/socX/revision
37Date: January 2012
38contact: Lee Jones <lee.jones@linaro.org>
39Description:
40 Read-only attribute supported by most SoCs. Contains the SoC's
41 manufacturing revision number.
42
43What: /sys/devices/socX/process
44Date: January 2012
45contact: Lee Jones <lee.jones@linaro.org>
46Description:
47 Read-only attribute supported ST-Ericsson's silicon. Contains the
48 the process by which the silicon chip was manufactured.
49
50What: /sys/bus/soc
51Date: January 2012
52contact: Lee Jones <lee.jones@linaro.org>
53Description:
54 The /sys/bus/soc/ directory contains the usual sub-folders
55 expected under most buses. /sys/bus/soc/devices is of particular
56 interest, as it contains a symlink for each SoC device found on
57 the system. Each symlink points back into the aforementioned
58 /sys/devices/socX devices.
diff --git a/Documentation/ABI/testing/sysfs-devices-sun b/Documentation/ABI/testing/sysfs-devices-sun
deleted file mode 100644
index 86be9848a77..00000000000
--- a/Documentation/ABI/testing/sysfs-devices-sun
+++ /dev/null
@@ -1,14 +0,0 @@
1Whatt: /sys/devices/.../sun
2Date: October 2012
3Contact: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
4Description:
5 The file contains a Slot-unique ID which provided by the _SUN
6 method in the ACPI namespace. The value is written in Advanced
7 Configuration and Power Interface Specification as follows:
8
9 "The _SUN value is required to be unique among the slots of
10 the same type. It is also recommended that this number match
11 the slot number printed on the physical slot whenever possible."
12
13 So reading the sysfs file, we can identify a physical position
14 of the slot in the system.
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 6943133afcb..e7be75b96e4 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -9,6 +9,31 @@ Description:
9 9
10 /sys/devices/system/cpu/cpu#/ 10 /sys/devices/system/cpu/cpu#/
11 11
12What: /sys/devices/system/cpu/sched_mc_power_savings
13 /sys/devices/system/cpu/sched_smt_power_savings
14Date: June 2006
15Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
16Description: Discover and adjust the kernel's multi-core scheduler support.
17
18 Possible values are:
19
20 0 - No power saving load balance (default value)
21 1 - Fill one thread/core/package first for long running threads
22 2 - Also bias task wakeups to semi-idle cpu package for power
23 savings
24
25 sched_mc_power_savings is dependent upon SCHED_MC, which is
26 itself architecture dependent.
27
28 sched_smt_power_savings is dependent upon SCHED_SMT, which
29 is itself architecture dependent.
30
31 The two files are independent of each other. It is possible
32 that one file may be present without the other.
33
34 Introduced by git commit 5c45bf27.
35
36
12What: /sys/devices/system/cpu/kernel_max 37What: /sys/devices/system/cpu/kernel_max
13 /sys/devices/system/cpu/offline 38 /sys/devices/system/cpu/offline
14 /sys/devices/system/cpu/online 39 /sys/devices/system/cpu/online
@@ -176,14 +201,3 @@ Description: Disable L3 cache indices
176 All AMD processors with L3 caches provide this functionality. 201 All AMD processors with L3 caches provide this functionality.
177 For details, see BKDGs at 202 For details, see BKDGs at
178 http://developer.amd.com/documentation/guides/Pages/default.aspx 203 http://developer.amd.com/documentation/guides/Pages/default.aspx
179
180
181What: /sys/devices/system/cpu/cpufreq/boost
182Date: August 2012
183Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
184Description: Processor frequency boosting control
185
186 This switch controls the boost setting for the whole system.
187 Boosting allows the CPU and the firmware to run at a frequency
188 beyound it's nominal limit.
189 More details can be found in Documentation/cpu-freq/boost.txt
diff --git a/Documentation/ABI/testing/sysfs-devices-system-xen_cpu b/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
deleted file mode 100644
index 9ca02fb2d49..00000000000
--- a/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
+++ /dev/null
@@ -1,20 +0,0 @@
1What: /sys/devices/system/xen_cpu/
2Date: May 2012
3Contact: Liu, Jinsong <jinsong.liu@intel.com>
4Description:
5 A collection of global/individual Xen physical cpu attributes
6
7 Individual physical cpu attributes are contained in
8 subdirectories named by the Xen's logical cpu number, e.g.:
9 /sys/devices/system/xen_cpu/xen_cpu#/
10
11
12What: /sys/devices/system/xen_cpu/xen_cpu#/online
13Date: May 2012
14Contact: Liu, Jinsong <jinsong.liu@intel.com>
15Description:
16 Interface to online/offline Xen physical cpus
17
18 When running under Xen platform, it provide user interface
19 to online/offline physical cpus, except cpu0 due to several
20 logic restrictions and assumptions.
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd b/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
deleted file mode 100644
index 57b92cbdcea..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
+++ /dev/null
@@ -1,38 +0,0 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_to_select
2Date: July 2011
3Contact: linux-input@vger.kernel.org
4Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be
5 is being controlled by press_speed.
6 Values are 0 or 1.
7
8What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging
9Date: July 2011
10Contact: linux-input@vger.kernel.org
11Description: If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.
12 Values are 0 or 1.
13
14What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select
15Date: July 2011
16Contact: linux-input@vger.kernel.org
17Description: For details regarding this setting please refer to http://www.pc.ibm.com/ww/healthycomputing/trkpntb.html
18 Values are 0 or 1.
19
20What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/select_right
21Date: July 2011
22Contact: linux-input@vger.kernel.org
23Description: This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate
24 a left or right mouse button click.
25 Values are 0 or 1.
26
27What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity
28Date: July 2011
29Contact: linux-input@vger.kernel.org
30Description: This file contains the trackpoint sensitivity.
31 Values are decimal integers from 1 (lowest sensitivity) to 255 (highest sensitivity).
32
33What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/press_speed
34Date: July 2011
35Contact: linux-input@vger.kernel.org
36Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.
37 Values are decimal integers from 1 (slowest) to 255 (fastest).
38
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 @@
1What: /sys/module/hid_logitech/drivers/hid:logitech/<dev>/range.
2Date: July 2011
3KernelVersion: 3.2
4Contact: Michal Malý <madcatxster@gmail.com>
5Description: 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-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 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/quirks
2Date: November 2011
3Contact: Benjamin Tissoires <benjamin.tissoires@gmail.com>
4Description: The integer value of this attribute corresponds to the
5 quirks actually in place to handle the device's protocol.
6 When read, this attribute returns the current settings (see
7 MT_QUIRKS_* in hid-multitouch.c).
8 When written this attribute change on the fly the quirks, then
9 the protocol to handle the device.
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 9eca5a182e6..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-isku
+++ /dev/null
@@ -1,143 +0,0 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/actual_profile
2Date: June 2011
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: The integer value of this attribute ranges from 0-4.
5 When read, this attribute returns the number of the actual
6 profile. This value is persistent, so its equivalent to the
7 profile that's active when the device is powered on next time.
8 When written, this file sets the number of the startup profile
9 and the device activates this profile immediately.
10Users: http://roccat.sourceforge.net
11
12What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/info
13Date: June 2011
14Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
15Description: When read, this file returns general data like firmware version.
16 The data is 6 bytes long.
17 This file is readonly.
18Users: http://roccat.sourceforge.net
19
20What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/key_mask
21Date: June 2011
22Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
23Description: When written, this file lets one deactivate certain keys like
24 windows and application keys, to prevent accidental presses.
25 Profile number for which this settings occur is included in
26 written data. The data has to be 6 bytes long.
27 Before reading this file, control has to be written to select
28 which profile to read.
29Users: http://roccat.sourceforge.net
30
31What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_capslock
32Date: June 2011
33Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
34Description: When written, this file lets one set the function of the
35 capslock key for a specific profile. Profile number is included
36 in written data. The data has to be 6 bytes long.
37 Before reading this file, control has to be written to select
38 which profile to read.
39Users: http://roccat.sourceforge.net
40
41What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_easyzone
42Date: June 2011
43Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
44Description: When written, this file lets one set the function of the
45 easyzone keys for a specific profile. Profile number is included
46 in written data. The data has to be 65 bytes long.
47 Before reading this file, control has to be written to select
48 which profile to read.
49Users: http://roccat.sourceforge.net
50
51What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_function
52Date: June 2011
53Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
54Description: When written, this file lets one set the function of the
55 function keys for a specific profile. Profile number is included
56 in written data. The data has to be 41 bytes long.
57 Before reading this file, control has to be written to select
58 which profile to read.
59Users: http://roccat.sourceforge.net
60
61What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_macro
62Date: June 2011
63Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
64Description: When written, this file lets one set the function of the macro
65 keys for a specific profile. Profile number is included in
66 written data. The data has to be 35 bytes long.
67 Before reading this file, control has to be written to select
68 which profile to read.
69Users: http://roccat.sourceforge.net
70
71What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_media
72Date: June 2011
73Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
74Description: When written, this file lets one set the function of the media
75 keys for a specific profile. Profile number is included in
76 written data. The data has to be 29 bytes long.
77 Before reading this file, control has to be written to select
78 which profile to read.
79Users: http://roccat.sourceforge.net
80
81What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_thumbster
82Date: June 2011
83Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
84Description: When written, this file lets one set the function of the
85 thumbster keys for a specific profile. Profile number is included
86 in written data. The data has to be 23 bytes long.
87 Before reading this file, control has to be written to select
88 which profile to read.
89Users: http://roccat.sourceforge.net
90
91What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/last_set
92Date: June 2011
93Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
94Description: When written, this file lets one set the time in secs since
95 epoch in which the last configuration took place.
96 The data has to be 20 bytes long.
97Users: http://roccat.sourceforge.net
98
99What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/light
100Date: June 2011
101Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
102Description: When written, this file lets one set the backlight intensity for
103 a specific profile. Profile number is included in written data.
104 The data has to be 10 bytes long.
105 Before reading this file, control has to be written to select
106 which profile to read.
107Users: http://roccat.sourceforge.net
108
109What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/macro
110Date: June 2011
111Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
112Description: When written, this file lets one store macros with max 500
113 keystrokes for a specific button for a specific profile.
114 Button and profile numbers are included in written data.
115 The data has to be 2083 bytes long.
116 Before reading this file, control has to be written to select
117 which profile and key to read.
118Users: http://roccat.sourceforge.net
119
120What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/reset
121Date: November 2012
122Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
123Description: When written, this file lets one reset the device.
124 The data has to be 3 bytes long.
125 This file is writeonly.
126Users: http://roccat.sourceforge.net
127
128What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/control
129Date: June 2011
130Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
131Description: When written, this file lets one select which data from which
132 profile will be read next. The data has to be 3 bytes long.
133 This file is writeonly.
134Users: http://roccat.sourceforge.net
135
136What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/talk
137Date: June 2011
138Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
139Description: When written, this file lets one trigger easyshift functionality
140 from the host.
141 The data has to be 16 bytes long.
142 This file is writeonly.
143Users: http://roccat.sourceforge.net
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus b/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus
index 7bd776f9c3c..65e6e5dd67e 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-koneplus
@@ -9,12 +9,15 @@ Description: The integer value of this attribute ranges from 0-4.
9 and the mouse activates this profile immediately. 9 and the mouse activates this profile immediately.
10Users: http://roccat.sourceforge.net 10Users: http://roccat.sourceforge.net
11 11
12What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/info 12What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/firmware_version
13Date: November 2012 13Date: October 2010
14Contact: Stefan Achatz <erazor_de@users.sourceforge.net> 14Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
15Description: When read, this file returns general data like firmware version. 15Description: When read, this file returns the raw integer version number of the
16 When written, the device can be reset. 16 firmware reported by the mouse. Using the integer value eases
17 The data is 8 bytes long. 17 further usage in other programs. To receive the real version
18 number the decimal point has to be shifted 2 positions to the
19 left. E.g. a returned value of 121 means 1.21
20 This file is readonly.
18Users: http://roccat.sourceforge.net 21Users: http://roccat.sourceforge.net
19 22
20What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/macro 23What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/macro
@@ -39,8 +42,18 @@ Description: The mouse can store 5 profiles which can be switched by the
39 The mouse will reject invalid data. 42 The mouse will reject invalid data.
40 Which profile to write is determined by the profile number 43 Which profile to write is determined by the profile number
41 contained in the data. 44 contained in the data.
42 Before reading this file, control has to be written to select 45 This file is writeonly.
43 which profile to read. 46Users: http://roccat.sourceforge.net
47
48What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_buttons
49Date: August 2010
50Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
51Description: The mouse can store 5 profiles which can be switched by the
52 press of a button. A profile is split in settings and buttons.
53 profile_buttons holds information about button layout.
54 When read, these files return the respective profile buttons.
55 The returned data is 77 bytes in size.
56 This file is readonly.
44Users: http://roccat.sourceforge.net 57Users: http://roccat.sourceforge.net
45 58
46What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_settings 59What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_settings
@@ -55,8 +68,19 @@ Description: The mouse can store 5 profiles which can be switched by the
55 The mouse will reject invalid data. 68 The mouse will reject invalid data.
56 Which profile to write is determined by the profile number 69 Which profile to write is determined by the profile number
57 contained in the data. 70 contained in the data.
58 Before reading this file, control has to be written to select 71 This file is writeonly.
59 which profile to read. 72Users: http://roccat.sourceforge.net
73
74What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_settings
75Date: August 2010
76Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
77Description: The mouse can store 5 profiles which can be switched by the
78 press of a button. A profile is split in settings and buttons.
79 profile_settings holds information like resolution, sensitivity
80 and light effects.
81 When read, these files return the respective profile settings.
82 The returned data is 43 bytes in size.
83 This file is readonly.
60Users: http://roccat.sourceforge.net 84Users: http://roccat.sourceforge.net
61 85
62What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/sensor 86What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/sensor
@@ -80,9 +104,9 @@ What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-
80Date: October 2010 104Date: October 2010
81Contact: Stefan Achatz <erazor_de@users.sourceforge.net> 105Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
82Description: When written a calibration process for the tracking control unit 106Description: When written a calibration process for the tracking control unit
83 can be initiated/cancelled. Also lets one read/write sensor 107 can be initiated/cancelled.
84 registers. 108 The data has to be 3 bytes long.
85 The data has to be 4 bytes long. 109 This file is writeonly.
86Users: http://roccat.sourceforge.net 110Users: http://roccat.sourceforge.net
87 111
88What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu_image 112What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu_image
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus b/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus
index a10404f15a5..20f937c9d84 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-kovaplus
@@ -1,3 +1,12 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_cpi
2Date: January 2011
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: The integer value of this attribute ranges from 1-4.
5 When read, this attribute returns the number of the active
6 cpi level.
7 This file is readonly.
8Users: http://roccat.sourceforge.net
9
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_profile 10What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_profile
2Date: January 2011 11Date: January 2011
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net> 12Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
@@ -9,12 +18,33 @@ Description: The integer value of this attribute ranges from 0-4.
9 active when the mouse is powered on. 18 active when the mouse is powered on.
10Users: http://roccat.sourceforge.net 19Users: http://roccat.sourceforge.net
11 20
12What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/info 21What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x
13Date: November 2012 22Date: January 2011
14Contact: Stefan Achatz <erazor_de@users.sourceforge.net> 23Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
15Description: When read, this file returns general data like firmware version. 24Description: The integer value of this attribute ranges from 1-10.
16 When written, the device can be reset. 25 When read, this attribute returns the number of the actual
17 The data is 6 bytes long. 26 sensitivity in x direction.
27 This file is readonly.
28Users: http://roccat.sourceforge.net
29
30What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_y
31Date: January 2011
32Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
33Description: The integer value of this attribute ranges from 1-10.
34 When read, this attribute returns the number of the actual
35 sensitivity in y direction.
36 This file is readonly.
37Users: http://roccat.sourceforge.net
38
39What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/firmware_version
40Date: January 2011
41Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
42Description: When read, this file returns the raw integer version number of the
43 firmware reported by the mouse. Using the integer value eases
44 further usage in other programs. To receive the real version
45 number the decimal point has to be shifted 2 positions to the
46 left. E.g. a returned value of 121 means 1.21
47 This file is readonly.
18Users: http://roccat.sourceforge.net 48Users: http://roccat.sourceforge.net
19 49
20What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_buttons 50What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_buttons
@@ -28,8 +58,18 @@ Description: The mouse can store 5 profiles which can be switched by the
28 The mouse will reject invalid data. 58 The mouse will reject invalid data.
29 Which profile to write is determined by the profile number 59 Which profile to write is determined by the profile number
30 contained in the data. 60 contained in the data.
31 Before reading this file, control has to be written to select 61 This file is writeonly.
32 which profile to read. 62Users: http://roccat.sourceforge.net
63
64What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_buttons
65Date: January 2011
66Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
67Description: The mouse can store 5 profiles which can be switched by the
68 press of a button. A profile is split in settings and buttons.
69 profile_buttons holds information about button layout.
70 When read, these files return the respective profile buttons.
71 The returned data is 23 bytes in size.
72 This file is readonly.
33Users: http://roccat.sourceforge.net 73Users: http://roccat.sourceforge.net
34 74
35What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_settings 75What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_settings
@@ -44,6 +84,17 @@ Description: The mouse can store 5 profiles which can be switched by the
44 The mouse will reject invalid data. 84 The mouse will reject invalid data.
45 Which profile to write is determined by the profile number 85 Which profile to write is determined by the profile number
46 contained in the data. 86 contained in the data.
47 Before reading this file, control has to be written to select 87 This file is writeonly.
48 which profile to read. 88Users: http://roccat.sourceforge.net
89
90What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_settings
91Date: January 2011
92Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
93Description: The mouse can store 5 profiles which can be switched by the
94 press of a button. A profile is split in settings and buttons.
95 profile_settings holds information like resolution, sensitivity
96 and light effects.
97 When read, these files return the respective profile settings.
98 The returned data is 16 bytes in size.
99 This file is readonly.
49Users: http://roccat.sourceforge.net 100Users: http://roccat.sourceforge.net
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-lua b/Documentation/ABI/testing/sysfs-driver-hid-roccat-lua
deleted file mode 100644
index 31c6c4c8ba2..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-lua
+++ /dev/null
@@ -1,7 +0,0 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/control
2Date: October 2012
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: When written, cpi, button and light settings can be configured.
5 When read, actual cpi setting and sensor data are returned.
6 The data has to be 8 bytes long.
7Users: http://roccat.sourceforge.net
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra b/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
index 9fa9de30d14..3f8de50e4ff 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-pyra
@@ -1,9 +1,37 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/info 1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_cpi
2Date: November 2012 2Date: August 2010
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: It is possible to switch the cpi setting of the mouse with the
5 press of a button.
6 When read, this file returns the raw number of the actual cpi
7 setting reported by the mouse. This number has to be further
8 processed to receive the real dpi value.
9
10 VALUE DPI
11 1 400
12 2 800
13 4 1600
14
15 This file is readonly.
16Users: http://roccat.sourceforge.net
17
18What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_profile
19Date: August 2010
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net> 20Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: When read, this file returns general data like firmware version. 21Description: When read, this file returns the number of the actual profile in
5 When written, the device can be reset. 22 range 0-4.
6 The data is 6 bytes long. 23 This file is readonly.
24Users: http://roccat.sourceforge.net
25
26What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/firmware_version
27Date: August 2010
28Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
29Description: When read, this file returns the raw integer version number of the
30 firmware reported by the mouse. Using the integer value eases
31 further usage in other programs. To receive the real version
32 number the decimal point has to be shifted 2 positions to the
33 left. E.g. a returned value of 138 means 1.38
34 This file is readonly.
7Users: http://roccat.sourceforge.net 35Users: http://roccat.sourceforge.net
8 36
9What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_settings 37What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_settings
@@ -18,8 +46,19 @@ Description: The mouse can store 5 profiles which can be switched by the
18 The mouse will reject invalid data. 46 The mouse will reject invalid data.
19 Which profile to write is determined by the profile number 47 Which profile to write is determined by the profile number
20 contained in the data. 48 contained in the data.
21 Before reading this file, control has to be written to select 49 This file is writeonly.
22 which profile to read. 50Users: http://roccat.sourceforge.net
51
52What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_settings
53Date: August 2010
54Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
55Description: The mouse can store 5 profiles which can be switched by the
56 press of a button. A profile is split in settings and buttons.
57 profile_settings holds information like resolution, sensitivity
58 and light effects.
59 When read, these files return the respective profile settings.
60 The returned data is 13 bytes in size.
61 This file is readonly.
23Users: http://roccat.sourceforge.net 62Users: http://roccat.sourceforge.net
24 63
25What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_buttons 64What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_buttons
@@ -33,8 +72,27 @@ Description: The mouse can store 5 profiles which can be switched by the
33 The mouse will reject invalid data. 72 The mouse will reject invalid data.
34 Which profile to write is determined by the profile number 73 Which profile to write is determined by the profile number
35 contained in the data. 74 contained in the data.
36 Before reading this file, control has to be written to select 75 This file is writeonly.
37 which profile to read. 76Users: http://roccat.sourceforge.net
77
78What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_buttons
79Date: August 2010
80Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
81Description: The mouse can store 5 profiles which can be switched by the
82 press of a button. A profile is split in settings and buttons.
83 profile_buttons holds information about button layout.
84 When read, these files return the respective profile buttons.
85 The returned data is 19 bytes in size.
86 This file is readonly.
87Users: http://roccat.sourceforge.net
88
89What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/startup_profile
90Date: August 2010
91Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
92Description: The integer value of this attribute ranges from 0-4.
93 When read, this attribute returns the number of the profile
94 that's active when the mouse is powered on.
95 This file is readonly.
38Users: http://roccat.sourceforge.net 96Users: http://roccat.sourceforge.net
39 97
40What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/settings 98What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/settings
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu b/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
deleted file mode 100644
index f1e02a98bd9..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
+++ /dev/null
@@ -1,76 +0,0 @@
1What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons
2Date: Mai 2012
3Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
4Description: The mouse can store 5 profiles which can be switched by the
5 press of a button. A profile is split into general settings and
6 button settings. buttons holds informations about button layout.
7 When written, this file lets one write the respective profile
8 buttons to the mouse. The data has to be 47 bytes long.
9 The mouse will reject invalid data.
10 Which profile to write is determined by the profile number
11 contained in the data.
12 Before reading this file, control has to be written to select
13 which profile to read.
14Users: http://roccat.sourceforge.net
15
16What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
17Date: Mai 2012
18Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
19Description: When written, this file lets one select which data from which
20 profile will be read next. The data has to be 3 bytes long.
21 This file is writeonly.
22Users: http://roccat.sourceforge.net
23
24What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/general
25Date: Mai 2012
26Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
27Description: The mouse can store 5 profiles which can be switched by the
28 press of a button. A profile is split into general settings and
29 button settings. profile holds informations like resolution, sensitivity
30 and light effects.
31 When written, this file lets one write the respective profile
32 settings back to the mouse. The data has to be 43 bytes long.
33 The mouse will reject invalid data.
34 Which profile to write is determined by the profile number
35 contained in the data.
36 This file is writeonly.
37Users: http://roccat.sourceforge.net
38
39What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
40Date: Mai 2012
41Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
42Description: When read, this file returns general data like firmware version.
43 When written, the device can be reset.
44 The data is 8 bytes long.
45Users: http://roccat.sourceforge.net
46
47What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
48Date: Mai 2012
49Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
50Description: When written, this file lets one store macros with max 500
51 keystrokes for a specific button for a specific profile.
52 Button and profile numbers are included in written data.
53 The data has to be 2083 bytes long.
54 Before reading this file, control has to be written to select
55 which profile and key to read.
56Users: http://roccat.sourceforge.net
57
58What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
59Date: Mai 2012
60Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
61Description: The mouse can store 5 profiles which can be switched by the
62 press of a button. profile holds number of actual profile.
63 This value is persistent, so its value determines the profile
64 that's active when the mouse is powered on next time.
65 When written, the mouse activates the set profile immediately.
66 The data has to be 3 bytes long.
67 The mouse will reject invalid data.
68Users: http://roccat.sourceforge.net
69
70What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/sensor
71Date: July 2012
72Contact: Stefan Achatz <erazor_de@users.sourceforge.net>
73Description: The mouse has a Avago ADNS-3090 sensor.
74 This file allows reading and writing of the mouse sensors registers.
75 The data has to be 4 bytes long.
76Users: http://roccat.sourceforge.net
diff --git a/Documentation/ABI/testing/sysfs-driver-hid-wiimote b/Documentation/ABI/testing/sysfs-driver-hid-wiimote
index 3d98009f447..5d5a16ea57c 100644
--- a/Documentation/ABI/testing/sysfs-driver-hid-wiimote
+++ b/Documentation/ABI/testing/sysfs-driver-hid-wiimote
@@ -8,15 +8,3 @@ Contact: David Herrmann <dh.herrmann@googlemail.com>
8Description: Make it possible to set/get current led state. Reading from it 8Description: Make it possible to set/get current led state. Reading from it
9 returns 0 if led is off and 1 if it is on. Writing 0 to it 9 returns 0 if led is off and 1 if it is on. Writing 0 to it
10 disables the led, writing 1 enables it. 10 disables the led, writing 1 enables it.
11
12What: /sys/bus/hid/drivers/wiimote/<dev>/extension
13Date: August 2011
14KernelVersion: 3.2
15Contact: David Herrmann <dh.herrmann@googlemail.com>
16Description: This file contains the currently connected and initialized
17 extensions. It can be one of: none, motionp, nunchuck, classic,
18 motionp+nunchuck, motionp+classic
19 motionp is the official Nintendo Motion+ extension, nunchuck is
20 the official Nintendo Nunchuck extension and classic is the
21 Nintendo Classic Controller extension. The motionp extension can
22 be combined with the other two.
diff --git a/Documentation/ABI/testing/sysfs-driver-ppi b/Documentation/ABI/testing/sysfs-driver-ppi
deleted file mode 100644
index 7d1435bc976..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-ppi
+++ /dev/null
@@ -1,70 +0,0 @@
1What: /sys/devices/pnp0/<bus-num>/ppi/
2Date: August 2012
3Kernel Version: 3.6
4Contact: xiaoyan.zhang@intel.com
5Description:
6 This folder includes the attributes related with PPI (Physical
7 Presence Interface). Only if TPM is supported by BIOS, this
8 folder makes sense. The folder path can be got by command
9 'find /sys/ -name 'pcrs''. For the detail information of PPI,
10 please refer to the PPI specification from
11 http://www.trustedcomputinggroup.org/
12
13What: /sys/devices/pnp0/<bus-num>/ppi/version
14Date: August 2012
15Contact: xiaoyan.zhang@intel.com
16Description:
17 This attribute shows the version of the PPI supported by the
18 platform.
19 This file is readonly.
20
21What: /sys/devices/pnp0/<bus-num>/ppi/request
22Date: August 2012
23Contact: xiaoyan.zhang@intel.com
24Description:
25 This attribute shows the request for an operation to be
26 executed in the pre-OS environment. It is the only input from
27 the OS to the pre-OS environment. The request should be an
28 integer value range from 1 to 160, and 0 means no request.
29 This file can be read and written.
30
31What: /sys/devices/pnp0/00:<bus-num>/ppi/response
32Date: August 2012
33Contact: xiaoyan.zhang@intel.com
34Description:
35 This attribute shows the response to the most recent operation
36 request it acted upon. The format is "<request> <response num>
37 : <response description>".
38 This file is readonly.
39
40What: /sys/devices/pnp0/<bus-num>/ppi/transition_action
41Date: August 2012
42Contact: xiaoyan.zhang@intel.com
43Description:
44 This attribute shows the platform-specific action that should
45 take place in order to transition to the BIOS for execution of
46 a requested operation. The format is "<action num>: <action
47 description>".
48 This file is readonly.
49
50What: /sys/devices/pnp0/<bus-num>/ppi/tcg_operations
51Date: August 2012
52Contact: xiaoyan.zhang@intel.com
53Description:
54 This attribute shows whether it is allowed to request an
55 operation to be executed in the pre-OS environment by the BIOS
56 for the requests defined by TCG, i.e. requests from 1 to 22.
57 The format is "<request> <status num>: <status description>".
58 This attribute is only supported by PPI version 1.2+.
59 This file is readonly.
60
61What: /sys/devices/pnp0/<bus-num>/ppi/vs_operations
62Date: August 2012
63Contact: xiaoyan.zhang@intel.com
64Description:
65 This attribute shows whether it is allowed to request an
66 operation to be executed in the pre-OS environment by the BIOS
67 for the verdor specific requests, i.e. requests from 128 to
68 255. The format is same with tcg_operations. This attribute
69 is also only supported by PPI version 1.2+.
70 This file is readonly.
diff --git a/Documentation/ABI/testing/sysfs-driver-samsung-laptop b/Documentation/ABI/testing/sysfs-driver-samsung-laptop
index 678819a3f8b..0a810231aad 100644
--- a/Documentation/ABI/testing/sysfs-driver-samsung-laptop
+++ b/Documentation/ABI/testing/sysfs-driver-samsung-laptop
@@ -1,7 +1,7 @@
1What: /sys/devices/platform/samsung/performance_level 1What: /sys/devices/platform/samsung/performance_level
2Date: January 1, 2010 2Date: January 1, 2010
3KernelVersion: 2.6.33 3KernelVersion: 2.6.33
4Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 4Contact: Greg Kroah-Hartman <gregkh@suse.de>
5Description: Some Samsung laptops have different "performance levels" 5Description: Some Samsung laptops have different "performance levels"
6 that are can be modified by a function key, and by this 6 that are can be modified by a function key, and by this
7 sysfs file. These values don't always make a whole lot 7 sysfs file. These values don't always make a whole lot
@@ -17,21 +17,3 @@ Description: Some Samsung laptops have different "performance levels"
17 Specifically, not all support the "overclock" option, 17 Specifically, not all support the "overclock" option,
18 and it's still unknown if this value even changes 18 and it's still unknown if this value even changes
19 anything, other than making the user feel a bit better. 19 anything, other than making the user feel a bit better.
20
21What: /sys/devices/platform/samsung/battery_life_extender
22Date: December 1, 2011
23KernelVersion: 3.3
24Contact: Corentin Chary <corentin.chary@gmail.com>
25Description: Max battery charge level can be modified, battery cycle
26 life can be extended by reducing the max battery charge
27 level.
28 0 means normal battery mode (100% charge)
29 1 means battery life extender mode (80% charge)
30
31What: /sys/devices/platform/samsung/usb_charge
32Date: December 1, 2011
33KernelVersion: 3.3
34Contact: Corentin Chary <corentin.chary@gmail.com>
35Description: Use your USB ports to charge devices, even
36 when your laptop is powered off.
37 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 7fc781048b7..00000000000
--- a/Documentation/ABI/testing/sysfs-driver-wacom
+++ /dev/null
@@ -1,95 +0,0 @@
1WWhat: /sys/class/hidraw/hidraw*/device/oled*_img
2Date: June 2012
3Contact: linux-bluetooth@vger.kernel.org
4Description:
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
14What: /sys/class/hidraw/hidraw*/device/speed
15Date: April 2010
16Kernel Version: 2.6.35
17Contact: linux-bluetooth@vger.kernel.org
18Description:
19 The /sys/class/hidraw/hidraw*/device/speed file controls
20 reporting speed of Wacom bluetooth tablet. Reading from
21 this file returns 1 if tablet reports in high speed mode
22 or 0 otherwise. Writing to this file one of these values
23 switches reporting speed.
24
25What: /sys/class/leds/0005\:056A\:00BD.0001\:selector\:*/
26Date: May 2012
27Kernel Version: 3.5
28Contact: linux-bluetooth@vger.kernel.org
29Description:
30 LED selector for Intuos4 WL. There are 4 leds, but only one LED
31 can be lit at a time. Max brightness is 127.
32
33What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led
34Date: August 2011
35Contact: linux-input@vger.kernel.org
36Description:
37 Attribute group for control of the status LEDs and the OLEDs.
38 This attribute group is only available for Intuos 4 M, L,
39 and XL (with LEDs and OLEDs), Intuos 5 (LEDs only), and Cintiq
40 21UX2 and Cintiq 24HD (LEDs only). Therefore its presence
41 implicitly signifies the presence of said LEDs and OLEDs on the
42 tablet device.
43
44What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance
45Date: August 2011
46Contact: linux-input@vger.kernel.org
47Description:
48 Writing to this file sets the status LED luminance (1..127)
49 when the stylus does not touch the tablet surface, and no
50 button is pressed on the stylus. This luminance level is
51 normally lower than the level when a button is pressed.
52
53What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status1_luminance
54Date: August 2011
55Contact: linux-input@vger.kernel.org
56Description:
57 Writing to this file sets the status LED luminance (1..127)
58 when the stylus touches the tablet surface, or any button is
59 pressed on the stylus.
60
61What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led0_select
62Date: August 2011
63Contact: linux-input@vger.kernel.org
64Description:
65 Writing to this file sets which one of the four (for Intuos 4
66 and Intuos 5) or of the right four (for Cintiq 21UX2 and Cintiq
67 24HD) status LEDs is active (0..3). The other three LEDs on the
68 same side are always inactive.
69
70What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select
71Date: September 2011
72Contact: linux-input@vger.kernel.org
73Description:
74 Writing to this file sets which one of the left four (for Cintiq 21UX2
75 and Cintiq 24HD) status LEDs is active (0..3). The other three LEDs on
76 the left are always inactive.
77
78What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/buttons_luminance
79Date: August 2011
80Contact: linux-input@vger.kernel.org
81Description:
82 Writing to this file sets the overall luminance level (0..15)
83 of all eight button OLED displays.
84
85What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/button<n>_rawimg
86Date: August 2011
87Contact: linux-input@vger.kernel.org
88Description:
89 When writing a 1024 byte raw image in Wacom Intuos 4
90 interleaving format to the file, the image shows up on Button N
91 of the device. The image is a 64x32 pixel 4-bit gray image. The
92 1024 byte binary is split up into 16x 64 byte chunks. Each 64
93 byte chunk encodes the image data for two consecutive lines on
94 the display. The low nibble of each byte contains the first
95 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
index dd930c8db41..4f9ba3c2fca 100644
--- a/Documentation/ABI/testing/sysfs-firmware-acpi
+++ b/Documentation/ABI/testing/sysfs-firmware-acpi
@@ -1,23 +1,3 @@
1What: /sys/firmware/acpi/bgrt/
2Date: January 2012
3Contact: Matthew Garrett <mjg@redhat.com>
4Description:
5 The BGRT is an ACPI 5.0 feature that allows the OS
6 to obtain a copy of the firmware boot splash and
7 some associated metadata. This is intended to be used
8 by boot splash applications in order to interact with
9 the firmware boot splash in order to avoid jarring
10 transitions.
11
12 image: The image bitmap. Currently a 32-bit BMP.
13 status: 1 if the image is valid, 0 if firmware invalidated it.
14 type: 0 indicates image is in BMP format.
15 version: The version of the BGRT. Currently 1.
16 xoffset: The number of pixels between the left of the screen
17 and the left edge of the image.
18 yoffset: The number of pixels between the top of the screen
19 and the top edge of the image.
20
21What: /sys/firmware/acpi/interrupts/ 1What: /sys/firmware/acpi/interrupts/
22Date: February 2008 2Date: February 2008
23Contact: Len Brown <lenb@kernel.org> 3Contact: Len Brown <lenb@kernel.org>
diff --git a/Documentation/ABI/testing/sysfs-fs-ext4 b/Documentation/ABI/testing/sysfs-fs-ext4
index c631253cf85..f22ac0872ae 100644
--- a/Documentation/ABI/testing/sysfs-fs-ext4
+++ b/Documentation/ABI/testing/sysfs-fs-ext4
@@ -96,16 +96,3 @@ Contact: "Theodore Ts'o" <tytso@mit.edu>
96Description: 96Description:
97 The maximum number of megabytes the writeback code will 97 The maximum number of megabytes the writeback code will
98 try to write out before move on to another inode. 98 try to write out before move on to another inode.
99
100What: /sys/fs/ext4/<disk>/extent_max_zeroout_kb
101Date: August 2012
102Contact: "Theodore Ts'o" <tytso@mit.edu>
103Description:
104 The maximum number of kilobytes which will be zeroed
105 out in preference to creating a new uninitialized
106 extent when manipulating an inode's extent tree. Note
107 that using a larger value will increase the
108 variability of time necessary to complete a random
109 write operation (since a 4k random write might turn
110 into a much larger write due to the zeroout
111 operation).
diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
deleted file mode 100644
index 9b31556cfdd..00000000000
--- a/Documentation/ABI/testing/sysfs-kernel-iommu_groups
+++ /dev/null
@@ -1,14 +0,0 @@
1What: /sys/kernel/iommu_groups/
2Date: May 2012
3KernelVersion: v3.5
4Contact: Alex Williamson <alex.williamson@redhat.com>
5Description: /sys/kernel/iommu_groups/ contains a number of sub-
6 directories, each representing an IOMMU group. The
7 name of the sub-directory matches the iommu_group_id()
8 for the group, which is an integer value. Within each
9 subdirectory is another directory named "devices" with
10 links to the sysfs devices contained in this group.
11 The group directory also optionally contains a "name"
12 file if the IOMMU driver has chosen to register a more
13 common name for the group.
14Users:
diff --git a/Documentation/ABI/testing/sysfs-kernel-slab b/Documentation/ABI/testing/sysfs-kernel-slab
index 91bd6ca5440..8b093f8222d 100644
--- a/Documentation/ABI/testing/sysfs-kernel-slab
+++ b/Documentation/ABI/testing/sysfs-kernel-slab
@@ -346,10 +346,6 @@ Description:
346 number of objects per slab. If a slab cannot be allocated 346 number of objects per slab. If a slab cannot be allocated
347 because of fragmentation, SLUB will retry with the minimum order 347 because of fragmentation, SLUB will retry with the minimum order
348 possible depending on its characteristics. 348 possible depending on its characteristics.
349 When debug_guardpage_minorder=N (N > 0) parameter is specified
350 (see Documentation/kernel-parameters.txt), the minimum possible
351 order is used and this sysfs entry can not be used to change
352 the order at run time.
353 349
354What: /sys/kernel/slab/cache/order_fallback 350What: /sys/kernel/slab/cache/order_fallback
355Date: April 2008 351Date: April 2008
diff --git a/Documentation/ABI/testing/sysfs-module b/Documentation/ABI/testing/sysfs-module
index 47064c2b1f7..9489ea8e294 100644
--- a/Documentation/ABI/testing/sysfs-module
+++ b/Documentation/ABI/testing/sysfs-module
@@ -33,19 +33,3 @@ Description: Maximum time allowed for periodic transfers per microframe (μs)
33 Beware, non-standard modes are usually not thoroughly tested by 33 Beware, non-standard modes are usually not thoroughly tested by
34 hardware designers, and the hardware can malfunction when this 34 hardware designers, and the hardware can malfunction when this
35 setting differ from default 100. 35 setting differ from default 100.
36
37What: /sys/module/*/{coresize,initsize}
38Date: Jan 2012
39KernelVersion:»·3.3
40Contact: Kay Sievers <kay.sievers@vrfy.org>
41Description: Module size in bytes.
42
43What: /sys/module/*/taint
44Date: Jan 2012
45KernelVersion:»·3.3
46Contact: Kay Sievers <kay.sievers@vrfy.org>
47Description: Module taint flags:
48 P - proprietary module
49 O - out-of-tree module
50 F - force-loaded module
51 C - staging driver module
diff --git a/Documentation/ABI/testing/sysfs-platform-asus-wmi b/Documentation/ABI/testing/sysfs-platform-asus-wmi
index 019e1e29370..2e7df91620d 100644
--- a/Documentation/ABI/testing/sysfs-platform-asus-wmi
+++ b/Documentation/ABI/testing/sysfs-platform-asus-wmi
@@ -29,10 +29,3 @@ KernelVersion: 2.6.39
29Contact: "Corentin Chary" <corentincj@iksaif.net> 29Contact: "Corentin Chary" <corentincj@iksaif.net>
30Description: 30Description:
31 Control the card touchpad. 1 means on, 0 means off. 31 Control the card touchpad. 1 means on, 0 means off.
32
33What: /sys/devices/platform/<platform>/lid_resume
34Date: May 2012
35KernelVersion: 3.5
36Contact: "AceLan Kao" <acelan.kao@canonical.com>
37Description:
38 Resume on lid open. 1 means on, 0 means off.
diff --git a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
index b31e782bd98..ff53183c384 100644
--- a/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
+++ b/Documentation/ABI/testing/sysfs-platform-ideapad-laptop
@@ -5,15 +5,19 @@ Contact: "Ike Panhc <ike.pan@canonical.com>"
5Description: 5Description:
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
8What: /sys/devices/platform/ideapad/fan_mode 8What: /sys/devices/platform/ideapad/cfg
9Date: June 2012 9Date: Jun 2011
10KernelVersion: 3.6 10KernelVersion: 3.1
11Contact: "Maxim Mikityanskiy <maxtram95@gmail.com>" 11Contact: "Ike Panhc <ike.pan@canonical.com>"
12Description: 12Description:
13 Change fan mode 13 Ideapad capability bits.
14 There are four available modes: 14 Bit 8-10: 1 - Intel graphic only
15 * 0 -> Super Silent Mode 15 2 - ATI graphic only
16 * 1 -> Standard Mode 16 3 - Nvidia graphic only
17 * 2 -> Dust Cleaning 17 4 - Intel and ATI graphic
18 * 4 -> Efficient Thermal Dissipation Mode 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)
19 23
diff --git a/Documentation/ABI/testing/sysfs-power b/Documentation/ABI/testing/sysfs-power
index 217772615d0..b464d12761b 100644
--- a/Documentation/ABI/testing/sysfs-power
+++ b/Documentation/ABI/testing/sysfs-power
@@ -172,75 +172,3 @@ Description:
172 172
173 Reading from this file will display the current value, which is 173 Reading from this file will display the current value, which is
174 set to 1 MB by default. 174 set to 1 MB by default.
175
176What: /sys/power/autosleep
177Date: April 2012
178Contact: Rafael J. Wysocki <rjw@sisk.pl>
179Description:
180 The /sys/power/autosleep file can be written one of the strings
181 returned by reads from /sys/power/state. If that happens, a
182 work item attempting to trigger a transition of the system to
183 the sleep state represented by that string is queued up. This
184 attempt will only succeed if there are no active wakeup sources
185 in the system at that time. After every execution, regardless
186 of whether or not the attempt to put the system to sleep has
187 succeeded, the work item requeues itself until user space
188 writes "off" to /sys/power/autosleep.
189
190 Reading from this file causes the last string successfully
191 written to it to be returned.
192
193What: /sys/power/wake_lock
194Date: February 2012
195Contact: Rafael J. Wysocki <rjw@sisk.pl>
196Description:
197 The /sys/power/wake_lock file allows user space to create
198 wakeup source objects and activate them on demand (if one of
199 those wakeup sources is active, reads from the
200 /sys/power/wakeup_count file block or return false). When a
201 string without white space is written to /sys/power/wake_lock,
202 it will be assumed to represent a wakeup source name. If there
203 is a wakeup source object with that name, it will be activated
204 (unless active already). Otherwise, a new wakeup source object
205 will be registered, assigned the given name and activated.
206 If a string written to /sys/power/wake_lock contains white
207 space, the part of the string preceding the white space will be
208 regarded as a wakeup source name and handled as descrived above.
209 The other part of the string will be regarded as a timeout (in
210 nanoseconds) such that the wakeup source will be automatically
211 deactivated after it has expired. The timeout, if present, is
212 set regardless of the current state of the wakeup source object
213 in question.
214
215 Reads from this file return a string consisting of the names of
216 wakeup sources created with the help of it that are active at
217 the moment, separated with spaces.
218
219
220What: /sys/power/wake_unlock
221Date: February 2012
222Contact: Rafael J. Wysocki <rjw@sisk.pl>
223Description:
224 The /sys/power/wake_unlock file allows user space to deactivate
225 wakeup sources created with the help of /sys/power/wake_lock.
226 When a string is written to /sys/power/wake_unlock, it will be
227 assumed to represent the name of a wakeup source to deactivate.
228 If a wakeup source object of that name exists and is active at
229 the moment, it will be deactivated.
230
231 Reads from this file return a string consisting of the names of
232 wakeup sources created with the help of /sys/power/wake_lock
233 that are inactive at the moment, separated with spaces.
234
235What: /sys/power/pm_print_times
236Date: May 2012
237Contact: Sameer Nanda <snanda@chromium.org>
238Description:
239 The /sys/power/pm_print_times file allows user space to
240 control whether the time taken by devices to suspend and
241 resume is printed. These prints are useful for hunting down
242 devices that take too long to suspend or resume.
243
244 Writing a "1" enables this printing while writing a "0"
245 disables it. The default value is "0". Reading from this file
246 will display the current value.
diff --git a/Documentation/ABI/testing/sysfs-profiling b/Documentation/ABI/testing/sysfs-profiling
index 8a8e466eb2c..b02d8b8c173 100644
--- a/Documentation/ABI/testing/sysfs-profiling
+++ b/Documentation/ABI/testing/sysfs-profiling
@@ -1,13 +1,13 @@
1What: /sys/kernel/profiling 1What: /sys/kernel/profile
2Date: September 2008 2Date: September 2008
3Contact: Dave Hansen <dave@linux.vnet.ibm.com> 3Contact: Dave Hansen <dave@linux.vnet.ibm.com>
4Description: 4Description:
5 /sys/kernel/profiling is the runtime equivalent 5 /sys/kernel/profile is the runtime equivalent
6 of the boot-time profile= option. 6 of the boot-time profile= option.
7 7
8 You can get the same effect running: 8 You can get the same effect running:
9 9
10 echo 2 > /sys/kernel/profiling 10 echo 2 > /sys/kernel/profile
11 11
12 as you would by issuing profile=2 on the boot 12 as you would by issuing profile=2 on the boot
13 command line. 13 command line.
diff --git a/Documentation/ABI/testing/sysfs-ptp b/Documentation/ABI/testing/sysfs-ptp
index 05aeedf1779..d40d2b55050 100644
--- a/Documentation/ABI/testing/sysfs-ptp
+++ b/Documentation/ABI/testing/sysfs-ptp
@@ -19,11 +19,7 @@ Date: September 2010
19Contact: Richard Cochran <richardcochran@gmail.com> 19Contact: Richard Cochran <richardcochran@gmail.com>
20Description: 20Description:
21 This file contains the name of the PTP hardware clock 21 This file contains the name of the PTP hardware clock
22 as a human readable string. The purpose of this 22 as a human readable string.
23 attribute is to provide the user with a "friendly
24 name" and to help distinguish PHY based devices from
25 MAC based ones. The string does not necessarily have
26 to be any kind of unique id.
27 23
28What: /sys/class/ptp/ptpN/max_adjustment 24What: /sys/class/ptp/ptpN/max_adjustment
29Date: September 2010 25Date: September 2010
diff --git a/Documentation/ABI/testing/sysfs-tty b/Documentation/ABI/testing/sysfs-tty
index ad22fb0ee76..b138b663bf5 100644
--- a/Documentation/ABI/testing/sysfs-tty
+++ b/Documentation/ABI/testing/sysfs-tty
@@ -17,124 +17,3 @@ 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
21What: /sys/class/tty/ttyS0/uartclk
22Date: Sep 2012
23Contact: Tomas Hlavacek <tmshlvck@gmail.com>
24Description:
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
29 These sysfs values expose the TIOCGSERIAL interface via
30 sysfs rather than via ioctls.
31
32What: /sys/class/tty/ttyS0/type
33Date: October 2012
34Contact: Alan Cox <alan@linux.intel.com>
35Description:
36 Shows the current tty type for this port.
37
38 These sysfs values expose the TIOCGSERIAL interface via
39 sysfs rather than via ioctls.
40
41What: /sys/class/tty/ttyS0/line
42Date: October 2012
43Contact: Alan Cox <alan@linux.intel.com>
44Description:
45 Shows the current tty line number for this port.
46
47 These sysfs values expose the TIOCGSERIAL interface via
48 sysfs rather than via ioctls.
49
50What: /sys/class/tty/ttyS0/port
51Date: October 2012
52Contact: Alan Cox <alan@linux.intel.com>
53Description:
54 Shows the current tty port I/O address for this port.
55
56 These sysfs values expose the TIOCGSERIAL interface via
57 sysfs rather than via ioctls.
58
59What: /sys/class/tty/ttyS0/irq
60Date: October 2012
61Contact: Alan Cox <alan@linux.intel.com>
62Description:
63 Shows the current primary interrupt for this port.
64
65 These sysfs values expose the TIOCGSERIAL interface via
66 sysfs rather than via ioctls.
67
68What: /sys/class/tty/ttyS0/flags
69Date: October 2012
70Contact: Alan Cox <alan@linux.intel.com>
71Description:
72 Show the tty port status flags for this port.
73
74 These sysfs values expose the TIOCGSERIAL interface via
75 sysfs rather than via ioctls.
76
77What: /sys/class/tty/ttyS0/xmit_fifo_size
78Date: October 2012
79Contact: Alan Cox <alan@linux.intel.com>
80Description:
81 Show the transmit FIFO size for this port.
82
83 These sysfs values expose the TIOCGSERIAL interface via
84 sysfs rather than via ioctls.
85
86What: /sys/class/tty/ttyS0/close_delay
87Date: October 2012
88Contact: Alan Cox <alan@linux.intel.com>
89Description:
90 Show the closing delay time for this port in ms.
91
92 These sysfs values expose the TIOCGSERIAL interface via
93 sysfs rather than via ioctls.
94
95What: /sys/class/tty/ttyS0/closing_wait
96Date: October 2012
97Contact: Alan Cox <alan@linux.intel.com>
98Description:
99 Show the close wait time for this port in ms.
100
101 These sysfs values expose the TIOCGSERIAL interface via
102 sysfs rather than via ioctls.
103
104What: /sys/class/tty/ttyS0/custom_divisor
105Date: October 2012
106Contact: Alan Cox <alan@linux.intel.com>
107Description:
108 Show the custom divisor if any that is set on this port.
109
110 These sysfs values expose the TIOCGSERIAL interface via
111 sysfs rather than via ioctls.
112
113What: /sys/class/tty/ttyS0/io_type
114Date: October 2012
115Contact: Alan Cox <alan@linux.intel.com>
116Description:
117 Show the I/O type that is to be used with the iomem base
118 address.
119
120 These sysfs values expose the TIOCGSERIAL interface via
121 sysfs rather than via ioctls.
122
123What: /sys/class/tty/ttyS0/iomem_base
124Date: October 2012
125Contact: Alan Cox <alan@linux.intel.com>
126Description:
127 The I/O memory base for this port.
128
129 These sysfs values expose the TIOCGSERIAL interface via
130 sysfs rather than via ioctls.
131
132What: /sys/class/tty/ttyS0/iomem_reg_shift
133Date: October 2012
134Contact: Alan Cox <alan@linux.intel.com>
135Description:
136 Show the register shift indicating the spacing to be used
137 for accesses on this iomem address.
138
139 These sysfs values expose the TIOCGSERIAL interface via
140 sysfs rather than via ioctls.
generated by cgit v1.2.2 (git 2.25.0) at 2025-10-13 20:03:59 -0400