blob: e0f68f6a0e2af5703845db69855b29127dc049dd [file] [log] [blame]
Jonathan Cameronb3874062011-08-30 12:32:49 +01001What: /sys/bus/iio/devices/iio:deviceX
Jonathan Camerone34d2c52010-05-04 14:43:05 +01002KernelVersion: 2.6.35
3Contact: linux-iio@vger.kernel.org
4Description:
Jonathan Cameronde1874b2011-08-12 16:55:38 +01005 Hardware chip or device accessed by one communication port.
Jonathan Cameronf386caa2010-11-22 23:31:16 +00006 Corresponds to a grouping of sensor channels. X is the IIO
7 index of the device.
Jonathan Camerone34d2c52010-05-04 14:43:05 +01008
Jonathan Cameronf386caa2010-11-22 23:31:16 +00009What: /sys/bus/iio/devices/triggerX
Jonathan Camerone34d2c52010-05-04 14:43:05 +010010KernelVersion: 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.
Jonathan Cameronf386caa2010-11-22 23:31:16 +000017 periodic timer, GPIO or high resolution timer).
Jonathan Camerone34d2c52010-05-04 14:43:05 +010018 Contains trigger type specific elements. These do not
19 generalize well and hence are not documented in this file.
Jonathan Cameronf386caa2010-11-22 23:31:16 +000020 X is the IIO index of the trigger.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010021
Jonathan Cameronb3874062011-08-30 12:32:49 +010022What: /sys/bus/iio/devices/iio:deviceX/buffer
Jonathan Camerone34d2c52010-05-04 14:43:05 +010023KernelVersion: 2.6.35
24Contact: linux-iio@vger.kernel.org
25Description:
Jonathan Cameronb3874062011-08-30 12:32:49 +010026 Directory of attributes relating to the buffer for the device.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010027
Jonathan Cameronb3874062011-08-30 12:32:49 +010028What: /sys/bus/iio/devices/iio:deviceX/name
Jonathan Camerone34d2c52010-05-04 14:43:05 +010029KernelVersion: 2.6.35
30Contact: linux-iio@vger.kernel.org
31Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +000032 Description of the physical chip / device for device X.
33 Typically a part number.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010034
Jonathan Cameronb3874062011-08-30 12:32:49 +010035What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency
Jonathan Cameron15739cd2011-09-21 11:15:51 +010036What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency
37What: /sys/bus/iio/devices/triggerX/sampling_frequency
Jonathan Camerone34d2c52010-05-04 14:43:05 +010038KernelVersion: 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
Peter Meerwald8b417d72012-06-12 15:31:27 +020043 parameter has an effect on input filters etc. rather than
Jonathan Camerone34d2c52010-05-04 14:43:05 +010044 simply controlling when the input is sampled. As this
Peter Meerwald8b417d72012-06-12 15:31:27 +020045 effects data ready triggers, hardware buffers and the sysfs
Jonathan Camerone34d2c52010-05-04 14:43:05 +010046 direct access interfaces, it may be found in any of the
47 relevant directories. If it effects all of the above
Jonathan Cameron15739cd2011-09-21 11:15:51 +010048 then it is to be found in the base device directory.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010049
Jonathan Cameronb3874062011-08-30 12:32:49 +010050What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available
Jonathan Cameron15739cd2011-09-21 11:15:51 +010051What: /sys/.../iio:deviceX/buffer/sampling_frequency_available
52What: /sys/bus/iio/devices/triggerX/sampling_frequency_available
Jonathan Camerone34d2c52010-05-04 14:43:05 +010053KernelVersion: 2.6.35
54Contact: linux-iio@vger.kernel.org
55Description:
56 When the internal sampling clock can only take a small
Jonathan Cameronf386caa2010-11-22 23:31:16 +000057 discrete set of values, this file lists those available.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010058
Jonathan Cameronb3874062011-08-30 12:32:49 +010059What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio
Michael Hennerichb9618c02011-02-22 21:46:18 +010060KernelVersion: 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
Jonathan Cameronb3874062011-08-30 12:32:49 +010066What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available
Michael Hennerichb9618c02011-02-22 21:46:18 +010067KernelVersion: 2.6.38
68Contact: linux-iio@vger.kernel.org
69Description:
70 Hardware dependent values supported by the oversampling filter.
71
Jonathan Camerona37b5492011-09-02 17:14:35 +010072What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw
73What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
Jonathan Camerone34d2c52010-05-04 14:43:05 +010074KernelVersion: 2.6.35
75Contact: linux-iio@vger.kernel.org
76Description:
Peter Meerwald8b417d72012-06-12 15:31:27 +020077 Raw (unscaled no bias removal etc.) voltage measurement from
Jonathan Cameronf386caa2010-11-22 23:31:16 +000078 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
Jonathan Cameron15739cd2011-09-21 11:15:51 +010081 unique to allow association with event codes. Units after
82 application of scale and offset are microvolts.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010083
Jonathan Camerona37b5492011-09-02 17:14:35 +010084What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
Jonathan Camerone34d2c52010-05-04 14:43:05 +010085KernelVersion: 2.6.35
86Contact: linux-iio@vger.kernel.org
87Description:
88 Raw (unscaled) differential voltage measurement equivalent to
Jonathan Cameronf386caa2010-11-22 23:31:16 +000089 channel Y - channel Z where these channel numbers apply to the
Jonathan Cameron2f3cc662010-10-08 12:14:12 +010090 physically equivalent inputs when non differential readings are
91 separately available. In differential only parts, then all that
Jonathan Cameron15739cd2011-09-21 11:15:51 +010092 is required is a consistent labeling. Units after application
93 of scale and offset are microvolts.
Jonathan Camerone34d2c52010-05-04 14:43:05 +010094
Jonathan Cameron0baf29d2011-09-21 11:15:52 +010095What: /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
Jonathan Cameron68284a12012-04-25 15:54:57 +0100111 of scale and offset are nanofarads.
Jonathan Cameron0baf29d2011-09-21 11:15:52 +0100112
Jonathan Camerona37b5492011-09-02 17:14:35 +0100113What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100114What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw
Jonathan Camerona37b5492011-09-02 17:14:35 +0100115What: /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
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000118KernelVersion: 2.6.35
119Contact: linux-iio@vger.kernel.org
120Description:
Peter Meerwald8b417d72012-06-12 15:31:27 +0200121 Raw (unscaled no bias removal etc.) temperature measurement.
Jonathan Cameron68284a12012-04-25 15:54:57 +0100122 If an axis is specified it generally means that the temperature
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000123 sensor is associated with one part of a compound device (e.g.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100124 a gyroscope axis). Units after application of scale and offset
125 are milli degrees Celsuis.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000126
Jonathan Camerona37b5492011-09-02 17:14:35 +0100127What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
Michael Hennerich7c31b982011-02-24 12:32:45 +0100128KernelVersion: 2.6.38
129Contact: linux-iio@vger.kernel.org
130Description:
131 Scaled temperature measurement in milli degrees Celsius.
132
Jonathan Camerona37b5492011-09-02 17:14:35 +0100133What: /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
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100136KernelVersion: 2.6.35
137Contact: linux-iio@vger.kernel.org
138Description:
139 Acceleration in direction x, y or z (may be arbitrarily assigned
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100140 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.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100143
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100144What: /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
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100147KernelVersion: 2.6.35
148Contact: linux-iio@vger.kernel.org
149Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100150 Angular velocity about axis x, y or z (may be arbitrarily
Peter Meerwald8b417d72012-06-12 15:31:27 +0200151 assigned). Has all the equivalent parameters as per voltageY.
152 Units after application of scale and offset are radians per
153 second.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100154
Jonathan Camerona37b5492011-09-02 17:14:35 +0100155What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
156What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
157What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw
Jonathan Camerone5107fb2010-05-07 15:38:57 +0100158KernelVersion: 2.6.35
159Contact: linux-iio@vger.kernel.org
160Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000161 Inclination raw reading about axis x, y or z (may be
162 arbitrarily assigned). Data converted by application of offset
Peter Meerwald8b417d72012-06-12 15:31:27 +0200163 and scale to degrees.
Jonathan Camerone5107fb2010-05-07 15:38:57 +0100164
Jonathan Camerona37b5492011-09-02 17:14:35 +0100165What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
166What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
167What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100168KernelVersion: 2.6.35
169Contact: linux-iio@vger.kernel.org
170Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100171 Magnetic field along axis x, y or z (may be arbitrarily
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100172 assigned). Data converted by application of offset
173 then scale to Gauss.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100174
Jonathan Camerona37b5492011-09-02 17:14:35 +0100175What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw
176What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw
177What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000178KernelVersion: 2.6.36
179Contact: linux-iio@vger.kernel.org
180Description:
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100181 Highest value since some reset condition. These
182 attributes allow access to this and are otherwise
183 the direct equivalent of the <type>Y[_name]_raw attributes.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000184
Jonathan Camerona37b5492011-09-02 17:14:35 +0100185What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000186KernelVersion: 2.6.36
187Contact: linux-iio@vger.kernel.org
188Description:
189 A computed peak value based on the sum squared magnitude of
190 the underlying value in the specified directions.
191
Jonathan Camerona37b5492011-09-02 17:14:35 +0100192What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100193What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
194What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
195What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
196What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
197What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
198What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
Jonathan Camerona37b5492011-09-02 17:14:35 +0100199What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100200KernelVersion: 2.6.35
201Contact: linux-iio@vger.kernel.org
202Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000203 If known for a device, offset to be added to <type>[Y]_raw prior
204 to scaling by <type>[Y]_scale in order to obtain value in the
Peter Meerwald8b417d72012-06-12 15:31:27 +0200205 <type> units as specified in <type>[Y]_raw documentation.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100206 Not present if the offset is always 0 or unknown. If Y or
207 axis <x|y|z> is not present, then the offset applies to all
208 in channels of <type>.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000209 May be writable if a variable offset can be applied on the
210 device. Note that this is different to calibbias which
211 is for devices (or drivers) that apply offsets to compensate
212 for variation between different instances of the part, typically
213 adjusted by using some hardware supported calibration procedure.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100214 Calibbias is applied internally, offset is applied in userspace
215 to the _raw output.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100216
Jonathan Camerona37b5492011-09-02 17:14:35 +0100217What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
218What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
219What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
220What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
221What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
222What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100223What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
Jonathan Camerona37b5492011-09-02 17:14:35 +0100224What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
225What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
226What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
227What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100228KernelVersion: 2.6.35
229Contact: linux-iio@vger.kernel.org
230Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000231 If known for a device, scale to be applied to <type>Y[_name]_raw
232 post addition of <type>[Y][_name]_offset in order to obtain the
233 measured value in <type> units as specified in
Jonathan Cameron68284a12012-04-25 15:54:57 +0100234 <type>[Y][_name]_raw documentation. If shared across all in
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100235 channels then Y and <x|y|z> are not present and the value is
236 called <type>[Y][_name]_scale. The peak modifier means this
237 value is applied to <type>Y[_name]_peak_raw values.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100238
Jonathan Camerona37b5492011-09-02 17:14:35 +0100239What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias
240What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias
241What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100242What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias
243What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias
244What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias
Jon Brenner3c97c082012-04-24 11:56:49 -0500245What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias
246What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000247KernelVersion: 2.6.35
248Contact: linux-iio@vger.kernel.org
249Description:
Peter Meerwald8b417d72012-06-12 15:31:27 +0200250 Hardware applied calibration offset (assumed to fix production
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100251 inaccuracies).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100252
Jonathan Camerona37b5492011-09-02 17:14:35 +0100253What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
254What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
255What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
256What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
257What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
258What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100259What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
260What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
261What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
Jon Brenner3c97c082012-04-24 11:56:49 -0500262what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
263what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000264KernelVersion: 2.6.35
265Contact: linux-iio@vger.kernel.org
266Description:
Peter Meerwald8b417d72012-06-12 15:31:27 +0200267 Hardware applied calibration scale factor (assumed to fix
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000268 production inaccuracies). If shared across all channels,
269 <type>_calibscale is used.
270
Jonathan Camerona37b5492011-09-02 17:14:35 +0100271What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100272What: /sys/.../iio:deviceX/in_voltageX_scale_available
273What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
274What: /sys/.../iio:deviceX/out_voltageX_scale_available
Jonathan Cameron0baf29d2011-09-21 11:15:52 +0100275What: /sys/.../iio:deviceX/in_capacitance_scale_available
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000276KernelVersion: 2.635
277Contact: linux-iio@vger.kernel.org
278Description:
Peter Meerwald8b417d72012-06-12 15:31:27 +0200279 If a discrete set of scale values is available, they
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000280 are listed in this attribute.
281
Michael Hennerichb65d6212012-05-11 11:36:53 +0200282What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
283KernelVersion: 2.6.35
284Contact: linux-iio@vger.kernel.org
285Description:
286 Hardware applied gain factor. If shared across all channels,
287 <type>_hardwaregain is used.
288
Jonathan Cameron0c22db4392011-11-27 11:39:14 +0000289What: /sys/.../in_accel_filter_low_pass_3db_frequency
290What: /sys/.../in_magn_filter_low_pass_3db_frequency
291What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
292KernelVersion: 3.2
293Contact: linux-iio@vger.kernel.org
294Description:
295 If a known or controllable low pass filter is applied
296 to the underlying data channel, then this parameter
297 gives the 3dB frequency of the filter in Hz.
298
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100299What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
Roland Stigge98069c32011-01-13 17:43:29 +0100300KernelVersion: 2.6.37
301Contact: linux-iio@vger.kernel.org
302Description:
303 Raw (unscaled, no bias etc.) output voltage for
304 channel Y. The number must always be specified and
305 unique if the output corresponds to a single channel.
306
Jonathan Camerona37b5492011-09-02 17:14:35 +0100307What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
Roland Stigge98069c32011-01-13 17:43:29 +0100308KernelVersion: 2.6.37
309Contact: linux-iio@vger.kernel.org
310Description:
311 Raw (unscaled, no bias etc.) output voltage for an aggregate of
312 channel Y, channel Z, etc. This interface is available in cases
313 where a single output sets the value for multiple channels
314 simultaneously.
315
Jonathan Camerona37b5492011-09-02 17:14:35 +0100316What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
317What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
Michael Hennerich14f88f12011-03-09 16:01:45 +0100318KernelVersion: 2.6.38
319Contact: linux-iio@vger.kernel.org
320Description:
321 Specifies the output powerdown mode.
322 DAC output stage is disconnected from the amplifier and
Peter Meerwald8b417d72012-06-12 15:31:27 +0200323 1kohm_to_gnd: connected to ground via an 1kOhm resistor,
324 6kohm_to_gnd: connected to ground via a 6kOhm resistor,
325 20kohm_to_gnd: connected to ground via a 20kOhm resistor,
326 100kohm_to_gnd: connected to ground via an 100kOhm resistor,
327 three_state: left floating.
Michael Hennerich14f88f12011-03-09 16:01:45 +0100328 For a list of available output power down options read
329 outX_powerdown_mode_available. If Y is not present the
330 mode is shared across all outputs.
331
Jonathan Camerona37b5492011-09-02 17:14:35 +0100332What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
333What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
Michael Hennerich14f88f12011-03-09 16:01:45 +0100334KernelVersion: 2.6.38
335Contact: linux-iio@vger.kernel.org
336Description:
337 Lists all available output power down modes.
338 If Y is not present the mode is shared across all outputs.
339
Jonathan Camerona37b5492011-09-02 17:14:35 +0100340What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
341What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
Michael Hennerich14f88f12011-03-09 16:01:45 +0100342KernelVersion: 2.6.38
343Contact: linux-iio@vger.kernel.org
344Description:
345 Writing 1 causes output Y to enter the power down mode specified
Peter Meerwald8b417d72012-06-12 15:31:27 +0200346 by the corresponding outY_powerdown_mode. DAC output stage is
347 disconnected from the amplifier. Clearing returns to normal
348 operation. Y may be suppressed if all outputs are controlled
349 together.
Michael Hennerich14f88f12011-03-09 16:01:45 +0100350
Jonathan Cameronb3874062011-08-30 12:32:49 +0100351What: /sys/bus/iio/devices/iio:deviceX/events
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000352KernelVersion: 2.6.35
353Contact: linux-iio@vger.kernel.org
354Description:
355 Configuration of which hardware generated events are passed up
356 to user-space.
357
Jonathan Camerona37b5492011-09-02 17:14:35 +0100358What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
359What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
360What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
361What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
362What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
363What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100364What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
365What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
366What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
367What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
368What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
369What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100370What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
371What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
372What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
373What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
374What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
375What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100376What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
377What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
378What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
379What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
380What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
381What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100382KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100383Contact: linux-iio@vger.kernel.org
384Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000385 Event generated when channel passes a threshold in the specified
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100386 (_rising|_falling) direction. If the direction is not specified,
387 then either the device will report an event which ever direction
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100388 a single threshold value is passed in (e.g.
389 <type>[Y][_name]_<raw|input>_thresh_value) or
390 <type>[Y][_name]_<raw|input>_thresh_rising_value and
391 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000392 different values, but the device can only enable both thresholds
393 or neither.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100394 Note the driver will assume the last p events requested are
Peter Meerwald8b417d72012-06-12 15:31:27 +0200395 to be enabled where p is how many it supports (which may vary
396 depending on the exact set requested. So if you want to be
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100397 sure you have set what you think you have, check the contents of
398 these attributes after everything is configured. Drivers may
399 have to buffer any parameters so that they are consistent when
Peter Meerwald8b417d72012-06-12 15:31:27 +0200400 a given event type is enabled at a future point (and not those for
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100401 whatever event was previously enabled).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100402
Jonathan Camerona37b5492011-09-02 17:14:35 +0100403What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
404What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
405What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
406What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
407What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
408What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100409What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
410What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
411What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
412What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
413What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
414What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100415What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
416What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
417What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
418What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
419What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
420What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100421What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
422What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
423What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
424What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
425What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
426What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000427KernelVersion: 2.6.37
428Contact: linux-iio@vger.kernel.org
429Description:
430 Event generated when channel passes a threshold on the rate of
431 change (1st differential) in the specified (_rising|_falling)
432 direction. If the direction is not specified, then either the
433 device will report an event which ever direction a single
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100434 threshold value is passed in (e.g.
435 <type>[Y][_name]_<raw|input>_roc_value) or
436 <type>[Y][_name]_<raw|input>_roc_rising_value and
437 <type>[Y][_name]_<raw|input>_roc_falling_value may take
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000438 different values, but the device can only enable both rate of
439 change thresholds or neither.
440 Note the driver will assume the last p events requested are
441 to be enabled where p is however many it supports (which may
442 vary depending on the exact set requested. So if you want to be
443 sure you have set what you think you have, check the contents of
444 these attributes after everything is configured. Drivers may
445 have to buffer any parameters so that they are consistent when
446 a given event type is enabled a future point (and not those for
447 whatever event was previously enabled).
448
Jonathan Camerona37b5492011-09-02 17:14:35 +0100449What: /sys/.../events/in_accel_x_raw_thresh_rising_value
450What: /sys/.../events/in_accel_x_raw_thresh_falling_value
451What: /sys/.../events/in_accel_y_raw_thresh_rising_value
452What: /sys/.../events/in_accel_y_raw_thresh_falling_value
453What: /sys/.../events/in_accel_z_raw_thresh_rising_value
454What: /sys/.../events/in_accel_z_raw_thresh_falling_value
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100455What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
456What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
457What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
458What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
459What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
460What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
Jonathan Camerona37b5492011-09-02 17:14:35 +0100461What: /sys/.../events/in_magn_x_raw_thresh_rising_value
462What: /sys/.../events/in_magn_x_raw_thresh_falling_value
463What: /sys/.../events/in_magn_y_raw_thresh_rising_value
464What: /sys/.../events/in_magn_y_raw_thresh_falling_value
465What: /sys/.../events/in_magn_z_raw_thresh_rising_value
466What: /sys/.../events/in_magn_z_raw_thresh_falling_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100467What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
468What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100469What: /sys/.../events/in_voltageY_raw_thresh_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100470What: /sys/.../events/in_voltageY_raw_thresh_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100471What: /sys/.../events/in_tempY_raw_thresh_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100472What: /sys/.../events/in_tempY_raw_thresh_falling_value
Jon Brenner3c97c082012-04-24 11:56:49 -0500473What: /sys/.../events/in_illuminance0_thresh_falling_value
474what: /sys/.../events/in_illuminance0_thresh_rising_value
475what: /sys/.../events/in_proximity0_thresh_falling_value
476what: /sys/.../events/in_proximity0_thresh_rising_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100477KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100478Contact: linux-iio@vger.kernel.org
479Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100480 Specifies the value of threshold that the device is comparing
481 against for the events enabled by
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100482 <type>Y[_name]_thresh[_rising|falling]_en.
483 If separate attributes exist for the two directions, but
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000484 direction is not specified for this attribute, then a single
485 threshold value applies to both directions.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100486 The raw or input element of the name indicates whether the
487 value is in raw device units or in processed units (as _raw
488 and _input do on sysfs direct channel read attributes).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100489
Jonathan Camerona37b5492011-09-02 17:14:35 +0100490What: /sys/.../events/in_accel_x_raw_roc_rising_value
491What: /sys/.../events/in_accel_x_raw_roc_falling_value
492What: /sys/.../events/in_accel_y_raw_roc_rising_value
493What: /sys/.../events/in_accel_y_raw_roc_falling_value
494What: /sys/.../events/in_accel_z_raw_roc_rising_value
495What: /sys/.../events/in_accel_z_raw_roc_falling_value
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100496What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
497What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
498What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
499What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
500What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
501What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
Jonathan Camerona37b5492011-09-02 17:14:35 +0100502What: /sys/.../events/in_magn_x_raw_roc_rising_value
503What: /sys/.../events/in_magn_x_raw_roc_falling_value
504What: /sys/.../events/in_magn_y_raw_roc_rising_value
505What: /sys/.../events/in_magn_y_raw_roc_falling_value
506What: /sys/.../events/in_magn_z_raw_roc_rising_value
507What: /sys/.../events/in_magn_z_raw_roc_falling_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100508What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
509What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100510What: /sys/.../events/in_voltageY_raw_roc_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100511What: /sys/.../events/in_voltageY_raw_roc_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100512What: /sys/.../events/in_tempY_raw_roc_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100513What: /sys/.../events/in_tempY_raw_roc_falling_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100514KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100515Contact: linux-iio@vger.kernel.org
516Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000517 Specifies the value of rate of change threshold that the
518 device is comparing against for the events enabled by
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100519 <type>[Y][_name]_roc[_rising|falling]_en.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000520 If separate attributes exist for the two directions,
521 but direction is not specified for this attribute,
522 then a single threshold value applies to both directions.
523 The raw or input element of the name indicates whether the
524 value is in raw device units or in processed units (as _raw
525 and _input do on sysfs direct channel read attributes).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100526
Jonathan Camerona37b5492011-09-02 17:14:35 +0100527What: /sys/.../events/in_accel_x_thresh_rising_period
528What: /sys/.../events/in_accel_x_thresh_falling_period
529hat: /sys/.../events/in_accel_x_roc_rising_period
530What: /sys/.../events/in_accel_x_roc_falling_period
531What: /sys/.../events/in_accel_y_thresh_rising_period
532What: /sys/.../events/in_accel_y_thresh_falling_period
533What: /sys/.../events/in_accel_y_roc_rising_period
534What: /sys/.../events/in_accel_y_roc_falling_period
535What: /sys/.../events/in_accel_z_thresh_rising_period
536What: /sys/.../events/in_accel_z_thresh_falling_period
537What: /sys/.../events/in_accel_z_roc_rising_period
538What: /sys/.../events/in_accel_z_roc_falling_period
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100539What: /sys/.../events/in_anglvel_x_thresh_rising_period
540What: /sys/.../events/in_anglvel_x_thresh_falling_period
541What: /sys/.../events/in_anglvel_x_roc_rising_period
542What: /sys/.../events/in_anglvel_x_roc_falling_period
543What: /sys/.../events/in_anglvel_y_thresh_rising_period
544What: /sys/.../events/in_anglvel_y_thresh_falling_period
545What: /sys/.../events/in_anglvel_y_roc_rising_period
546What: /sys/.../events/in_anglvel_y_roc_falling_period
547What: /sys/.../events/in_anglvel_z_thresh_rising_period
548What: /sys/.../events/in_anglvel_z_thresh_falling_period
549What: /sys/.../events/in_anglvel_z_roc_rising_period
550What: /sys/.../events/in_anglvel_z_roc_falling_period
Jonathan Camerona37b5492011-09-02 17:14:35 +0100551What: /sys/.../events/in_magn_x_thresh_rising_period
552What: /sys/.../events/in_magn_x_thresh_falling_period
553What: /sys/.../events/in_magn_x_roc_rising_period
554What: /sys/.../events/in_magn_x_roc_falling_period
555What: /sys/.../events/in_magn_y_thresh_rising_period
556What: /sys/.../events/in_magn_y_thresh_falling_period
557What: /sys/.../events/in_magn_y_roc_rising_period
558What: /sys/.../events/in_magn_y_roc_falling_period
559What: /sys/.../events/in_magn_z_thresh_rising_period
560What: /sys/.../events/in_magn_z_thresh_falling_period
561What: /sys/.../events/in_magn_z_roc_rising_period
562What: /sys/.../events/in_magn_z_roc_falling_period
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100563What: /sys/.../events/in_voltageY_supply_thresh_rising_period
564What: /sys/.../events/in_voltageY_supply_thresh_falling_period
565What: /sys/.../events/in_voltageY_supply_roc_rising_period
566What: /sys/.../events/in_voltageY_supply_roc_falling_period
567What: /sys/.../events/in_voltageY_thresh_rising_period
568What: /sys/.../events/in_voltageY_thresh_falling_period
569What: /sys/.../events/in_voltageY_roc_rising_period
570What: /sys/.../events/in_voltageY_roc_falling_period
571What: /sys/.../events/in_tempY_thresh_rising_period
572What: /sys/.../events/in_tempY_thresh_falling_period
573What: /sys/.../events/in_tempY_roc_rising_period
574What: /sys/.../events/in_tempY_roc_falling_period
Jonathan Camerona37b5492011-09-02 17:14:35 +0100575What: /sys/.../events/in_accel_x&y&z_mag_falling_period
Jon Brenner3c97c082012-04-24 11:56:49 -0500576What: /sys/.../events/in_intensity0_thresh_period
577What: /sys/.../events/in_proximity0_thresh_period
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100578KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100579Contact: linux-iio@vger.kernel.org
580Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000581 Period of time (in seconds) for which the condition must be
582 met before an event is generated. If direction is not
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100583 specified then this period applies to both directions.
584
Jonathan Camerona37b5492011-09-02 17:14:35 +0100585What: /sys/.../iio:deviceX/events/in_accel_mag_en
586What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
587What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
588What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
589What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
590What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
591What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
592What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
593What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
594What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
595What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
596What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
597What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
598What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100599KernelVersion: 2.6.37
600Contact: linux-iio@vger.kernel.org
601Description:
Jonathan Camerona37b5492011-09-02 17:14:35 +0100602 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100603 magnitude of the channel is compared to the threshold, not its
604 signed value.
605
Jonathan Camerona37b5492011-09-02 17:14:35 +0100606What: /sys/.../events/in_accel_raw_mag_value
607What: /sys/.../events/in_accel_x_raw_mag_rising_value
608What: /sys/.../events/in_accel_y_raw_mag_rising_value
609What: /sys/.../events/in_accel_z_raw_mag_rising_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100610KernelVersion: 2.6.37
611Contact: linux-iio@vger.kernel.org
612Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000613 The value to which the magnitude of the channel is compared. If
614 number or direction is not specified, applies to all channels of
615 this type.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100616
Jonathan Cameronb3874062011-08-30 12:32:49 +0100617What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100618KernelVersion: 2.6.35
619Contact: linux-iio@vger.kernel.org
620Description:
621 The name of the trigger source being used, as per string given
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000622 in /sys/class/iio/triggerY/name.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100623
Jonathan Cameronb3874062011-08-30 12:32:49 +0100624What: /sys/bus/iio/devices/iio:deviceX/buffer/length
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100625KernelVersion: 2.6.35
626Contact: linux-iio@vger.kernel.org
627Description:
628 Number of scans contained by the buffer.
629
Jonathan Cameronb3874062011-08-30 12:32:49 +0100630What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200631KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100632Contact: linux-iio@vger.kernel.org
633Description:
634 Bytes per scan. Due to alignment fun, the scan may be larger
635 than implied directly by the scan_element parameters.
636
Jonathan Cameronb3874062011-08-30 12:32:49 +0100637What: /sys/bus/iio/devices/iio:deviceX/buffer/enable
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100638KernelVersion: 2.6.35
639Contact: linux-iio@vger.kernel.org
640Description:
641 Actually start the buffer capture up. Will start trigger
642 if first device and appropriate.
643
Jonathan Cameronb3874062011-08-30 12:32:49 +0100644What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200645KernelVersion: 2.6.37
646Contact: linux-iio@vger.kernel.org
647Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100648 Directory containing interfaces for elements that will be
649 captured for a single triggered sample set in the buffer.
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200650
Jonathan Camerona37b5492011-09-02 17:14:35 +0100651What: /sys/.../buffer/scan_elements/in_accel_x_en
652What: /sys/.../buffer/scan_elements/in_accel_y_en
653What: /sys/.../buffer/scan_elements/in_accel_z_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100654What: /sys/.../buffer/scan_elements/in_anglvel_x_en
655What: /sys/.../buffer/scan_elements/in_anglvel_y_en
656What: /sys/.../buffer/scan_elements/in_anglvel_z_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100657What: /sys/.../buffer/scan_elements/in_magn_x_en
658What: /sys/.../buffer/scan_elements/in_magn_y_en
659What: /sys/.../buffer/scan_elements/in_magn_z_en
660What: /sys/.../buffer/scan_elements/in_timestamp_en
661What: /sys/.../buffer/scan_elements/in_voltageY_supply_en
662What: /sys/.../buffer/scan_elements/in_voltageY_en
663What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en
664What: /sys/.../buffer/scan_elements/in_incli_x_en
665What: /sys/.../buffer/scan_elements/in_incli_y_en
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200666KernelVersion: 2.6.37
667Contact: linux-iio@vger.kernel.org
668Description:
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100669 Scan element control for triggered data capture.
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200670
Jonathan Camerona37b5492011-09-02 17:14:35 +0100671What: /sys/.../buffer/scan_elements/in_accel_type
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100672What: /sys/.../buffer/scan_elements/in_anglvel_type
Jonathan Camerona37b5492011-09-02 17:14:35 +0100673What: /sys/.../buffer/scan_elements/in_magn_type
674What: /sys/.../buffer/scan_elements/in_incli_type
675What: /sys/.../buffer/scan_elements/in_voltageY_type
Peter Meerwald8b417d72012-06-12 15:31:27 +0200676What: /sys/.../buffer/scan_elements/in_voltage_type
Jonathan Camerona37b5492011-09-02 17:14:35 +0100677What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
678What: /sys/.../buffer/scan_elements/in_timestamp_type
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200679KernelVersion: 2.6.37
680Contact: linux-iio@vger.kernel.org
681Description:
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100682 Description of the scan element data storage within the buffer
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000683 and hence the form in which it is read from user-space.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100684 Form is [be|le]:[s|u]bits/storagebits[>>shift].
685 be or le specifies big or little endian. s or u specifies if
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000686 signed (2's complement) or unsigned. bits is the number of bits
687 of data and storagebits is the space (after padding) that it
688 occupies in the buffer. shift if specified, is the shift that
689 needs to be applied prior to masking out unused bits. Some
690 devices put their data in the middle of the transferred elements
691 with additional information on both sides. Note that some
692 devices will have additional information in the unused bits
693 so to get a clean value, the bits value must be used to mask
694 the buffer output value appropriately. The storagebits value
695 also specifies the data alignment. So s48/64>>2 will be a
696 signed 48 bit integer stored in a 64 bit location aligned to
Peter Meerwald8b417d72012-06-12 15:31:27 +0200697 a 64 bit boundary. To obtain the clean value, shift right 2
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000698 and apply a mask to zero the top 16 bits of the result.
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100699 For other storage combinations this attribute will be extended
700 appropriately.
701
Jonathan Camerona37b5492011-09-02 17:14:35 +0100702What: /sys/.../buffer/scan_elements/in_accel_type_available
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000703KernelVersion: 2.6.37
704Contact: linux-iio@vger.kernel.org
705Description:
706 If the type parameter can take one of a small set of values,
707 this attribute lists them.
708
Jonathan Camerona37b5492011-09-02 17:14:35 +0100709What: /sys/.../buffer/scan_elements/in_voltageY_index
710What: /sys/.../buffer/scan_elements/in_voltageY_supply_index
711What: /sys/.../buffer/scan_elements/in_accel_x_index
712What: /sys/.../buffer/scan_elements/in_accel_y_index
713What: /sys/.../buffer/scan_elements/in_accel_z_index
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100714What: /sys/.../buffer/scan_elements/in_anglvel_x_index
715What: /sys/.../buffer/scan_elements/in_anglvel_y_index
716What: /sys/.../buffer/scan_elements/in_anglvel_z_index
Jonathan Camerona37b5492011-09-02 17:14:35 +0100717What: /sys/.../buffer/scan_elements/in_magn_x_index
718What: /sys/.../buffer/scan_elements/in_magn_y_index
719What: /sys/.../buffer/scan_elements/in_magn_z_index
720What: /sys/.../buffer/scan_elements/in_incli_x_index
721What: /sys/.../buffer/scan_elements/in_incli_y_index
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100722What: /sys/.../buffer/scan_elements/in_timestamp_index
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100723KernelVersion: 2.6.37
724Contact: linux-iio@vger.kernel.org
725Description:
726 A single positive integer specifying the position of this
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000727 scan element in the buffer. Note these are not dependent on
728 what is enabled and may not be contiguous. Thus for user-space
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100729 to establish the full layout these must be used in conjunction
730 with all _en attributes to establish which channels are present,
731 and the relevant _type attributes to establish the data storage
732 format.
Michael Hennerichd4894632011-04-06 11:42:48 +0200733
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100734What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
Michael Hennerichd4894632011-04-06 11:42:48 +0200735KernelVersion: 2.6.38
Jonathan Camerona37b5492011-09-02 17:14:35 +0100736Contact: linux-iio@vger.kernel.org
Michael Hennerichd4894632011-04-06 11:42:48 +0200737Description:
738 This attribute is used to read the amount of quadrature error
739 present in the device at a given time.