blob: cfedf63cce151d2bdb9237ed58726a136f4cc065 [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
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
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:
77 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:
121 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
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000151 assigned) Data converted by application of offset then scale to
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100152 radians per second. Has all the equivalent parameters as
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100153 per voltageY. Units after application of scale and offset are
154 radians per second.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100155
Jonathan Camerona37b5492011-09-02 17:14:35 +0100156What: /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
Jonathan Camerone5107fb2010-05-07 15:38:57 +0100159KernelVersion: 2.6.35
160Contact: linux-iio@vger.kernel.org
161Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000162 Inclination raw reading about axis x, y or z (may be
163 arbitrarily assigned). Data converted by application of offset
Jonathan Camerone5107fb2010-05-07 15:38:57 +0100164 and scale to Degrees.
165
Jonathan Camerona37b5492011-09-02 17:14:35 +0100166What: /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
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100169KernelVersion: 2.6.35
170Contact: linux-iio@vger.kernel.org
171Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100172 Magnetic field along axis x, y or z (may be arbitrarily
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100173 assigned). Data converted by application of offset
174 then scale to Gauss.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100175
Jonathan Camerona37b5492011-09-02 17:14:35 +0100176What: /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
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000179KernelVersion: 2.6.36
180Contact: linux-iio@vger.kernel.org
181Description:
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100182 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.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000185
Jonathan Camerona37b5492011-09-02 17:14:35 +0100186What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000187KernelVersion: 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
Jonathan Camerona37b5492011-09-02 17:14:35 +0100193What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100194What: /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
Jonathan Camerona37b5492011-09-02 17:14:35 +0100200What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100201KernelVersion: 2.6.35
202Contact: linux-iio@vger.kernel.org
203Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000204 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.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100207 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>.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000210 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.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100215 Calibbias is applied internally, offset is applied in userspace
216 to the _raw output.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100217
Jonathan Camerona37b5492011-09-02 17:14:35 +0100218What: /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
Michael Hennerichd802bf62012-05-21 14:30:31 +0200222What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
Jonathan Camerona37b5492011-09-02 17:14:35 +0100223What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
224What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100225What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
Jonathan Camerona37b5492011-09-02 17:14:35 +0100226What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
227What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
228What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
229What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100230KernelVersion: 2.6.35
231Contact: linux-iio@vger.kernel.org
232Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000233 If known for a device, scale to be applied to <type>Y[_name]_raw
234 post addition of <type>[Y][_name]_offset in order to obtain the
235 measured value in <type> units as specified in
Jonathan Cameron68284a12012-04-25 15:54:57 +0100236 <type>[Y][_name]_raw documentation. If shared across all in
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100237 channels then Y and <x|y|z> are not present and the value is
238 called <type>[Y][_name]_scale. The peak modifier means this
239 value is applied to <type>Y[_name]_peak_raw values.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100240
Jonathan Camerona37b5492011-09-02 17:14:35 +0100241What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias
242What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias
243What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100244What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias
245What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias
246What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias
Jon Brenner3c97c082012-04-24 11:56:49 -0500247What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias
248What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000249KernelVersion: 2.6.35
250Contact: linux-iio@vger.kernel.org
251Description:
252 Hardware applied calibration offset. (assumed to fix production
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100253 inaccuracies).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100254
Jonathan Camerona37b5492011-09-02 17:14:35 +0100255What /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
256What /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
257What /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
258What /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
259What /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
260What /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100261What /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
262What /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
263What /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
Jon Brenner3c97c082012-04-24 11:56:49 -0500264what /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
265what /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000266KernelVersion: 2.6.35
267Contact: linux-iio@vger.kernel.org
268Description:
269 Hardware applied calibration scale factor. (assumed to fix
270 production inaccuracies). If shared across all channels,
271 <type>_calibscale is used.
272
Jonathan Camerona37b5492011-09-02 17:14:35 +0100273What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100274What: /sys/.../iio:deviceX/in_voltageX_scale_available
275What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
276What: /sys/.../iio:deviceX/out_voltageX_scale_available
Michael Hennerichd802bf62012-05-21 14:30:31 +0200277What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
Jonathan Cameron0baf29d2011-09-21 11:15:52 +0100278What: /sys/.../iio:deviceX/in_capacitance_scale_available
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000279KernelVersion: 2.635
280Contact: linux-iio@vger.kernel.org
281Description:
282 If a discrete set of scale values are available, they
283 are listed in this attribute.
284
Michael Hennerichb65d6212012-05-11 11:36:53 +0200285What /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
286KernelVersion: 2.6.35
287Contact: linux-iio@vger.kernel.org
288Description:
289 Hardware applied gain factor. If shared across all channels,
290 <type>_hardwaregain is used.
291
Jonathan Cameron0c22db4392011-11-27 11:39:14 +0000292What: /sys/.../in_accel_filter_low_pass_3db_frequency
293What: /sys/.../in_magn_filter_low_pass_3db_frequency
294What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
295KernelVersion: 3.2
296Contact: linux-iio@vger.kernel.org
297Description:
298 If a known or controllable low pass filter is applied
299 to the underlying data channel, then this parameter
300 gives the 3dB frequency of the filter in Hz.
301
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100302What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
Michael Hennerichd802bf62012-05-21 14:30:31 +0200303What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
Roland Stigge98069c32011-01-13 17:43:29 +0100304KernelVersion: 2.6.37
305Contact: linux-iio@vger.kernel.org
306Description:
307 Raw (unscaled, no bias etc.) output voltage for
308 channel Y. The number must always be specified and
309 unique if the output corresponds to a single channel.
Michael Hennerichd802bf62012-05-21 14:30:31 +0200310 While DAC like devices typically use out_voltage,
311 a continuous frequency generating device, such as
312 a DDS or PLL should use out_altvoltage.
Roland Stigge98069c32011-01-13 17:43:29 +0100313
Jonathan Camerona37b5492011-09-02 17:14:35 +0100314What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
Michael Hennerichd802bf62012-05-21 14:30:31 +0200315What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw
Roland Stigge98069c32011-01-13 17:43:29 +0100316KernelVersion: 2.6.37
317Contact: linux-iio@vger.kernel.org
318Description:
319 Raw (unscaled, no bias etc.) output voltage for an aggregate of
320 channel Y, channel Z, etc. This interface is available in cases
321 where a single output sets the value for multiple channels
322 simultaneously.
323
Jonathan Camerona37b5492011-09-02 17:14:35 +0100324What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
325What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
Michael Hennerichd802bf62012-05-21 14:30:31 +0200326What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode
327What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode
Michael Hennerich14f88f12011-03-09 16:01:45 +0100328KernelVersion: 2.6.38
329Contact: linux-iio@vger.kernel.org
330Description:
331 Specifies the output powerdown mode.
332 DAC output stage is disconnected from the amplifier and
333 1kohm_to_gnd: connected to ground via an 1kOhm resistor
334 100kohm_to_gnd: connected to ground via an 100kOhm resistor
335 three_state: left floating
336 For a list of available output power down options read
337 outX_powerdown_mode_available. If Y is not present the
338 mode is shared across all outputs.
339
Jonathan Camerona37b5492011-09-02 17:14:35 +0100340What: /sys/.../iio:deviceX/out_votlageY_powerdown_mode_available
341What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
Michael Hennerichd802bf62012-05-21 14:30:31 +0200342What: /sys/.../iio:deviceX/out_altvotlageY_powerdown_mode_available
343What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available
Michael Hennerich14f88f12011-03-09 16:01:45 +0100344KernelVersion: 2.6.38
345Contact: linux-iio@vger.kernel.org
346Description:
347 Lists all available output power down modes.
348 If Y is not present the mode is shared across all outputs.
349
Jonathan Camerona37b5492011-09-02 17:14:35 +0100350What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
351What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
Michael Hennerichd802bf62012-05-21 14:30:31 +0200352What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
353What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown
Michael Hennerich14f88f12011-03-09 16:01:45 +0100354KernelVersion: 2.6.38
355Contact: linux-iio@vger.kernel.org
356Description:
357 Writing 1 causes output Y to enter the power down mode specified
358 by the corresponding outY_powerdown_mode. Clearing returns to
359 normal operation. Y may be suppressed if all outputs are
360 controlled together.
361
Michael Hennerichd802bf62012-05-21 14:30:31 +0200362What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
363KernelVersion: 3.4.0
364Contact: linux-iio@vger.kernel.org
365Description:
366 Output frequency for channel Y in Hz. The number must always be
367 specified and unique if the output corresponds to a single
368 channel.
369
370What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase
371KernelVersion: 3.4.0
372Contact: linux-iio@vger.kernel.org
373Description:
374 Phase in radians of one frequency/clock output Y
375 (out_altvoltageY) relative to another frequency/clock output
376 (out_altvoltageZ) of the device X. The number must always be
377 specified and unique if the output corresponds to a single
378 channel.
379
Jonathan Cameronb3874062011-08-30 12:32:49 +0100380What: /sys/bus/iio/devices/iio:deviceX/events
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000381KernelVersion: 2.6.35
382Contact: linux-iio@vger.kernel.org
383Description:
384 Configuration of which hardware generated events are passed up
385 to user-space.
386
Jonathan Camerona37b5492011-09-02 17:14:35 +0100387What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
388What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
389What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
390What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
391What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
392What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100393What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
394What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
395What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
396What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
397What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
398What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100399What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
400What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
401What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
402What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
403What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
404What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100405What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
406What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
407What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
408What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
409What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
410What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100411KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100412Contact: linux-iio@vger.kernel.org
413Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000414 Event generated when channel passes a threshold in the specified
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100415 (_rising|_falling) direction. If the direction is not specified,
416 then either the device will report an event which ever direction
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100417 a single threshold value is passed in (e.g.
418 <type>[Y][_name]_<raw|input>_thresh_value) or
419 <type>[Y][_name]_<raw|input>_thresh_rising_value and
420 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000421 different values, but the device can only enable both thresholds
422 or neither.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100423 Note the driver will assume the last p events requested are
424 to be enabled where p is however many it supports (which may
425 vary depending on the exact set requested. So if you want to be
426 sure you have set what you think you have, check the contents of
427 these attributes after everything is configured. Drivers may
428 have to buffer any parameters so that they are consistent when
429 a given event type is enabled a future point (and not those for
430 whatever event was previously enabled).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100431
Jonathan Camerona37b5492011-09-02 17:14:35 +0100432What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
433What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
434What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
435What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
436What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
437What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100438What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
439What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
440What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
441What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
442What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
443What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100444What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
445What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
446What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
447What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
448What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
449What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100450What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
451What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
452What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
453What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
454What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
455What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000456KernelVersion: 2.6.37
457Contact: linux-iio@vger.kernel.org
458Description:
459 Event generated when channel passes a threshold on the rate of
460 change (1st differential) in the specified (_rising|_falling)
461 direction. If the direction is not specified, then either the
462 device will report an event which ever direction a single
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100463 threshold value is passed in (e.g.
464 <type>[Y][_name]_<raw|input>_roc_value) or
465 <type>[Y][_name]_<raw|input>_roc_rising_value and
466 <type>[Y][_name]_<raw|input>_roc_falling_value may take
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000467 different values, but the device can only enable both rate of
468 change thresholds or neither.
469 Note the driver will assume the last p events requested are
470 to be enabled where p is however many it supports (which may
471 vary depending on the exact set requested. So if you want to be
472 sure you have set what you think you have, check the contents of
473 these attributes after everything is configured. Drivers may
474 have to buffer any parameters so that they are consistent when
475 a given event type is enabled a future point (and not those for
476 whatever event was previously enabled).
477
Jonathan Camerona37b5492011-09-02 17:14:35 +0100478What: /sys/.../events/in_accel_x_raw_thresh_rising_value
479What: /sys/.../events/in_accel_x_raw_thresh_falling_value
480What: /sys/.../events/in_accel_y_raw_thresh_rising_value
481What: /sys/.../events/in_accel_y_raw_thresh_falling_value
482What: /sys/.../events/in_accel_z_raw_thresh_rising_value
483What: /sys/.../events/in_accel_z_raw_thresh_falling_value
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100484What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
485What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
486What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
487What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
488What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
489What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
Jonathan Camerona37b5492011-09-02 17:14:35 +0100490What: /sys/.../events/in_magn_x_raw_thresh_rising_value
491What: /sys/.../events/in_magn_x_raw_thresh_falling_value
492What: /sys/.../events/in_magn_y_raw_thresh_rising_value
493What: /sys/.../events/in_magn_y_raw_thresh_falling_value
494What: /sys/.../events/in_magn_z_raw_thresh_rising_value
495What: /sys/.../events/in_magn_z_raw_thresh_falling_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100496What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
497What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100498What: /sys/.../events/in_voltageY_raw_thresh_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100499What: /sys/.../events/in_voltageY_raw_thresh_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100500What: /sys/.../events/in_tempY_raw_thresh_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100501What: /sys/.../events/in_tempY_raw_thresh_falling_value
Jon Brenner3c97c082012-04-24 11:56:49 -0500502What: /sys/.../events/in_illuminance0_thresh_falling_value
503what: /sys/.../events/in_illuminance0_thresh_rising_value
504what: /sys/.../events/in_proximity0_thresh_falling_value
505what: /sys/.../events/in_proximity0_thresh_rising_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100506KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100507Contact: linux-iio@vger.kernel.org
508Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100509 Specifies the value of threshold that the device is comparing
510 against for the events enabled by
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100511 <type>Y[_name]_thresh[_rising|falling]_en.
512 If separate attributes exist for the two directions, but
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000513 direction is not specified for this attribute, then a single
514 threshold value applies to both directions.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100515 The raw or input element of the name indicates whether the
516 value is in raw device units or in processed units (as _raw
517 and _input do on sysfs direct channel read attributes).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100518
Jonathan Camerona37b5492011-09-02 17:14:35 +0100519What: /sys/.../events/in_accel_x_raw_roc_rising_value
520What: /sys/.../events/in_accel_x_raw_roc_falling_value
521What: /sys/.../events/in_accel_y_raw_roc_rising_value
522What: /sys/.../events/in_accel_y_raw_roc_falling_value
523What: /sys/.../events/in_accel_z_raw_roc_rising_value
524What: /sys/.../events/in_accel_z_raw_roc_falling_value
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100525What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
526What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
527What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
528What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
529What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
530What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
Jonathan Camerona37b5492011-09-02 17:14:35 +0100531What: /sys/.../events/in_magn_x_raw_roc_rising_value
532What: /sys/.../events/in_magn_x_raw_roc_falling_value
533What: /sys/.../events/in_magn_y_raw_roc_rising_value
534What: /sys/.../events/in_magn_y_raw_roc_falling_value
535What: /sys/.../events/in_magn_z_raw_roc_rising_value
536What: /sys/.../events/in_magn_z_raw_roc_falling_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100537What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
538What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100539What: /sys/.../events/in_voltageY_raw_roc_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100540What: /sys/.../events/in_voltageY_raw_roc_falling_value
Jonathan Camerona7322fc2012-04-13 10:24:19 +0100541What: /sys/.../events/in_tempY_raw_roc_rising_value
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100542What: /sys/.../events/in_tempY_raw_roc_falling_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100543KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100544Contact: linux-iio@vger.kernel.org
545Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000546 Specifies the value of rate of change threshold that the
547 device is comparing against for the events enabled by
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100548 <type>[Y][_name]_roc[_rising|falling]_en.
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000549 If separate attributes exist for the two directions,
550 but direction is not specified for this attribute,
551 then a single threshold value applies to both directions.
552 The raw or input element of the name indicates whether the
553 value is in raw device units or in processed units (as _raw
554 and _input do on sysfs direct channel read attributes).
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100555
Jonathan Camerona37b5492011-09-02 17:14:35 +0100556What: /sys/.../events/in_accel_x_thresh_rising_period
557What: /sys/.../events/in_accel_x_thresh_falling_period
558hat: /sys/.../events/in_accel_x_roc_rising_period
559What: /sys/.../events/in_accel_x_roc_falling_period
560What: /sys/.../events/in_accel_y_thresh_rising_period
561What: /sys/.../events/in_accel_y_thresh_falling_period
562What: /sys/.../events/in_accel_y_roc_rising_period
563What: /sys/.../events/in_accel_y_roc_falling_period
564What: /sys/.../events/in_accel_z_thresh_rising_period
565What: /sys/.../events/in_accel_z_thresh_falling_period
566What: /sys/.../events/in_accel_z_roc_rising_period
567What: /sys/.../events/in_accel_z_roc_falling_period
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100568What: /sys/.../events/in_anglvel_x_thresh_rising_period
569What: /sys/.../events/in_anglvel_x_thresh_falling_period
570What: /sys/.../events/in_anglvel_x_roc_rising_period
571What: /sys/.../events/in_anglvel_x_roc_falling_period
572What: /sys/.../events/in_anglvel_y_thresh_rising_period
573What: /sys/.../events/in_anglvel_y_thresh_falling_period
574What: /sys/.../events/in_anglvel_y_roc_rising_period
575What: /sys/.../events/in_anglvel_y_roc_falling_period
576What: /sys/.../events/in_anglvel_z_thresh_rising_period
577What: /sys/.../events/in_anglvel_z_thresh_falling_period
578What: /sys/.../events/in_anglvel_z_roc_rising_period
579What: /sys/.../events/in_anglvel_z_roc_falling_period
Jonathan Camerona37b5492011-09-02 17:14:35 +0100580What: /sys/.../events/in_magn_x_thresh_rising_period
581What: /sys/.../events/in_magn_x_thresh_falling_period
582What: /sys/.../events/in_magn_x_roc_rising_period
583What: /sys/.../events/in_magn_x_roc_falling_period
584What: /sys/.../events/in_magn_y_thresh_rising_period
585What: /sys/.../events/in_magn_y_thresh_falling_period
586What: /sys/.../events/in_magn_y_roc_rising_period
587What: /sys/.../events/in_magn_y_roc_falling_period
588What: /sys/.../events/in_magn_z_thresh_rising_period
589What: /sys/.../events/in_magn_z_thresh_falling_period
590What: /sys/.../events/in_magn_z_roc_rising_period
591What: /sys/.../events/in_magn_z_roc_falling_period
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100592What: /sys/.../events/in_voltageY_supply_thresh_rising_period
593What: /sys/.../events/in_voltageY_supply_thresh_falling_period
594What: /sys/.../events/in_voltageY_supply_roc_rising_period
595What: /sys/.../events/in_voltageY_supply_roc_falling_period
596What: /sys/.../events/in_voltageY_thresh_rising_period
597What: /sys/.../events/in_voltageY_thresh_falling_period
598What: /sys/.../events/in_voltageY_roc_rising_period
599What: /sys/.../events/in_voltageY_roc_falling_period
600What: /sys/.../events/in_tempY_thresh_rising_period
601What: /sys/.../events/in_tempY_thresh_falling_period
602What: /sys/.../events/in_tempY_roc_rising_period
603What: /sys/.../events/in_tempY_roc_falling_period
Jonathan Camerona37b5492011-09-02 17:14:35 +0100604What: /sys/.../events/in_accel_x&y&z_mag_falling_period
Jon Brenner3c97c082012-04-24 11:56:49 -0500605What: /sys/.../events/in_intensity0_thresh_period
606What: /sys/.../events/in_proximity0_thresh_period
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100607KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100608Contact: linux-iio@vger.kernel.org
609Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000610 Period of time (in seconds) for which the condition must be
611 met before an event is generated. If direction is not
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100612 specified then this period applies to both directions.
613
Jonathan Camerona37b5492011-09-02 17:14:35 +0100614What: /sys/.../iio:deviceX/events/in_accel_mag_en
615What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
616What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
617What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
618What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
619What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
620What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
621What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
622What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
623What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
624What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
625What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
626What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
627What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100628KernelVersion: 2.6.37
629Contact: linux-iio@vger.kernel.org
630Description:
Jonathan Camerona37b5492011-09-02 17:14:35 +0100631 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100632 magnitude of the channel is compared to the threshold, not its
633 signed value.
634
Jonathan Camerona37b5492011-09-02 17:14:35 +0100635What: /sys/.../events/in_accel_raw_mag_value
636What: /sys/.../events/in_accel_x_raw_mag_rising_value
637What: /sys/.../events/in_accel_y_raw_mag_rising_value
638What: /sys/.../events/in_accel_z_raw_mag_rising_value
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100639KernelVersion: 2.6.37
640Contact: linux-iio@vger.kernel.org
641Description:
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000642 The value to which the magnitude of the channel is compared. If
643 number or direction is not specified, applies to all channels of
644 this type.
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100645
Jonathan Cameronb3874062011-08-30 12:32:49 +0100646What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100647KernelVersion: 2.6.35
648Contact: linux-iio@vger.kernel.org
649Description:
650 The name of the trigger source being used, as per string given
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000651 in /sys/class/iio/triggerY/name.
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100652
Jonathan Cameronb3874062011-08-30 12:32:49 +0100653What: /sys/bus/iio/devices/iio:deviceX/buffer/length
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100654KernelVersion: 2.6.35
655Contact: linux-iio@vger.kernel.org
656Description:
657 Number of scans contained by the buffer.
658
Jonathan Cameronb3874062011-08-30 12:32:49 +0100659What: /sys/bus/iio/devices/iio:deviceX/buffer/bytes_per_datum
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200660KernelVersion: 2.6.37
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100661Contact: linux-iio@vger.kernel.org
662Description:
663 Bytes per scan. Due to alignment fun, the scan may be larger
664 than implied directly by the scan_element parameters.
665
Jonathan Cameronb3874062011-08-30 12:32:49 +0100666What: /sys/bus/iio/devices/iio:deviceX/buffer/enable
Jonathan Camerone34d2c52010-05-04 14:43:05 +0100667KernelVersion: 2.6.35
668Contact: linux-iio@vger.kernel.org
669Description:
670 Actually start the buffer capture up. Will start trigger
671 if first device and appropriate.
672
Jonathan Cameronb3874062011-08-30 12:32:49 +0100673What: /sys/bus/iio/devices/iio:deviceX/buffer/scan_elements
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200674KernelVersion: 2.6.37
675Contact: linux-iio@vger.kernel.org
676Description:
Jonathan Cameron2f3cc662010-10-08 12:14:12 +0100677 Directory containing interfaces for elements that will be
678 captured for a single triggered sample set in the buffer.
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200679
Jonathan Camerona37b5492011-09-02 17:14:35 +0100680What: /sys/.../buffer/scan_elements/in_accel_x_en
681What: /sys/.../buffer/scan_elements/in_accel_y_en
682What: /sys/.../buffer/scan_elements/in_accel_z_en
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100683What: /sys/.../buffer/scan_elements/in_anglvel_x_en
684What: /sys/.../buffer/scan_elements/in_anglvel_y_en
685What: /sys/.../buffer/scan_elements/in_anglvel_z_en
Jonathan Camerona37b5492011-09-02 17:14:35 +0100686What: /sys/.../buffer/scan_elements/in_magn_x_en
687What: /sys/.../buffer/scan_elements/in_magn_y_en
688What: /sys/.../buffer/scan_elements/in_magn_z_en
689What: /sys/.../buffer/scan_elements/in_timestamp_en
690What: /sys/.../buffer/scan_elements/in_voltageY_supply_en
691What: /sys/.../buffer/scan_elements/in_voltageY_en
692What: /sys/.../buffer/scan_elements/in_voltageY-voltageZ_en
693What: /sys/.../buffer/scan_elements/in_incli_x_en
694What: /sys/.../buffer/scan_elements/in_incli_y_en
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200695KernelVersion: 2.6.37
696Contact: linux-iio@vger.kernel.org
697Description:
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100698 Scan element control for triggered data capture.
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200699
Jonathan Camerona37b5492011-09-02 17:14:35 +0100700What: /sys/.../buffer/scan_elements/in_accel_type
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100701What: /sys/.../buffer/scan_elements/in_anglvel_type
Jonathan Camerona37b5492011-09-02 17:14:35 +0100702What: /sys/.../buffer/scan_elements/in_magn_type
703What: /sys/.../buffer/scan_elements/in_incli_type
704What: /sys/.../buffer/scan_elements/in_voltageY_type
705What: /sys/.../buffer/scan_elements/in_voltage-in_type
706What: /sys/.../buffer/scan_elements/in_voltageY_supply_type
707What: /sys/.../buffer/scan_elements/in_timestamp_type
Manuel Stahl5770b8f2010-08-31 11:32:53 +0200708KernelVersion: 2.6.37
709Contact: linux-iio@vger.kernel.org
710Description:
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100711 Description of the scan element data storage within the buffer
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000712 and hence the form in which it is read from user-space.
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100713 Form is [be|le]:[s|u]bits/storagebits[>>shift].
714 be or le specifies big or little endian. s or u specifies if
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000715 signed (2's complement) or unsigned. bits is the number of bits
716 of data and storagebits is the space (after padding) that it
717 occupies in the buffer. shift if specified, is the shift that
718 needs to be applied prior to masking out unused bits. Some
719 devices put their data in the middle of the transferred elements
720 with additional information on both sides. Note that some
721 devices will have additional information in the unused bits
722 so to get a clean value, the bits value must be used to mask
723 the buffer output value appropriately. The storagebits value
724 also specifies the data alignment. So s48/64>>2 will be a
725 signed 48 bit integer stored in a 64 bit location aligned to
726 a a64 bit boundary. To obtain the clean value, shift right 2
727 and apply a mask to zero the top 16 bits of the result.
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100728 For other storage combinations this attribute will be extended
729 appropriately.
730
Jonathan Camerona37b5492011-09-02 17:14:35 +0100731What: /sys/.../buffer/scan_elements/in_accel_type_available
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000732KernelVersion: 2.6.37
733Contact: linux-iio@vger.kernel.org
734Description:
735 If the type parameter can take one of a small set of values,
736 this attribute lists them.
737
Jonathan Camerona37b5492011-09-02 17:14:35 +0100738What: /sys/.../buffer/scan_elements/in_voltageY_index
739What: /sys/.../buffer/scan_elements/in_voltageY_supply_index
740What: /sys/.../buffer/scan_elements/in_accel_x_index
741What: /sys/.../buffer/scan_elements/in_accel_y_index
742What: /sys/.../buffer/scan_elements/in_accel_z_index
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100743What: /sys/.../buffer/scan_elements/in_anglvel_x_index
744What: /sys/.../buffer/scan_elements/in_anglvel_y_index
745What: /sys/.../buffer/scan_elements/in_anglvel_z_index
Jonathan Camerona37b5492011-09-02 17:14:35 +0100746What: /sys/.../buffer/scan_elements/in_magn_x_index
747What: /sys/.../buffer/scan_elements/in_magn_y_index
748What: /sys/.../buffer/scan_elements/in_magn_z_index
749What: /sys/.../buffer/scan_elements/in_incli_x_index
750What: /sys/.../buffer/scan_elements/in_incli_y_index
Jonathan Cameron15739cd2011-09-21 11:15:51 +0100751What: /sys/.../buffer/scan_elements/in_timestamp_index
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100752KernelVersion: 2.6.37
753Contact: linux-iio@vger.kernel.org
754Description:
755 A single positive integer specifying the position of this
Jonathan Cameronf386caa2010-11-22 23:31:16 +0000756 scan element in the buffer. Note these are not dependent on
757 what is enabled and may not be contiguous. Thus for user-space
Jonathan Cameron10ba8ea2010-09-21 14:41:08 +0100758 to establish the full layout these must be used in conjunction
759 with all _en attributes to establish which channels are present,
760 and the relevant _type attributes to establish the data storage
761 format.
Michael Hennerichd4894632011-04-06 11:42:48 +0200762
Jonathan Camerond4c926f2011-10-05 15:28:00 +0100763What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
Michael Hennerichd4894632011-04-06 11:42:48 +0200764KernelVersion: 2.6.38
Jonathan Camerona37b5492011-09-02 17:14:35 +0100765Contact: linux-iio@vger.kernel.org
Michael Hennerichd4894632011-04-06 11:42:48 +0200766Description:
767 This attribute is used to read the amount of quadrature error
768 present in the device at a given time.