aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2012-05-22 19:34:21 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2012-05-22 19:34:21 -0400
commitfb09bafda67041b74a668dc9d77735e36bd33d3b (patch)
tree2dd32b65062a95045468fdcab366ecdb8e4fcac6 /Documentation/ABI
parent94b5aff4c6f72fee6b0f49d49e4fa8b204e8ded9 (diff)
parentc3c6cc91b0ae7b3d598488ad0b593bafba4a0817 (diff)
Merge tag 'staging-3.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
Pull staging tree changes from Greg Kroah-Hartman: "Here is the big staging tree pull request for the 3.5-rc1 merge window. Loads of changes here, and we just narrowly added more lines than we added: 622 files changed, 28356 insertions(+), 26059 deletions(-) But, good news is that there is a number of subsystems that moved out of the staging tree, to their respective "real" portions of the kernel. Code that moved out was: - iio core code - mei driver - vme core and bridge drivers There was one broken network driver that moved into staging as a step before it is removed from the tree (pc300), and there was a few new drivers added to the tree: - new iio drivers - gdm72xx wimax USB driver - ipack subsystem and 2 drivers All of the movements around have acks from the various subsystem maintainers, and all of this has been in the linux-next tree for a while. Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>" Fixed up various trivial conflicts, along with a non-trivial one found in -next and pointed out by Olof Johanssen: a clean - but incorrect - merge of the arch/arm/boot/dts/at91sam9g20.dtsi file. Fix up manually as per Stephen Rothwell. * tag 'staging-3.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging: (536 commits) Staging: bcm: Remove two unused variables from Adapter.h Staging: bcm: Removes the volatile type definition from Adapter.h Staging: bcm: Rename all "INT" to "int" in Adapter.h Staging: bcm: Fix warning: __packed vs. __attribute__((packed)) in Adapter.h Staging: bcm: Correctly format all comments in Adapter.h Staging: bcm: Fix all whitespace issues in Adapter.h Staging: bcm: Properly format braces in Adapter.h Staging: ipack/bridges/tpci200: remove unneeded casts Staging: ipack/bridges/tpci200: remove TPCI200_SHORTNAME constant Staging: ipack: remove board_name and bus_name fields from struct ipack_device Staging: ipack: improve the register of a bus and a device in the bus. staging: comedi: cleanup all the comedi_driver 'detach' functions staging: comedi: remove all 'default N' in Kconfig staging: line6/config.h: Delete unused header staging: gdm72xx depends on NET staging: gdm72xx: Set up parent link in sysfs for gdm72xx devices staging: drm/omap: initial dmabuf/prime import support staging: drm/omap: dmabuf/prime mmap support pstore/ram: Add ECC support pstore/ram: Switch to persistent_ram routines ...
Diffstat (limited to 'Documentation/ABI')
-rw-r--r--Documentation/ABI/testing/sysfs-bus-iio737
1 files changed, 737 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
new file mode 100644
index 000000000000..5bc8a476c15e
--- /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.
generated by cgit v1.2.2 (git 2.25.0) at 2024-12-28 21:21:05 -0500