aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ABI')
-rw-r--r--Documentation/ABI/removed/ip_queue9
-rw-r--r--Documentation/ABI/stable/sysfs-driver-w1_ds28e0415
-rw-r--r--Documentation/ABI/stable/vdso2
-rw-r--r--Documentation/ABI/testing/debugfs-pfo-nx-crypto45
-rw-r--r--Documentation/ABI/testing/dev-kmsg101
-rw-r--r--Documentation/ABI/testing/sysfs-block-rssd15
-rw-r--r--Documentation/ABI/testing/sysfs-block-zram2
-rw-r--r--Documentation/ABI/testing/sysfs-bus-fcoe77
-rw-r--r--Documentation/ABI/testing/sysfs-bus-i2c-devices-lm353315
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio770
-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-rbd4
-rw-r--r--Documentation/ABI/testing/sysfs-bus-usb31
-rw-r--r--Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg2
-rw-r--r--Documentation/ABI/testing/sysfs-class-backlight-driver-adp88702
-rw-r--r--Documentation/ABI/testing/sysfs-class-backlight-driver-lm353348
-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-mesh9
-rw-r--r--Documentation/ABI/testing/sysfs-devices-power35
-rw-r--r--Documentation/ABI/testing/sysfs-devices-system-cpu25
-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-roccat-savu77
-rw-r--r--Documentation/ABI/testing/sysfs-driver-wacom23
-rw-r--r--Documentation/ABI/testing/sysfs-kernel-iommu_groups14
-rw-r--r--Documentation/ABI/testing/sysfs-power72
30 files changed, 1723 insertions, 61 deletions
diff --git a/Documentation/ABI/removed/ip_queue b/Documentation/ABI/removed/ip_queue
new file mode 100644
index 000000000000..3243613bc2d2
--- /dev/null
+++ b/Documentation/ABI/removed/ip_queue
@@ -0,0 +1,9 @@
1What: ip_queue
2Date: finally removed in kernel v3.5.0
3Contact: Pablo Neira Ayuso <pablo@netfilter.org>
4Description:
5 ip_queue has been replaced by nfnetlink_queue which provides
6 more advanced queueing mechanism to user-space. The ip_queue
7 module was already announced to become obsolete years ago.
8
9Users:
diff --git a/Documentation/ABI/stable/sysfs-driver-w1_ds28e04 b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04
new file mode 100644
index 000000000000..26579ee868c9
--- /dev/null
+++ b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04
@@ -0,0 +1,15 @@
1What: /sys/bus/w1/devices/.../pio
2Date: May 2012
3Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
4Description: read/write the contents of the two PIO's of the DS28E04-100
5 see Documentation/w1/slaves/w1_ds28e04 for detailed information
6Users: any user space application which wants to communicate with DS28E04-100
7
8
9
10What: /sys/bus/w1/devices/.../eeprom
11Date: May 2012
12Contact: Markus Franke <franm@hrz.tu-chemnitz.de>
13Description: read/write the contents of the EEPROM memory of the DS28E04-100
14 see Documentation/w1/slaves/w1_ds28e04 for detailed information
15Users: any user space application which wants to communicate with DS28E04-100
diff --git a/Documentation/ABI/stable/vdso b/Documentation/ABI/stable/vdso
index 8a1cbb594497..7cdfc28cc2c6 100644
--- a/Documentation/ABI/stable/vdso
+++ b/Documentation/ABI/stable/vdso
@@ -24,4 +24,4 @@ though.
24 24
25(As of this writing, this ABI documentation as been confirmed for x86_64. 25(As of this writing, this ABI documentation as been confirmed for x86_64.
26 The maintainers of the other vDSO-using architectures should confirm 26 The maintainers of the other vDSO-using architectures should confirm
27 that it is correct for their architecture.) \ No newline at end of file 27 that it is correct for their architecture.)
diff --git a/Documentation/ABI/testing/debugfs-pfo-nx-crypto b/Documentation/ABI/testing/debugfs-pfo-nx-crypto
new file mode 100644
index 000000000000..685d5a448423
--- /dev/null
+++ b/Documentation/ABI/testing/debugfs-pfo-nx-crypto
@@ -0,0 +1,45 @@
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
new file mode 100644
index 000000000000..7e7e07a82e0e
--- /dev/null
+++ b/Documentation/ABI/testing/dev-kmsg
@@ -0,0 +1,101 @@
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 neccessarily 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/sysfs-block-rssd b/Documentation/ABI/testing/sysfs-block-rssd
index d535757799fe..beef30c046b0 100644
--- a/Documentation/ABI/testing/sysfs-block-rssd
+++ b/Documentation/ABI/testing/sysfs-block-rssd
@@ -1,18 +1,5 @@
1What: /sys/block/rssd*/registers
2Date: March 2012
3KernelVersion: 3.3
4Contact: Asai Thambi S P <asamymuthupa@micron.com>
5Description: This is a read-only file. Dumps below driver information and
6 hardware registers.
7 - S ACTive
8 - Command Issue
9 - Allocated
10 - Completed
11 - PORT IRQ STAT
12 - HOST IRQ STAT
13
14What: /sys/block/rssd*/status 1What: /sys/block/rssd*/status
15Date: April 2012 2Date: April 2012
16KernelVersion: 3.4 3KernelVersion: 3.4
17Contact: Asai Thambi S P <asamymuthupa@micron.com> 4Contact: Asai Thambi S P <asamymuthupa@micron.com>
18Description: This is a read-only file. Indicates the status of the device. 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 c8b3b48ec62c..ec93fe33baa6 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 \ No newline at end of file 99 Unit: bytes
diff --git a/Documentation/ABI/testing/sysfs-bus-fcoe b/Documentation/ABI/testing/sysfs-bus-fcoe
new file mode 100644
index 000000000000..469d09c02f6b
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-fcoe
@@ -0,0 +1,77 @@
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-i2c-devices-lm3533 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533
new file mode 100644
index 000000000000..1b62230b33b9
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533
@@ -0,0 +1,15 @@
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
new file mode 100644
index 000000000000..2f06d40fe07d
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -0,0 +1,770 @@
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_accel_offset
193What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
194What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
195What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
196What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
197What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
198What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
199What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
200KernelVersion: 2.6.35
201Contact: linux-iio@vger.kernel.org
202Description:
203 If known for a device, offset to be added to <type>[Y]_raw prior
204 to scaling by <type>[Y]_scale in order to obtain value in the
205 <type> units as specified in <type>[Y]_raw documentation.
206 Not present if the offset is always 0 or unknown. If Y or
207 axis <x|y|z> is not present, then the offset applies to all
208 in channels of <type>.
209 May be writable if a variable offset can be applied on the
210 device. Note that this is different to calibbias which
211 is for devices (or drivers) that apply offsets to compensate
212 for variation between different instances of the part, typically
213 adjusted by using some hardware supported calibration procedure.
214 Calibbias is applied internally, offset is applied in userspace
215 to the _raw output.
216
217What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
218What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
219What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
220What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
221What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
222What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
223What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
224What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
225What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
226What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
227What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
228What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale
229KernelVersion: 2.6.35
230Contact: linux-iio@vger.kernel.org
231Description:
232 If known for a device, scale to be applied to <type>Y[_name]_raw
233 post addition of <type>[Y][_name]_offset in order to obtain the
234 measured value in <type> units as specified in
235 <type>[Y][_name]_raw documentation. If shared across all in
236 channels then Y and <x|y|z> are not present and the value is
237 called <type>[Y][_name]_scale. The peak modifier means this
238 value is applied to <type>Y[_name]_peak_raw values.
239
240What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias
241What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias
242What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias
243What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias
244What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias
245What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias
246What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias
247What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
248KernelVersion: 2.6.35
249Contact: linux-iio@vger.kernel.org
250Description:
251 Hardware applied calibration offset (assumed to fix production
252 inaccuracies).
253
254What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
255What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
256What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
257What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
258What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
259What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
260What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
261What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
262What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
263what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
264what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
265KernelVersion: 2.6.35
266Contact: linux-iio@vger.kernel.org
267Description:
268 Hardware applied calibration scale factor (assumed to fix
269 production inaccuracies). If shared across all channels,
270 <type>_calibscale is used.
271
272What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
273What: /sys/.../iio:deviceX/in_voltageX_scale_available
274What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
275What: /sys/.../iio:deviceX/out_voltageX_scale_available
276What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
277What: /sys/.../iio:deviceX/in_capacitance_scale_available
278KernelVersion: 2.6.35
279Contact: linux-iio@vger.kernel.org
280Description:
281 If a discrete set of scale values is available, they
282 are listed in this attribute.
283
284What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
285KernelVersion: 2.6.35
286Contact: linux-iio@vger.kernel.org
287Description:
288 Hardware applied gain factor. If shared across all channels,
289 <type>_hardwaregain is used.
290
291What: /sys/.../in_accel_filter_low_pass_3db_frequency
292What: /sys/.../in_magn_filter_low_pass_3db_frequency
293What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
294KernelVersion: 3.2
295Contact: linux-iio@vger.kernel.org
296Description:
297 If a known or controllable low pass filter is applied
298 to the underlying data channel, then this parameter
299 gives the 3dB frequency of the filter in Hz.
300
301What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
302What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
303KernelVersion: 2.6.37
304Contact: linux-iio@vger.kernel.org
305Description:
306 Raw (unscaled, no bias etc.) output voltage for
307 channel Y. The number must always be specified and
308 unique if the output corresponds to a single channel.
309 While DAC like devices typically use out_voltage,
310 a continuous frequency generating device, such as
311 a DDS or PLL should use out_altvoltage.
312
313What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
314What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw
315KernelVersion: 2.6.37
316Contact: linux-iio@vger.kernel.org
317Description:
318 Raw (unscaled, no bias etc.) output voltage for an aggregate of
319 channel Y, channel Z, etc. This interface is available in cases
320 where a single output sets the value for multiple channels
321 simultaneously.
322
323What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
324What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
325What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode
326What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode
327KernelVersion: 2.6.38
328Contact: linux-iio@vger.kernel.org
329Description:
330 Specifies the output powerdown mode.
331 DAC output stage is disconnected from the amplifier and
332 1kohm_to_gnd: connected to ground via an 1kOhm resistor,
333 6kohm_to_gnd: connected to ground via a 6kOhm resistor,
334 20kohm_to_gnd: connected to ground via a 20kOhm resistor,
335 100kohm_to_gnd: connected to ground via an 100kOhm resistor,
336 three_state: left floating.
337 For a list of available output power down options read
338 outX_powerdown_mode_available. If Y is not present the
339 mode is shared across all outputs.
340
341What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
342What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
343What: /sys/.../iio:deviceX/out_altvotlageY_powerdown_mode_available
344What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available
345KernelVersion: 2.6.38
346Contact: linux-iio@vger.kernel.org
347Description:
348 Lists all available output power down modes.
349 If Y is not present the mode is shared across all outputs.
350
351What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
352What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
353What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
354What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown
355KernelVersion: 2.6.38
356Contact: linux-iio@vger.kernel.org
357Description:
358 Writing 1 causes output Y to enter the power down mode specified
359 by the corresponding outY_powerdown_mode. DAC output stage is
360 disconnected from the amplifier. Clearing returns to normal
361 operation. Y may be suppressed if all outputs are controlled
362 together.
363
364What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
365KernelVersion: 3.4.0
366Contact: linux-iio@vger.kernel.org
367Description:
368 Output frequency for channel Y in Hz. The number must always be
369 specified and unique if the output corresponds to a single
370 channel.
371
372What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase
373KernelVersion: 3.4.0
374Contact: linux-iio@vger.kernel.org
375Description:
376 Phase in radians of one frequency/clock output Y
377 (out_altvoltageY) relative to another frequency/clock output
378 (out_altvoltageZ) of the device X. The number must always be
379 specified and unique if the output corresponds to a single
380 channel.
381
382What: /sys/bus/iio/devices/iio:deviceX/events
383KernelVersion: 2.6.35
384Contact: linux-iio@vger.kernel.org
385Description:
386 Configuration of which hardware generated events are passed up
387 to user-space.
388
389What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
390What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
391What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
392What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
393What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
394What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
395What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
396What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
397What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
398What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
399What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
400What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
401What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
402What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
403What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
404What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
405What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
406What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
407What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
408What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
409What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
410What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
411What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
412What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
413KernelVersion: 2.6.37
414Contact: linux-iio@vger.kernel.org
415Description:
416 Event generated when channel passes a threshold in the specified
417 (_rising|_falling) direction. If the direction is not specified,
418 then either the device will report an event which ever direction
419 a single threshold value is passed in (e.g.
420 <type>[Y][_name]_<raw|input>_thresh_value) or
421 <type>[Y][_name]_<raw|input>_thresh_rising_value and
422 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
423 different values, but the device can only enable both thresholds
424 or neither.
425 Note the driver will assume the last p events requested are
426 to be enabled where p is how many it supports (which may vary
427 depending on the exact set requested. So if you want to be
428 sure you have set what you think you have, check the contents of
429 these attributes after everything is configured. Drivers may
430 have to buffer any parameters so that they are consistent when
431 a given event type is enabled at a future point (and not those for
432 whatever event was previously enabled).
433
434What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
435What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
436What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
437What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
438What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
439What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
440What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
441What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
442What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
443What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
444What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
445What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
446What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
447What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
448What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
449What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
450What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
451What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
452What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
453What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
454What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
455What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
456What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
457What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
458KernelVersion: 2.6.37
459Contact: linux-iio@vger.kernel.org
460Description:
461 Event generated when channel passes a threshold on the rate of
462 change (1st differential) in the specified (_rising|_falling)
463 direction. If the direction is not specified, then either the
464 device will report an event which ever direction a single
465 threshold value is passed in (e.g.
466 <type>[Y][_name]_<raw|input>_roc_value) or
467 <type>[Y][_name]_<raw|input>_roc_rising_value and
468 <type>[Y][_name]_<raw|input>_roc_falling_value may take
469 different values, but the device can only enable both rate of
470 change thresholds or neither.
471 Note the driver will assume the last p events requested are
472 to be enabled where p is however many it supports (which may
473 vary depending on the exact set requested. So if you want to be
474 sure you have set what you think you have, check the contents of
475 these attributes after everything is configured. Drivers may
476 have to buffer any parameters so that they are consistent when
477 a given event type is enabled a future point (and not those for
478 whatever event was previously enabled).
479
480What: /sys/.../events/in_accel_x_raw_thresh_rising_value
481What: /sys/.../events/in_accel_x_raw_thresh_falling_value
482What: /sys/.../events/in_accel_y_raw_thresh_rising_value
483What: /sys/.../events/in_accel_y_raw_thresh_falling_value
484What: /sys/.../events/in_accel_z_raw_thresh_rising_value
485What: /sys/.../events/in_accel_z_raw_thresh_falling_value
486What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
487What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
488What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
489What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
490What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
491What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
492What: /sys/.../events/in_magn_x_raw_thresh_rising_value
493What: /sys/.../events/in_magn_x_raw_thresh_falling_value
494What: /sys/.../events/in_magn_y_raw_thresh_rising_value
495What: /sys/.../events/in_magn_y_raw_thresh_falling_value
496What: /sys/.../events/in_magn_z_raw_thresh_rising_value
497What: /sys/.../events/in_magn_z_raw_thresh_falling_value
498What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
499What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
500What: /sys/.../events/in_voltageY_raw_thresh_rising_value
501What: /sys/.../events/in_voltageY_raw_thresh_falling_value
502What: /sys/.../events/in_tempY_raw_thresh_rising_value
503What: /sys/.../events/in_tempY_raw_thresh_falling_value
504What: /sys/.../events/in_illuminance0_thresh_falling_value
505what: /sys/.../events/in_illuminance0_thresh_rising_value
506what: /sys/.../events/in_proximity0_thresh_falling_value
507what: /sys/.../events/in_proximity0_thresh_rising_value
508KernelVersion: 2.6.37
509Contact: linux-iio@vger.kernel.org
510Description:
511 Specifies the value of threshold that the device is comparing
512 against for the events enabled by
513 <type>Y[_name]_thresh[_rising|falling]_en.
514 If separate attributes exist for the two directions, but
515 direction is not specified for this attribute, then a single
516 threshold value applies to both directions.
517 The raw or input element of the name indicates whether the
518 value is in raw device units or in processed units (as _raw
519 and _input do on sysfs direct channel read attributes).
520
521What: /sys/.../events/in_accel_x_raw_roc_rising_value
522What: /sys/.../events/in_accel_x_raw_roc_falling_value
523What: /sys/.../events/in_accel_y_raw_roc_rising_value
524What: /sys/.../events/in_accel_y_raw_roc_falling_value
525What: /sys/.../events/in_accel_z_raw_roc_rising_value
526What: /sys/.../events/in_accel_z_raw_roc_falling_value
527What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
528What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
529What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
530What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
531What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
532What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
533What: /sys/.../events/in_magn_x_raw_roc_rising_value
534What: /sys/.../events/in_magn_x_raw_roc_falling_value
535What: /sys/.../events/in_magn_y_raw_roc_rising_value
536What: /sys/.../events/in_magn_y_raw_roc_falling_value
537What: /sys/.../events/in_magn_z_raw_roc_rising_value
538What: /sys/.../events/in_magn_z_raw_roc_falling_value
539What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
540What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
541What: /sys/.../events/in_voltageY_raw_roc_rising_value
542What: /sys/.../events/in_voltageY_raw_roc_falling_value
543What: /sys/.../events/in_tempY_raw_roc_rising_value
544What: /sys/.../events/in_tempY_raw_roc_falling_value
545KernelVersion: 2.6.37
546Contact: linux-iio@vger.kernel.org
547Description:
548 Specifies the value of rate of change threshold that the
549 device is comparing against for the events enabled by
550 <type>[Y][_name]_roc[_rising|falling]_en.
551 If separate attributes exist for the two directions,
552 but direction is not specified for this attribute,
553 then a single threshold value applies to both directions.
554 The raw or input element of the name indicates whether the
555 value is in raw device units or in processed units (as _raw
556 and _input do on sysfs direct channel read attributes).
557
558What: /sys/.../events/in_accel_x_thresh_rising_period
559What: /sys/.../events/in_accel_x_thresh_falling_period
560hat: /sys/.../events/in_accel_x_roc_rising_period
561What: /sys/.../events/in_accel_x_roc_falling_period
562What: /sys/.../events/in_accel_y_thresh_rising_period
563What: /sys/.../events/in_accel_y_thresh_falling_period
564What: /sys/.../events/in_accel_y_roc_rising_period
565What: /sys/.../events/in_accel_y_roc_falling_period
566What: /sys/.../events/in_accel_z_thresh_rising_period
567What: /sys/.../events/in_accel_z_thresh_falling_period
568What: /sys/.../events/in_accel_z_roc_rising_period
569What: /sys/.../events/in_accel_z_roc_falling_period
570What: /sys/.../events/in_anglvel_x_thresh_rising_period
571What: /sys/.../events/in_anglvel_x_thresh_falling_period
572What: /sys/.../events/in_anglvel_x_roc_rising_period
573What: /sys/.../events/in_anglvel_x_roc_falling_period
574What: /sys/.../events/in_anglvel_y_thresh_rising_period
575What: /sys/.../events/in_anglvel_y_thresh_falling_period
576What: /sys/.../events/in_anglvel_y_roc_rising_period
577What: /sys/.../events/in_anglvel_y_roc_falling_period
578What: /sys/.../events/in_anglvel_z_thresh_rising_period
579What: /sys/.../events/in_anglvel_z_thresh_falling_period
580What: /sys/.../events/in_anglvel_z_roc_rising_period
581What: /sys/.../events/in_anglvel_z_roc_falling_period
582What: /sys/.../events/in_magn_x_thresh_rising_period
583What: /sys/.../events/in_magn_x_thresh_falling_period
584What: /sys/.../events/in_magn_x_roc_rising_period
585What: /sys/.../events/in_magn_x_roc_falling_period
586What: /sys/.../events/in_magn_y_thresh_rising_period
587What: /sys/.../events/in_magn_y_thresh_falling_period
588What: /sys/.../events/in_magn_y_roc_rising_period
589What: /sys/.../events/in_magn_y_roc_falling_period
590What: /sys/.../events/in_magn_z_thresh_rising_period
591What: /sys/.../events/in_magn_z_thresh_falling_period
592What: /sys/.../events/in_magn_z_roc_rising_period
593What: /sys/.../events/in_magn_z_roc_falling_period
594What: /sys/.../events/in_voltageY_supply_thresh_rising_period
595What: /sys/.../events/in_voltageY_supply_thresh_falling_period
596What: /sys/.../events/in_voltageY_supply_roc_rising_period
597What: /sys/.../events/in_voltageY_supply_roc_falling_period
598What: /sys/.../events/in_voltageY_thresh_rising_period
599What: /sys/.../events/in_voltageY_thresh_falling_period
600What: /sys/.../events/in_voltageY_roc_rising_period
601What: /sys/.../events/in_voltageY_roc_falling_period
602What: /sys/.../events/in_tempY_thresh_rising_period
603What: /sys/.../events/in_tempY_thresh_falling_period
604What: /sys/.../events/in_tempY_roc_rising_period
605What: /sys/.../events/in_tempY_roc_falling_period
606What: /sys/.../events/in_accel_x&y&z_mag_falling_period
607What: /sys/.../events/in_intensity0_thresh_period
608What: /sys/.../events/in_proximity0_thresh_period
609KernelVersion: 2.6.37
610Contact: linux-iio@vger.kernel.org
611Description:
612 Period of time (in seconds) for which the condition must be
613 met before an event is generated. If direction is not
614 specified then this period applies to both directions.
615
616What: /sys/.../iio:deviceX/events/in_accel_mag_en
617What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
618What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
619What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
620What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
621What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
622What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
623What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
624What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
625What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
626What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
627What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
628What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
629What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
630KernelVersion: 2.6.37
631Contact: linux-iio@vger.kernel.org
632Description:
633 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
634 magnitude of the channel is compared to the threshold, not its
635 signed value.
636
637What: /sys/.../events/in_accel_raw_mag_value
638What: /sys/.../events/in_accel_x_raw_mag_rising_value
639What: /sys/.../events/in_accel_y_raw_mag_rising_value
640What: /sys/.../events/in_accel_z_raw_mag_rising_value
641KernelVersion: 2.6.37
642Contact: linux-iio@vger.kernel.org
643Description:
644 The value to which the magnitude of the channel is compared. If
645 number or direction is not specified, applies to all channels of
646 this type.
647
648What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
649KernelVersion: 2.6.35
650Contact: linux-iio@vger.kernel.org
651Description:
652 The name of the trigger source being used, as per string given
653 in /sys/class/iio/triggerY/name.
654
655What: /sys/bus/iio/devices/iio:deviceX/buffer/length
656KernelVersion: 2.6.35
657Contact: linux-iio@vger.kernel.org
658Description:
659 Number of scans contained by the buffer.
660
661What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum
662KernelVersion: 2.6.37
663Contact: linux-iio@vger.kernel.org
664Description:
665 Bytes per scan. Due to alignment fun, the scan may be larger
666 than implied directly by the scan_element parameters.
667
668What: /sys/bus/iio/devices/iio:deviceX/buffer/enable
669KernelVersion: 2.6.35
670Contact: linux-iio@vger.kernel.org
671Description:
672 Actually start the buffer capture up. Will start trigger
673 if first device and appropriate.
674
675What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements
676KernelVersion: 2.6.37
677Contact: linux-iio@vger.kernel.org
678Description:
679 Directory containing interfaces for elements that will be
680 captured for a single triggered sample set in the buffer.
681
682What: /sys/.../buffer/scan_elements/in_accel_x_en
683What: /sys/.../buffer/scan_elements/in_accel_y_en
684What: /sys/.../buffer/scan_elements/in_accel_z_en
685What: /sys/.../buffer/scan_elements/in_anglvel_x_en
686What: /sys/.../buffer/scan_elements/in_anglvel_y_en
687What: /sys/.../buffer/scan_elements/in_anglvel_z_en
688What: /sys/.../buffer/scan_elements/in_magn_x_en
689What: /sys/.../buffer/scan_elements/in_magn_y_en
690What: /sys/.../buffer/scan_elements/in_magn_z_en
691What: /sys/.../buffer/scan_elements/in_timestamp_en
692What: /sys/.../buffer/scan_elements/in_voltageY_supply_en
693What: /sys/.../buffer/scan_elements/in_voltageY_en
694What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en
695What: /sys/.../buffer/scan_elements/in_incli_x_en
696What: /sys/.../buffer/scan_elements/in_incli_y_en
697KernelVersion: 2.6.37
698Contact: linux-iio@vger.kernel.org
699Description:
700 Scan element control for triggered data capture.
701
702What: /sys/.../buffer/scan_elements/in_accel_type
703What: /sys/.../buffer/scan_elements/in_anglvel_type
704What: /sys/.../buffer/scan_elements/in_magn_type
705What: /sys/.../buffer/scan_elements/in_incli_type
706What: /sys/.../buffer/scan_elements/in_voltageY_type
707What: /sys/.../buffer/scan_elements/in_voltage_type
708What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
709What: /sys/.../buffer/scan_elements/in_timestamp_type
710KernelVersion: 2.6.37
711Contact: linux-iio@vger.kernel.org
712Description:
713 Description of the scan element data storage within the buffer
714 and hence the form in which it is read from user-space.
715 Form is [be|le]:[s|u]bits/storagebits[>>shift].
716 be or le specifies big or little endian. s or u specifies if
717 signed (2's complement) or unsigned. bits is the number of bits
718 of data and storagebits is the space (after padding) that it
719 occupies in the buffer. shift if specified, is the shift that
720 needs to be applied prior to masking out unused bits. Some
721 devices put their data in the middle of the transferred elements
722 with additional information on both sides. Note that some
723 devices will have additional information in the unused bits
724 so to get a clean value, the bits value must be used to mask
725 the buffer output value appropriately. The storagebits value
726 also specifies the data alignment. So s48/64>>2 will be a
727 signed 48 bit integer stored in a 64 bit location aligned to
728 a 64 bit boundary. To obtain the clean value, shift right 2
729 and apply a mask to zero the top 16 bits of the result.
730 For other storage combinations this attribute will be extended
731 appropriately.
732
733What: /sys/.../buffer/scan_elements/in_accel_type_available
734KernelVersion: 2.6.37
735Contact: linux-iio@vger.kernel.org
736Description:
737 If the type parameter can take one of a small set of values,
738 this attribute lists them.
739
740What: /sys/.../buffer/scan_elements/in_voltageY_index
741What: /sys/.../buffer/scan_elements/in_voltageY_supply_index
742What: /sys/.../buffer/scan_elements/in_accel_x_index
743What: /sys/.../buffer/scan_elements/in_accel_y_index
744What: /sys/.../buffer/scan_elements/in_accel_z_index
745What: /sys/.../buffer/scan_elements/in_anglvel_x_index
746What: /sys/.../buffer/scan_elements/in_anglvel_y_index
747What: /sys/.../buffer/scan_elements/in_anglvel_z_index
748What: /sys/.../buffer/scan_elements/in_magn_x_index
749What: /sys/.../buffer/scan_elements/in_magn_y_index
750What: /sys/.../buffer/scan_elements/in_magn_z_index
751What: /sys/.../buffer/scan_elements/in_incli_x_index
752What: /sys/.../buffer/scan_elements/in_incli_y_index
753What: /sys/.../buffer/scan_elements/in_timestamp_index
754KernelVersion: 2.6.37
755Contact: linux-iio@vger.kernel.org
756Description:
757 A single positive integer specifying the position of this
758 scan element in the buffer. Note these are not dependent on
759 what is enabled and may not be contiguous. Thus for user-space
760 to establish the full layout these must be used in conjunction
761 with all _en attributes to establish which channels are present,
762 and the relevant _type attributes to establish the data storage
763 format.
764
765What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
766KernelVersion: 2.6.38
767Contact: linux-iio@vger.kernel.org
768Description:
769 This attribute is used to read the amount of quadrature error
770 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
new file mode 100644
index 000000000000..2ce9c3f68eee
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
@@ -0,0 +1,37 @@
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
new file mode 100644
index 000000000000..d89aded01c5a
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
@@ -0,0 +1,21 @@
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
new file mode 100644
index 000000000000..22c5ea670971
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als
@@ -0,0 +1,61 @@
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-rbd b/Documentation/ABI/testing/sysfs-bus-rbd
index dbedafb095e2..bcd88eb7ebcd 100644
--- a/Documentation/ABI/testing/sysfs-bus-rbd
+++ b/Documentation/ABI/testing/sysfs-bus-rbd
@@ -65,11 +65,11 @@ snap_*
65Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name> 65Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name>
66------------------------------------------------------------- 66-------------------------------------------------------------
67 67
68id 68snap_id
69 69
70 The rados internal snapshot id assigned for this snapshot 70 The rados internal snapshot id assigned for this snapshot
71 71
72size 72snap_size
73 73
74 The size of the image when this snapshot was taken. 74 The size of the image when this snapshot was taken.
75 75
diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb
index 7c22a532fdfb..5f75f8f7df34 100644
--- a/Documentation/ABI/testing/sysfs-bus-usb
+++ b/Documentation/ABI/testing/sysfs-bus-usb
@@ -135,6 +135,17 @@ Description:
135 for the device and attempt to bind to it. For example: 135 for the device and attempt to bind to it. For example:
136 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id 136 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
137 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
138What: /sys/bus/usb-serial/drivers/.../new_id 149What: /sys/bus/usb-serial/drivers/.../new_id
139Date: October 2011 150Date: October 2011
140Contact: linux-usb@vger.kernel.org 151Contact: linux-usb@vger.kernel.org
@@ -157,6 +168,10 @@ Description:
157 match the driver to the device. For example: 168 match the driver to the device. For example:
158 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id 169 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
159 170
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
160What: /sys/bus/usb/device/.../avoid_reset_quirk 175What: /sys/bus/usb/device/.../avoid_reset_quirk
161Date: December 2009 176Date: December 2009
162Contact: Oliver Neukum <oliver@neukum.org> 177Contact: Oliver Neukum <oliver@neukum.org>
@@ -189,7 +204,19 @@ Contact: Matthew Garrett <mjg@redhat.com>
189Description: 204Description:
190 Some information about whether a given USB device is 205 Some information about whether a given USB device is
191 physically fixed to the platform can be inferred from a 206 physically fixed to the platform can be inferred from a
192 combination of hub decriptor bits and platform-specific data 207 combination of hub descriptor bits and platform-specific data
193 such as ACPI. This file will read either "removable" or 208 such as ACPI. This file will read either "removable" or
194 "fixed" if the information is available, and "unknown" 209 "fixed" if the information is available, and "unknown"
195 otherwise. \ No newline at end of file 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.
diff --git a/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg b/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
index cb830df8777c..70d00dfa443d 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. \ No newline at end of file 43 change this fields value to k + 10 ** m.
diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870 b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
index 4a9c545bda4b..33e648808117 100644
--- a/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
+++ b/Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870
@@ -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. \ No newline at end of file 56 /sys/class/backlight/<backlight>/brightness.
diff --git a/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533 b/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533
new file mode 100644
index 000000000000..77cf7ac949af
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533
@@ -0,0 +1,48 @@
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-extcon b/Documentation/ABI/testing/sysfs-class-extcon
new file mode 100644
index 000000000000..20ab361bd8c6
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-extcon
@@ -0,0 +1,97 @@
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 simulteneously.
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 overriden 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 have 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 dev.
57 Inputs of all the methods are required to meet the
58 mutually_exclusive contidions if they exist.
59
60 It is recommended to use this "global" state interface if
61 you need to enter 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/name 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_dev is
87 {0x3, 0x5, 0xC, 0x0}, the, 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
new file mode 100644
index 000000000000..620ebb3b9baa
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-led-driver-lm3533
@@ -0,0 +1,65 @@
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 4d55a1888981..938ef71e2035 100644
--- a/Documentation/ABI/testing/sysfs-class-mtd
+++ b/Documentation/ABI/testing/sysfs-class-mtd
@@ -123,3 +123,55 @@ 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-mesh b/Documentation/ABI/testing/sysfs-class-net-mesh
index b218e0f8bdb3..c81fe89c4c46 100644
--- a/Documentation/ABI/testing/sysfs-class-net-mesh
+++ b/Documentation/ABI/testing/sysfs-class-net-mesh
@@ -14,6 +14,15 @@ Description:
14 mesh will be sent using multiple interfaces at the 14 mesh will be sent using multiple interfaces at the
15 same time (if available). 15 same time (if available).
16 16
17What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
18Date: November 2011
19Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
20Description:
21 Indicates whether the bridge loop avoidance feature
22 is enabled. This feature detects and avoids loops
23 between the mesh and devices bridged with the soft
24 interface <mesh_iface>.
25
17What: /sys/class/net/<mesh_iface>/mesh/fragmentation 26What: /sys/class/net/<mesh_iface>/mesh/fragmentation
18Date: October 2010 27Date: October 2010
19Contact: Andreas Langer <an.langer@gmx.de> 28Contact: Andreas Langer <an.langer@gmx.de>
diff --git a/Documentation/ABI/testing/sysfs-devices-power b/Documentation/ABI/testing/sysfs-devices-power
index 840f7d64d483..45000f0db4d4 100644
--- a/Documentation/ABI/testing/sysfs-devices-power
+++ b/Documentation/ABI/testing/sysfs-devices-power
@@ -96,16 +96,26 @@ 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_hit_count 99What: /sys/devices/.../power/wakeup_abort_count
100Date: September 2010 100Date: February 2012
101Contact: Rafael J. Wysocki <rjw@sisk.pl> 101Contact: Rafael J. Wysocki <rjw@sisk.pl>
102Description: 102Description:
103 The /sys/devices/.../wakeup_hit_count attribute contains the 103 The /sys/devices/.../wakeup_abort_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 prevent the system from entering a sleep state. 105 the device might have aborted system transition into a sleep
106 This attribute is read-only. If the device is not enabled to 106 state in progress. This attribute is read-only. If the device
107 wake up the system from sleep states, this attribute is not 107 is not enabled to wake up the system from sleep states, this
108 present. 108 attribute is not 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.
109 119
110What: /sys/devices/.../power/wakeup_active 120What: /sys/devices/.../power/wakeup_active
111Date: September 2010 121Date: September 2010
@@ -148,6 +158,17 @@ Description:
148 not enabled to wake up the system from sleep states, this 158 not enabled to wake up the system from sleep states, this
149 attribute is not present. 159 attribute is not present.
150 160
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 occuring.
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
151What: /sys/devices/.../power/autosuspend_delay_ms 172What: /sys/devices/.../power/autosuspend_delay_ms
152Date: September 2010 173Date: September 2010
153Contact: Alan Stern <stern@rowland.harvard.edu> 174Contact: Alan Stern <stern@rowland.harvard.edu>
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index e7be75b96e4b..5dab36448b44 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -9,31 +9,6 @@ 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
37What: /sys/devices/system/cpu/kernel_max 12What: /sys/devices/system/cpu/kernel_max
38 /sys/devices/system/cpu/offline 13 /sys/devices/system/cpu/offline
39 /sys/devices/system/cpu/online 14 /sys/devices/system/cpu/online
diff --git a/Documentation/ABI/testing/sysfs-devices-system-xen_cpu b/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
new file mode 100644
index 000000000000..9ca02fb2d498
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-devices-system-xen_cpu
@@ -0,0 +1,20 @@
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
new file mode 100644
index 000000000000..57b92cbdceae
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-hid-lenovo-tpkbd
@@ -0,0 +1,38 @@
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-roccat-savu b/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
new file mode 100644
index 000000000000..b42922cf6b1f
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-driver-hid-roccat-savu
@@ -0,0 +1,77 @@
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 The data is 8 bytes long.
44 This file is readonly.
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
77
diff --git a/Documentation/ABI/testing/sysfs-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom
index 0130d6683c14..8d55a83d6921 100644
--- a/Documentation/ABI/testing/sysfs-driver-wacom
+++ b/Documentation/ABI/testing/sysfs-driver-wacom
@@ -9,15 +9,24 @@ Description:
9 or 0 otherwise. Writing to this file one of these values 9 or 0 otherwise. Writing to this file one of these values
10 switches reporting speed. 10 switches reporting speed.
11 11
12What: /sys/class/leds/0005\:056A\:00BD.0001\:selector\:*/
13Date: May 2012
14Kernel Version: 3.5
15Contact: linux-bluetooth@vger.kernel.org
16Description:
17 LED selector for Intuos4 WL. There are 4 leds, but only one LED
18 can be lit at a time. Max brightness is 127.
19
12What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led 20What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/led
13Date: August 2011 21Date: August 2011
14Contact: linux-input@vger.kernel.org 22Contact: linux-input@vger.kernel.org
15Description: 23Description:
16 Attribute group for control of the status LEDs and the OLEDs. 24 Attribute group for control of the status LEDs and the OLEDs.
17 This attribute group is only available for Intuos 4 M, L, 25 This attribute group is only available for Intuos 4 M, L,
18 and XL (with LEDs and OLEDs) and Cintiq 21UX2 and Cintiq 24HD 26 and XL (with LEDs and OLEDs), Intuos 5 (LEDs only), and Cintiq
19 (LEDs only). Therefore its presence implicitly signifies the 27 21UX2 and Cintiq 24HD (LEDs only). Therefore its presence
20 presence of said LEDs and OLEDs on the tablet device. 28 implicitly signifies the presence of said LEDs and OLEDs on the
29 tablet device.
21 30
22What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance 31What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status0_luminance
23Date: August 2011 32Date: August 2011
@@ -40,10 +49,10 @@ What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led0
40Date: August 2011 49Date: August 2011
41Contact: linux-input@vger.kernel.org 50Contact: linux-input@vger.kernel.org
42Description: 51Description:
43 Writing to this file sets which one of the four (for Intuos 4) 52 Writing to this file sets which one of the four (for Intuos 4
44 or of the right four (for Cintiq 21UX2 and Cintiq 24HD) status 53 and Intuos 5) or of the right four (for Cintiq 21UX2 and Cintiq
45 LEDs is active (0..3). The other three LEDs on the same side are 54 24HD) status LEDs is active (0..3). The other three LEDs on the
46 always inactive. 55 same side are always inactive.
47 56
48What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select 57What: /sys/bus/usb/devices/<busnum>-<devnum>:<cfg>.<intf>/wacom_led/status_led1_select
49Date: September 2011 58Date: September 2011
diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
new file mode 100644
index 000000000000..9b31556cfdda
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
@@ -0,0 +1,14 @@
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-power b/Documentation/ABI/testing/sysfs-power
index b464d12761ba..217772615d02 100644
--- a/Documentation/ABI/testing/sysfs-power
+++ b/Documentation/ABI/testing/sysfs-power
@@ -172,3 +172,75 @@ 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.
generated by cgit v1.2.2 (git 2.25.0) at 2024-12-26 22:46:25 -0500