aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ABI/testing')
-rw-r--r--Documentation/ABI/testing/debugfs-pfo-nx-crypto45
-rw-r--r--Documentation/ABI/testing/dev-kmsg90
-rw-r--r--Documentation/ABI/testing/sysfs-bus-i2c-devices-lm353315
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio737
-rw-r--r--Documentation/ABI/testing/sysfs-bus-usb19
-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-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-driver-wacom23
-rw-r--r--Documentation/ABI/testing/sysfs-power59
13 files changed, 1226 insertions, 41 deletions
diff --git a/Documentation/ABI/testing/debugfs-pfo-nx-crypto b/Documentation/ABI/testing/debugfs-pfo-nx-crypto
new file mode 100644
index 00000000000..685d5a44842
--- /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 00000000000..281ecc5f970
--- /dev/null
+++ b/Documentation/ABI/testing/dev-kmsg
@@ -0,0 +1,90 @@
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 The values are separated by a ','. Future extensions might
63 add more comma separated values before the terminating ';'.
64 Unknown values should be gracefully ignored.
65
66 The human readable text string starts directly after the ';'
67 and is terminated by a '\n'. Untrusted values derived from
68 hardware or other facilities are printed, therefore
69 all non-printable characters in the log message are escaped
70 by "\x00" C-style hex encoding.
71
72 A line starting with ' ', is a continuation line, adding
73 key/value pairs to the log message, which provide the machine
74 readable context of the message, for reliable processing in
75 userspace.
76
77 Example:
78 7,160,424069;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
79 SUBSYSTEM=acpi
80 DEVICE=+acpi:PNP0A03:00
81 6,339,5140900;NET: Registered protocol family 10
82 30,340,5690716;udevd[80]: starting version 181
83
84 The DEVICE= key uniquely identifies devices the following way:
85 b12:8 - block dev_t
86 c127:3 - char dev_t
87 n8 - netdev ifindex
88 +sound:card0 - subsystem:devname
89
90Users: dmesg(1), userspace kernel log consumers
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 00000000000..1b62230b33b
--- /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 00000000000..5bc8a476c15
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -0,0 +1,737 @@
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 datardy 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 Celsuis.
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) Data converted by application of offset then scale to
152 radians per second. Has all the equivalent parameters as
153 per voltageY. Units after application of scale and offset are
154 radians per second.
155
156What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
157What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
158What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw
159KernelVersion: 2.6.35
160Contact: linux-iio@vger.kernel.org
161Description:
162 Inclination raw reading about axis x, y or z (may be
163 arbitrarily assigned). Data converted by application of offset
164 and scale to Degrees.
165
166What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
167What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
168What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw
169KernelVersion: 2.6.35
170Contact: linux-iio@vger.kernel.org
171Description:
172 Magnetic field along axis x, y or z (may be arbitrarily
173 assigned). Data converted by application of offset
174 then scale to Gauss.
175
176What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw
177What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw
178What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw
179KernelVersion: 2.6.36
180Contact: linux-iio@vger.kernel.org
181Description:
182 Highest value since some reset condition. These
183 attributes allow access to this and are otherwise
184 the direct equivalent of the <type>Y[_name]_raw attributes.
185
186What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw
187KernelVersion: 2.6.36
188Contact: linux-iio@vger.kernel.org
189Description:
190 A computed peak value based on the sum squared magnitude of
191 the underlying value in the specified directions.
192
193What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
194What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
195What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
196What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
197What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
198What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
199What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
200What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
201KernelVersion: 2.6.35
202Contact: linux-iio@vger.kernel.org
203Description:
204 If known for a device, offset to be added to <type>[Y]_raw prior
205 to scaling by <type>[Y]_scale in order to obtain value in the
206 <type> units as specified in <type>[y]_raw documentation.
207 Not present if the offset is always 0 or unknown. If Y or
208 axis <x|y|z> is not present, then the offset applies to all
209 in channels of <type>.
210 May be writable if a variable offset can be applied on the
211 device. Note that this is different to calibbias which
212 is for devices (or drivers) that apply offsets to compensate
213 for variation between different instances of the part, typically
214 adjusted by using some hardware supported calibration procedure.
215 Calibbias is applied internally, offset is applied in userspace
216 to the _raw output.
217
218What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
219What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
220What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
221What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_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/in_capacitance_scale_available
277KernelVersion: 2.635
278Contact: linux-iio@vger.kernel.org
279Description:
280 If a discrete set of scale values are available, they
281 are listed in this attribute.
282
283What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
284KernelVersion: 2.6.35
285Contact: linux-iio@vger.kernel.org
286Description:
287 Hardware applied gain factor. If shared across all channels,
288 <type>_hardwaregain is used.
289
290What: /sys/.../in_accel_filter_low_pass_3db_frequency
291What: /sys/.../in_magn_filter_low_pass_3db_frequency
292What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
293KernelVersion: 3.2
294Contact: linux-iio@vger.kernel.org
295Description:
296 If a known or controllable low pass filter is applied
297 to the underlying data channel, then this parameter
298 gives the 3dB frequency of the filter in Hz.
299
300What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
301KernelVersion: 2.6.37
302Contact: linux-iio@vger.kernel.org
303Description:
304 Raw (unscaled, no bias etc.) output voltage for
305 channel Y. The number must always be specified and
306 unique if the output corresponds to a single channel.
307
308What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
309KernelVersion: 2.6.37
310Contact: linux-iio@vger.kernel.org
311Description:
312 Raw (unscaled, no bias etc.) output voltage for an aggregate of
313 channel Y, channel Z, etc. This interface is available in cases
314 where a single output sets the value for multiple channels
315 simultaneously.
316
317What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
318What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
319KernelVersion: 2.6.38
320Contact: linux-iio@vger.kernel.org
321Description:
322 Specifies the output powerdown mode.
323 DAC output stage is disconnected from the amplifier and
324 1kohm_to_gnd: connected to ground via an 1kOhm resistor
325 100kohm_to_gnd: connected to ground via an 100kOhm resistor
326 three_state: left floating
327 For a list of available output power down options read
328 outX_powerdown_mode_available. If Y is not present the
329 mode is shared across all outputs.
330
331What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
332What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
333KernelVersion: 2.6.38
334Contact: linux-iio@vger.kernel.org
335Description:
336 Lists all available output power down modes.
337 If Y is not present the mode is shared across all outputs.
338
339What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
340What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
341KernelVersion: 2.6.38
342Contact: linux-iio@vger.kernel.org
343Description:
344 Writing 1 causes output Y to enter the power down mode specified
345 by the corresponding outY_powerdown_mode. Clearing returns to
346 normal operation. Y may be suppressed if all outputs are
347 controlled together.
348
349What: /sys/bus/iio/devices/iio:deviceX/events
350KernelVersion: 2.6.35
351Contact: linux-iio@vger.kernel.org
352Description:
353 Configuration of which hardware generated events are passed up
354 to user-space.
355
356What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
357What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
358What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
359What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
360What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
361What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
362What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
363What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
364What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
365What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
366What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
367What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
368What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
369What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
370What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
371What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
372What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
373What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
374What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
375What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
376What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
377What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
378What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
379What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
380KernelVersion: 2.6.37
381Contact: linux-iio@vger.kernel.org
382Description:
383 Event generated when channel passes a threshold in the specified
384 (_rising|_falling) direction. If the direction is not specified,
385 then either the device will report an event which ever direction
386 a single threshold value is passed in (e.g.
387 <type>[Y][_name]_<raw|input>_thresh_value) or
388 <type>[Y][_name]_<raw|input>_thresh_rising_value and
389 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
390 different values, but the device can only enable both thresholds
391 or neither.
392 Note the driver will assume the last p events requested are
393 to be enabled where p is however many it supports (which may
394 vary depending on the exact set requested. So if you want to be
395 sure you have set what you think you have, check the contents of
396 these attributes after everything is configured. Drivers may
397 have to buffer any parameters so that they are consistent when
398 a given event type is enabled a future point (and not those for
399 whatever event was previously enabled).
400
401What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
402What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
403What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
404What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
405What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
406What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
407What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
408What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
409What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
410What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
411What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
412What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
413What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
414What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
415What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
416What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
417What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
418What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
419What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
420What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
421What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
422What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
423What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
424What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
425KernelVersion: 2.6.37
426Contact: linux-iio@vger.kernel.org
427Description:
428 Event generated when channel passes a threshold on the rate of
429 change (1st differential) in the specified (_rising|_falling)
430 direction. If the direction is not specified, then either the
431 device will report an event which ever direction a single
432 threshold value is passed in (e.g.
433 <type>[Y][_name]_<raw|input>_roc_value) or
434 <type>[Y][_name]_<raw|input>_roc_rising_value and
435 <type>[Y][_name]_<raw|input>_roc_falling_value may take
436 different values, but the device can only enable both rate of
437 change thresholds or neither.
438 Note the driver will assume the last p events requested are
439 to be enabled where p is however many it supports (which may
440 vary depending on the exact set requested. So if you want to be
441 sure you have set what you think you have, check the contents of
442 these attributes after everything is configured. Drivers may
443 have to buffer any parameters so that they are consistent when
444 a given event type is enabled a future point (and not those for
445 whatever event was previously enabled).
446
447What: /sys/.../events/in_accel_x_raw_thresh_rising_value
448What: /sys/.../events/in_accel_x_raw_thresh_falling_value
449What: /sys/.../events/in_accel_y_raw_thresh_rising_value
450What: /sys/.../events/in_accel_y_raw_thresh_falling_value
451What: /sys/.../events/in_accel_z_raw_thresh_rising_value
452What: /sys/.../events/in_accel_z_raw_thresh_falling_value
453What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
454What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
455What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
456What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
457What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
458What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
459What: /sys/.../events/in_magn_x_raw_thresh_rising_value
460What: /sys/.../events/in_magn_x_raw_thresh_falling_value
461What: /sys/.../events/in_magn_y_raw_thresh_rising_value
462What: /sys/.../events/in_magn_y_raw_thresh_falling_value
463What: /sys/.../events/in_magn_z_raw_thresh_rising_value
464What: /sys/.../events/in_magn_z_raw_thresh_falling_value
465What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
466What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
467What: /sys/.../events/in_voltageY_raw_thresh_rising_value
468What: /sys/.../events/in_voltageY_raw_thresh_falling_value
469What: /sys/.../events/in_tempY_raw_thresh_rising_value
470What: /sys/.../events/in_tempY_raw_thresh_falling_value
471What: /sys/.../events/in_illuminance0_thresh_falling_value
472what: /sys/.../events/in_illuminance0_thresh_rising_value
473what: /sys/.../events/in_proximity0_thresh_falling_value
474what: /sys/.../events/in_proximity0_thresh_rising_value
475KernelVersion: 2.6.37
476Contact: linux-iio@vger.kernel.org
477Description:
478 Specifies the value of threshold that the device is comparing
479 against for the events enabled by
480 <type>Y[_name]_thresh[_rising|falling]_en.
481 If separate attributes exist for the two directions, but
482 direction is not specified for this attribute, then a single
483 threshold value applies to both directions.
484 The raw or input element of the name indicates whether the
485 value is in raw device units or in processed units (as _raw
486 and _input do on sysfs direct channel read attributes).
487
488What: /sys/.../events/in_accel_x_raw_roc_rising_value
489What: /sys/.../events/in_accel_x_raw_roc_falling_value
490What: /sys/.../events/in_accel_y_raw_roc_rising_value
491What: /sys/.../events/in_accel_y_raw_roc_falling_value
492What: /sys/.../events/in_accel_z_raw_roc_rising_value
493What: /sys/.../events/in_accel_z_raw_roc_falling_value
494What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
495What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
496What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
497What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
498What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
499What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
500What: /sys/.../events/in_magn_x_raw_roc_rising_value
501What: /sys/.../events/in_magn_x_raw_roc_falling_value
502What: /sys/.../events/in_magn_y_raw_roc_rising_value
503What: /sys/.../events/in_magn_y_raw_roc_falling_value
504What: /sys/.../events/in_magn_z_raw_roc_rising_value
505What: /sys/.../events/in_magn_z_raw_roc_falling_value
506What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
507What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
508What: /sys/.../events/in_voltageY_raw_roc_rising_value
509What: /sys/.../events/in_voltageY_raw_roc_falling_value
510What: /sys/.../events/in_tempY_raw_roc_rising_value
511What: /sys/.../events/in_tempY_raw_roc_falling_value
512KernelVersion: 2.6.37
513Contact: linux-iio@vger.kernel.org
514Description:
515 Specifies the value of rate of change threshold that the
516 device is comparing against for the events enabled by
517 <type>[Y][_name]_roc[_rising|falling]_en.
518 If separate attributes exist for the two directions,
519 but direction is not specified for this attribute,
520 then a single threshold value applies to both directions.
521 The raw or input element of the name indicates whether the
522 value is in raw device units or in processed units (as _raw
523 and _input do on sysfs direct channel read attributes).
524
525What: /sys/.../events/in_accel_x_thresh_rising_period
526What: /sys/.../events/in_accel_x_thresh_falling_period
527hat: /sys/.../events/in_accel_x_roc_rising_period
528What: /sys/.../events/in_accel_x_roc_falling_period
529What: /sys/.../events/in_accel_y_thresh_rising_period
530What: /sys/.../events/in_accel_y_thresh_falling_period
531What: /sys/.../events/in_accel_y_roc_rising_period
532What: /sys/.../events/in_accel_y_roc_falling_period
533What: /sys/.../events/in_accel_z_thresh_rising_period
534What: /sys/.../events/in_accel_z_thresh_falling_period
535What: /sys/.../events/in_accel_z_roc_rising_period
536What: /sys/.../events/in_accel_z_roc_falling_period
537What: /sys/.../events/in_anglvel_x_thresh_rising_period
538What: /sys/.../events/in_anglvel_x_thresh_falling_period
539What: /sys/.../events/in_anglvel_x_roc_rising_period
540What: /sys/.../events/in_anglvel_x_roc_falling_period
541What: /sys/.../events/in_anglvel_y_thresh_rising_period
542What: /sys/.../events/in_anglvel_y_thresh_falling_period
543What: /sys/.../events/in_anglvel_y_roc_rising_period
544What: /sys/.../events/in_anglvel_y_roc_falling_period
545What: /sys/.../events/in_anglvel_z_thresh_rising_period
546What: /sys/.../events/in_anglvel_z_thresh_falling_period
547What: /sys/.../events/in_anglvel_z_roc_rising_period
548What: /sys/.../events/in_anglvel_z_roc_falling_period
549What: /sys/.../events/in_magn_x_thresh_rising_period
550What: /sys/.../events/in_magn_x_thresh_falling_period
551What: /sys/.../events/in_magn_x_roc_rising_period
552What: /sys/.../events/in_magn_x_roc_falling_period
553What: /sys/.../events/in_magn_y_thresh_rising_period
554What: /sys/.../events/in_magn_y_thresh_falling_period
555What: /sys/.../events/in_magn_y_roc_rising_period
556What: /sys/.../events/in_magn_y_roc_falling_period
557What: /sys/.../events/in_magn_z_thresh_rising_period
558What: /sys/.../events/in_magn_z_thresh_falling_period
559What: /sys/.../events/in_magn_z_roc_rising_period
560What: /sys/.../events/in_magn_z_roc_falling_period
561What: /sys/.../events/in_voltageY_supply_thresh_rising_period
562What: /sys/.../events/in_voltageY_supply_thresh_falling_period
563What: /sys/.../events/in_voltageY_supply_roc_rising_period
564What: /sys/.../events/in_voltageY_supply_roc_falling_period
565What: /sys/.../events/in_voltageY_thresh_rising_period
566What: /sys/.../events/in_voltageY_thresh_falling_period
567What: /sys/.../events/in_voltageY_roc_rising_period
568What: /sys/.../events/in_voltageY_roc_falling_period
569What: /sys/.../events/in_tempY_thresh_rising_period
570What: /sys/.../events/in_tempY_thresh_falling_period
571What: /sys/.../events/in_tempY_roc_rising_period
572What: /sys/.../events/in_tempY_roc_falling_period
573What: /sys/.../events/in_accel_x&y&z_mag_falling_period
574What: /sys/.../events/in_intensity0_thresh_period
575What: /sys/.../events/in_proximity0_thresh_period
576KernelVersion: 2.6.37
577Contact: linux-iio@vger.kernel.org
578Description:
579 Period of time (in seconds) for which the condition must be
580 met before an event is generated. If direction is not
581 specified then this period applies to both directions.
582
583What: /sys/.../iio:deviceX/events/in_accel_mag_en
584What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
585What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
586What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
587What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
588What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
589What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
590What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
591What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
592What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
593What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
594What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
595What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
596What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
597KernelVersion: 2.6.37
598Contact: linux-iio@vger.kernel.org
599Description:
600 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
601 magnitude of the channel is compared to the threshold, not its
602 signed value.
603
604What: /sys/.../events/in_accel_raw_mag_value
605What: /sys/.../events/in_accel_x_raw_mag_rising_value
606What: /sys/.../events/in_accel_y_raw_mag_rising_value
607What: /sys/.../events/in_accel_z_raw_mag_rising_value
608KernelVersion: 2.6.37
609Contact: linux-iio@vger.kernel.org
610Description:
611 The value to which the magnitude of the channel is compared. If
612 number or direction is not specified, applies to all channels of
613 this type.
614
615What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
616KernelVersion: 2.6.35
617Contact: linux-iio@vger.kernel.org
618Description:
619 The name of the trigger source being used, as per string given
620 in /sys/class/iio/triggerY/name.
621
622What: /sys/bus/iio/devices/iio:deviceX/buffer/length
623KernelVersion: 2.6.35
624Contact: linux-iio@vger.kernel.org
625Description:
626 Number of scans contained by the buffer.
627
628What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum
629KernelVersion: 2.6.37
630Contact: linux-iio@vger.kernel.org
631Description:
632 Bytes per scan. Due to alignment fun, the scan may be larger
633 than implied directly by the scan_element parameters.
634
635What: /sys/bus/iio/devices/iio:deviceX/buffer/enable
636KernelVersion: 2.6.35
637Contact: linux-iio@vger.kernel.org
638Description:
639 Actually start the buffer capture up. Will start trigger
640 if first device and appropriate.
641
642What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements
643KernelVersion: 2.6.37
644Contact: linux-iio@vger.kernel.org
645Description:
646 Directory containing interfaces for elements that will be
647 captured for a single triggered sample set in the buffer.
648
649What: /sys/.../buffer/scan_elements/in_accel_x_en
650What: /sys/.../buffer/scan_elements/in_accel_y_en
651What: /sys/.../buffer/scan_elements/in_accel_z_en
652What: /sys/.../buffer/scan_elements/in_anglvel_x_en
653What: /sys/.../buffer/scan_elements/in_anglvel_y_en
654What: /sys/.../buffer/scan_elements/in_anglvel_z_en
655What: /sys/.../buffer/scan_elements/in_magn_x_en
656What: /sys/.../buffer/scan_elements/in_magn_y_en
657What: /sys/.../buffer/scan_elements/in_magn_z_en
658What: /sys/.../buffer/scan_elements/in_timestamp_en
659What: /sys/.../buffer/scan_elements/in_voltageY_supply_en
660What: /sys/.../buffer/scan_elements/in_voltageY_en
661What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en
662What: /sys/.../buffer/scan_elements/in_incli_x_en
663What: /sys/.../buffer/scan_elements/in_incli_y_en
664KernelVersion: 2.6.37
665Contact: linux-iio@vger.kernel.org
666Description:
667 Scan element control for triggered data capture.
668
669What: /sys/.../buffer/scan_elements/in_accel_type
670What: /sys/.../buffer/scan_elements/in_anglvel_type
671What: /sys/.../buffer/scan_elements/in_magn_type
672What: /sys/.../buffer/scan_elements/in_incli_type
673What: /sys/.../buffer/scan_elements/in_voltageY_type
674What: /sys/.../buffer/scan_elements/in_voltage-in_type
675What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
676What: /sys/.../buffer/scan_elements/in_timestamp_type
677KernelVersion: 2.6.37
678Contact: linux-iio@vger.kernel.org
679Description:
680 Description of the scan element data storage within the buffer
681 and hence the form in which it is read from user-space.
682 Form is [be|le]:[s|u]bits/storagebits[>>shift].
683 be or le specifies big or little endian. s or u specifies if
684 signed (2's complement) or unsigned. bits is the number of bits
685 of data and storagebits is the space (after padding) that it
686 occupies in the buffer. shift if specified, is the shift that
687 needs to be applied prior to masking out unused bits. Some
688 devices put their data in the middle of the transferred elements
689 with additional information on both sides. Note that some
690 devices will have additional information in the unused bits
691 so to get a clean value, the bits value must be used to mask
692 the buffer output value appropriately. The storagebits value
693 also specifies the data alignment. So s48/64>>2 will be a
694 signed 48 bit integer stored in a 64 bit location aligned to
695 a a64 bit boundary. To obtain the clean value, shift right 2
696 and apply a mask to zero the top 16 bits of the result.
697 For other storage combinations this attribute will be extended
698 appropriately.
699
700What: /sys/.../buffer/scan_elements/in_accel_type_available
701KernelVersion: 2.6.37
702Contact: linux-iio@vger.kernel.org
703Description:
704 If the type parameter can take one of a small set of values,
705 this attribute lists them.
706
707What: /sys/.../buffer/scan_elements/in_voltageY_index
708What: /sys/.../buffer/scan_elements/in_voltageY_supply_index
709What: /sys/.../buffer/scan_elements/in_accel_x_index
710What: /sys/.../buffer/scan_elements/in_accel_y_index
711What: /sys/.../buffer/scan_elements/in_accel_z_index
712What: /sys/.../buffer/scan_elements/in_anglvel_x_index
713What: /sys/.../buffer/scan_elements/in_anglvel_y_index
714What: /sys/.../buffer/scan_elements/in_anglvel_z_index
715What: /sys/.../buffer/scan_elements/in_magn_x_index
716What: /sys/.../buffer/scan_elements/in_magn_y_index
717What: /sys/.../buffer/scan_elements/in_magn_z_index
718What: /sys/.../buffer/scan_elements/in_incli_x_index
719What: /sys/.../buffer/scan_elements/in_incli_y_index
720What: /sys/.../buffer/scan_elements/in_timestamp_index
721KernelVersion: 2.6.37
722Contact: linux-iio@vger.kernel.org
723Description:
724 A single positive integer specifying the position of this
725 scan element in the buffer. Note these are not dependent on
726 what is enabled and may not be contiguous. Thus for user-space
727 to establish the full layout these must be used in conjunction
728 with all _en attributes to establish which channels are present,
729 and the relevant _type attributes to establish the data storage
730 format.
731
732What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
733KernelVersion: 2.6.38
734Contact: linux-iio@vger.kernel.org
735Description:
736 This attribute is used to read the amount of quadrature error
737 present in the device at a given time.
diff --git a/Documentation/ABI/testing/sysfs-bus-usb b/Documentation/ABI/testing/sysfs-bus-usb
index 7c22a532fdf..6df4e6f5756 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,7 @@ 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.
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 00000000000..77cf7ac949a
--- /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 00000000000..20ab361bd8c
--- /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 00000000000..620ebb3b9ba
--- /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-net-mesh b/Documentation/ABI/testing/sysfs-class-net-mesh
index b218e0f8bdb..c81fe89c4c4 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 840f7d64d48..45000f0db4d 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 e7be75b96e4..5dab36448b4 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-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom
index 0130d6683c1..8d55a83d692 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-power b/Documentation/ABI/testing/sysfs-power
index b464d12761b..31725ffeeb3 100644
--- a/Documentation/ABI/testing/sysfs-power
+++ b/Documentation/ABI/testing/sysfs-power
@@ -172,3 +172,62 @@ 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.
generated by cgit v1.2.2 (git 2.25.0) at 2025-01-27 21:41:26 -0500