1 What: /sys/bus/iio/devices/iio:deviceX
3 Contact: linux-iio@vger.kernel.org
5 Hardware chip or device accessed by one communication port.
6 Corresponds to a grouping of sensor channels. X is the IIO
9 What: /sys/bus/iio/devices/triggerX
11 Contact: linux-iio@vger.kernel.org
13 An event driven driver of data capture to an in kernel buffer.
14 May be provided by a device driver that also has an IIO device
15 based on hardware generated events (e.g. data ready) or
16 provided by a separate driver for other hardware (e.g.
17 periodic timer, GPIO or high resolution timer).
19 Contains trigger type specific elements. These do not
20 generalize well and hence are not documented in this file.
21 X is the IIO index of the trigger.
23 What: /sys/bus/iio/devices/iio:deviceX/buffer
25 Contact: linux-iio@vger.kernel.org
27 Directory of attributes relating to the buffer for the device.
29 What: /sys/bus/iio/devices/iio:deviceX/name
31 Contact: linux-iio@vger.kernel.org
33 Description of the physical chip / device for device X.
34 Typically a part number.
36 What: /sys/bus/iio/devices/iio:deviceX/label
38 Contact: linux-iio@vger.kernel.org
40 Optional symbolic label for a device.
41 This is useful for userspace to be able to better identify an
44 The contents of the label are free-form, but there are some
47 For proximity sensors which give the proximity (of a person) to
48 a certain wlan or wwan antenna the following standardized labels
53 * "proximity-wifi-lte"
54 * "proximity-wifi-left"
55 * "proximity-wifi-right"
57 These are used to indicate to userspace that these proximity
58 sensors may be used to tune transmit power to ensure that
59 Specific Absorption Rate (SAR) limits are honored.
60 The "-left" and "-right" labels are for devices with multiple
63 In some laptops/tablets the standardized proximity sensor labels
64 instead indicate proximity to a specific part of the device:
66 * "proximity-palmrest" indicates proximity to the keyboard's palmrest
67 * "proximity-palmrest-left" indicates proximity to the left part of the palmrest
68 * "proximity-palmrest-right" indicates proximity to the right part of the palmrest
69 * "proximity-lap" indicates the device is being used on someone's lap
71 Note "proximity-lap" is special in that its value may be
72 calculated by firmware from other sensor readings, rather then
73 being a raw sensor reading.
75 For accelerometers used in 2-in-1s with 360° (yoga-style) hinges,
76 which have an accelerometer in both their base and their display,
77 the following standardized labels are used:
82 What: /sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
84 Contact: linux-iio@vger.kernel.org
86 String identifying current posix clock used to timestamp
87 buffered samples and events for device X.
89 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency
90 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency
91 What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency
92 What: /sys/bus/iio/devices/triggerX/sampling_frequency
94 Contact: linux-iio@vger.kernel.org
96 Some devices have internal clocks. This parameter sets the
97 resulting sampling frequency. In many devices this
98 parameter has an effect on input filters etc. rather than
99 simply controlling when the input is sampled. As this
100 affects data ready triggers, hardware buffers and the sysfs
101 direct access interfaces, it may be found in any of the
102 relevant directories. If it affects all of the above
103 then it is to be found in the base device directory.
105 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available
106 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency_available
107 What: /sys/bus/iio/devices/iio:deviceX/in_proximity_sampling_frequency_available
108 What: /sys/.../iio:deviceX/buffer/sampling_frequency_available
109 What: /sys/bus/iio/devices/triggerX/sampling_frequency_available
110 KernelVersion: 2.6.35
111 Contact: linux-iio@vger.kernel.org
113 When the internal sampling clock can only take a specific set of
114 frequencies, we can specify the available values with:
116 - a small discrete set of values like "0 2 4 6 8"
117 - a range with minimum, step and maximum frequencies like
120 What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio
121 KernelVersion: 2.6.38
122 Contact: linux-iio@vger.kernel.org
124 Hardware dependent ADC oversampling. Controls the sampling ratio
125 of the digital filter if available.
127 What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available
128 KernelVersion: 2.6.38
129 Contact: linux-iio@vger.kernel.org
131 Hardware dependent values supported by the oversampling filter.
133 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw
134 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw
135 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_raw
136 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_raw
137 KernelVersion: 2.6.35
138 Contact: linux-iio@vger.kernel.org
140 Raw (unscaled no bias removal etc.) voltage measurement from
141 channel Y. In special cases where the channel does not
142 correspond to externally available input one of the named
143 versions may be used. The number must always be specified and
144 unique to allow association with event codes. Units after
145 application of scale and offset are millivolts.
147 Channels with 'i' and 'q' modifiers always exist in pairs and both
148 channels refer to the same signal. The 'i' channel contains the in-phase
149 component of the signal while the 'q' channel contains the quadrature
152 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
153 KernelVersion: 2.6.35
154 Contact: linux-iio@vger.kernel.org
156 Raw (unscaled) differential voltage measurement equivalent to
157 channel Y - channel Z where these channel numbers apply to the
158 physically equivalent inputs when non differential readings are
159 separately available. In differential only parts, then all that
160 is required is a consistent labeling. Units after application
161 of scale and offset are millivolts.
163 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_raw
164 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_raw
166 Contact: linux-iio@vger.kernel.org
168 Raw (unscaled no bias removal etc.) current measurement from
169 channel Y. In special cases where the channel does not
170 correspond to externally available input one of the named
171 versions may be used. The number must always be specified and
172 unique to allow association with event codes. Units after
173 application of scale and offset are milliamps.
175 What: /sys/bus/iio/devices/iio:deviceX/in_powerY_raw
177 Contact: linux-iio@vger.kernel.org
179 Raw (unscaled no bias removal etc.) power measurement from
180 channel Y. The number must always be specified and
181 unique to allow association with event codes. Units after
182 application of scale and offset are milliwatts.
184 What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw
186 Contact: linux-iio@vger.kernel.org
188 Raw capacitance measurement from channel Y. Units after
189 application of scale and offset are nanofarads.
191 What: /sys/.../iio:deviceX/in_capacitanceY-in_capacitanceZ_raw
193 Contact: linux-iio@vger.kernel.org
195 Raw differential capacitance measurement equivalent to
196 channel Y - channel Z where these channel numbers apply to the
197 physically equivalent inputs when non differential readings are
198 separately available. In differential only parts, then all that
199 is required is a consistent labeling. Units after application
200 of scale and offset are nanofarads.
202 What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw
203 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw
204 What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw
205 What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw
206 What: /sys/bus/iio/devices/iio:deviceX/in_temp_ambient_raw
207 What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_raw
208 KernelVersion: 2.6.35
209 Contact: linux-iio@vger.kernel.org
211 Raw (unscaled no bias removal etc.) temperature measurement.
212 If an axis is specified it generally means that the temperature
213 sensor is associated with one part of a compound device (e.g.
214 a gyroscope axis). The ambient and object modifiers distinguish
215 between ambient (reference) and distant temperature for contact-
216 less measurements. Units after application of scale and offset
217 are milli degrees Celsius.
219 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_input
220 KernelVersion: 2.6.38
221 Contact: linux-iio@vger.kernel.org
223 Scaled temperature measurement in milli degrees Celsius.
225 What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw
226 What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_raw
227 What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_raw
228 KernelVersion: 2.6.35
229 Contact: linux-iio@vger.kernel.org
231 Acceleration in direction x, y or z (may be arbitrarily assigned
232 but should match other such assignments on device).
233 Has all of the equivalent parameters as per voltageY. Units
234 after application of scale and offset are m/s^2.
236 What: /sys/bus/iio/devices/iio:deviceX/in_gravity_x_raw
237 What: /sys/bus/iio/devices/iio:deviceX/in_gravity_y_raw
238 What: /sys/bus/iio/devices/iio:deviceX/in_gravity_z_raw
240 Contact: linux-iio@vger.kernel.org
242 Gravity in direction x, y or z (may be arbitrarily assigned
243 but should match other such assignments on device).
244 Units after application of scale and offset are m/s^2.
246 What: /sys/bus/iio/devices/iio:deviceX/in_angl_raw
247 What: /sys/bus/iio/devices/iio:deviceX/in_anglY_raw
249 Contact: linux-iio@vger.kernel.org
251 Angle of rotation. Units after application of scale and offset
254 What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_x_raw
255 What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_y_raw
257 Contact: linux-iio@vger.kernel.org
259 Relative position in direction x or y on a pad (may be
260 arbitrarily assigned but should match other such assignments on
262 Units after application of scale and offset are milli percents
263 from the pad's size in both directions. Should be calibrated by
266 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_raw
267 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_raw
268 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_raw
269 KernelVersion: 2.6.35
270 Contact: linux-iio@vger.kernel.org
272 Angular velocity about axis x, y or z (may be arbitrarily
273 assigned). Has all the equivalent parameters as per voltageY.
274 Units after application of scale and offset are radians per
277 What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw
278 What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw
279 What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw
280 KernelVersion: 2.6.35
281 Contact: linux-iio@vger.kernel.org
283 Inclination raw reading about axis x, y or z (may be
284 arbitrarily assigned). Data converted by application of offset
285 and scale to degrees.
287 What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw
288 What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw
289 What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw
290 KernelVersion: 2.6.35
291 Contact: linux-iio@vger.kernel.org
293 Magnetic field along axis x, y or z (may be arbitrarily
294 assigned). Data converted by application of offset
297 What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw
298 What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw
299 What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw
300 KernelVersion: 2.6.36
301 Contact: linux-iio@vger.kernel.org
303 Highest value since some reset condition. These
304 attributes allow access to this and are otherwise
305 the direct equivalent of the <type>Y[_name]_raw attributes.
307 What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw
308 KernelVersion: 2.6.36
309 Contact: linux-iio@vger.kernel.org
311 A computed peak value based on the sum squared magnitude of
312 the underlying value in the specified directions.
314 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_raw
315 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_raw
317 Contact: linux-iio@vger.kernel.org
319 Raw pressure measurement from channel Y. Units after
320 application of scale and offset are kilopascal.
322 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_input
323 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_input
325 Contact: linux-iio@vger.kernel.org
327 Scaled pressure measurement from channel Y, in kilopascal.
329 What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_raw
331 Contact: linux-iio@vger.kernel.org
333 Raw humidity measurement of air. Units after application of
334 scale and offset are milli percent.
336 What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_input
338 Contact: linux-iio@vger.kernel.org
340 Scaled humidity measurement in milli percent.
342 What: /sys/bus/iio/devices/iio:deviceX/in_X_mean_raw
344 Contact: linux-iio@vger.kernel.org
346 Averaged raw measurement from channel X. The number of values
347 used for averaging is device specific. The converting rules for
348 normal raw values also applies to the averaged raw values.
350 What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset
351 What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset
352 What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset
353 What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset
354 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset
355 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset
356 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_offset
357 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_offset
358 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_offset
359 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_offset
360 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_offset
361 What: /sys/bus/iio/devices/iio:deviceX/in_current_offset
362 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_offset
363 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_offset
364 What: /sys/bus/iio/devices/iio:deviceX/in_current_q_offset
365 What: /sys/bus/iio/devices/iio:deviceX/in_current_i_offset
366 What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset
367 What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset
368 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
369 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset
370 What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset
371 What: /sys/bus/iio/devices/iio:deviceX/in_magn_offset
372 What: /sys/bus/iio/devices/iio:deviceX/in_rot_offset
373 What: /sys/bus/iio/devices/iio:deviceX/in_angl_offset
374 What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceX_offset
375 KernelVersion: 2.6.35
376 Contact: linux-iio@vger.kernel.org
378 If known for a device, offset to be added to <type>[Y]_raw prior
379 to scaling by <type>[Y]_scale in order to obtain value in the
380 <type> units as specified in <type>[Y]_raw documentation.
381 Not present if the offset is always 0 or unknown. If Y or
382 axis <x|y|z> is not present, then the offset applies to all
383 in channels of <type>.
384 May be writable if a variable offset can be applied on the
385 device. Note that this is different to calibbias which
386 is for devices (or drivers) that apply offsets to compensate
387 for variation between different instances of the part, typically
388 adjusted by using some hardware supported calibration procedure.
389 Calibbias is applied internally, offset is applied in userspace
392 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale
393 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_scale
394 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_scale
395 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale
396 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale
397 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_scale
398 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_scale
399 What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
400 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
401 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
402 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_scale
403 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale
404 What: /sys/bus/iio/devices/iio:deviceX/in_current_scale
405 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_scale
406 What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_scale
407 What: /sys/bus/iio/devices/iio:deviceX/in_current_i_scale
408 What: /sys/bus/iio/devices/iio:deviceX/in_current_q_scale
409 What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale
410 What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale
411 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale
412 What: /sys/bus/iio/devices/iio:deviceX/in_energy_scale
413 What: /sys/bus/iio/devices/iio:deviceX/in_distance_scale
414 What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale
415 What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale
416 What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale
417 What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale
418 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_scale
419 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_scale
420 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_scale
421 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_scale
422 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale
423 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale
424 What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale
425 What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale
426 What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale
427 What: /sys/bus/iio/devices/iio:deviceX/in_countY_scale
428 What: /sys/bus/iio/devices/iio:deviceX/in_angl_scale
429 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_scale
430 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_scale
431 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_scale
432 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_scale
433 KernelVersion: 2.6.35
434 Contact: linux-iio@vger.kernel.org
436 If known for a device, scale to be applied to <type>Y[_name]_raw
437 post addition of <type>[Y][_name]_offset in order to obtain the
438 measured value in <type> units as specified in
439 <type>[Y][_name]_raw documentation. If shared across all in
440 channels then Y and <x|y|z> are not present and the value is
441 called <type>[Y][_name]_scale. The peak modifier means this
442 value is applied to <type>Y[_name]_peak_raw values.
444 What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias
445 What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias
446 What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias
447 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias
448 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias
449 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias
450 What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias
451 What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias
452 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibbias
453 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibbias
454 KernelVersion: 2.6.35
455 Contact: linux-iio@vger.kernel.org
457 Hardware applied calibration offset (assumed to fix production
459 icm42600: For this device values are real physical offsets
460 expressed in SI units (m/s^2 for accelerometers and rad/s
463 What: /sys/bus/iio/devices/iio:deviceX/in_accel_calibbias_available
464 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_calibbias_available
466 Contact: linux-iio@vger.kernel.org
468 Available values of calibbias. Maybe expressed as either of:
470 - a small discrete set of values like "0 2 4 6 8"
471 - a range specified as "[min step max]"
473 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale
474 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale
475 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale
476 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale
477 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale
478 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale
479 What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage_calibscale
480 What: /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
481 What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
482 What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
483 What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale
484 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale
485 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale
486 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale
487 What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale
488 What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale
489 What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale
490 What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale
491 What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale
492 KernelVersion: 2.6.35
493 Contact: linux-iio@vger.kernel.org
495 Hardware applied calibration scale factor (assumed to fix
496 production inaccuracies). If shared across all channels,
497 <type>_calibscale is used.
499 What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender
500 What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender
501 What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender
502 What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender
504 Contact: linux-iio@vger.kernel.org
506 Gender of the user (e.g.: male, female) used by some pedometers
507 to compute the stride length, distance, speed and activity
510 What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available
511 What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available
512 What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available
513 What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available
515 Contact: linux-iio@vger.kernel.org
517 Lists all available gender values (e.g.: male, female).
519 What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibheight
520 What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibheight
521 What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibheight
522 What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibheight
524 Contact: linux-iio@vger.kernel.org
526 Height of the user (in meters) used by some pedometers
527 to compute the stride length, distance, speed and activity
530 What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight
532 Contact: linux-iio@vger.kernel.org
534 Weight of the user (in kg). It is needed by some pedometers
535 to compute the calories burnt by the user.
537 What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available
538 What: /sys/.../iio:deviceX/in_anglvel_scale_available
539 What: /sys/.../iio:deviceX/in_magn_scale_available
540 What: /sys/.../iio:deviceX/in_illuminance_scale_available
541 What: /sys/.../iio:deviceX/in_intensity_scale_available
542 What: /sys/.../iio:deviceX/in_proximity_scale_available
543 What: /sys/.../iio:deviceX/in_voltageX_scale_available
544 What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
545 What: /sys/.../iio:deviceX/out_voltageX_scale_available
546 What: /sys/.../iio:deviceX/out_altvoltageX_scale_available
547 What: /sys/.../iio:deviceX/in_capacitance_scale_available
548 What: /sys/.../iio:deviceX/in_pressure_scale_available
549 What: /sys/.../iio:deviceX/in_pressureY_scale_available
550 KernelVersion: 2.6.35
551 Contact: linux-iio@vger.kernel.org
553 If a discrete set of scale values is available, they
554 are listed in this attribute.
556 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain
557 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain
558 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_red_hardwaregain
559 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_green_hardwaregain
560 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_blue_hardwaregain
561 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_clear_hardwaregain
562 KernelVersion: 2.6.35
563 Contact: linux-iio@vger.kernel.org
565 Hardware applied gain factor. If shared across all channels,
566 <type>_hardwaregain is used.
568 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain_available
570 Contact: linux-iio@vger.kernel.org
572 Lists all available hardware applied gain factors. Shared across all
575 What: /sys/.../in_accel_filter_low_pass_3db_frequency
576 What: /sys/.../in_magn_filter_low_pass_3db_frequency
577 What: /sys/.../in_anglvel_filter_low_pass_3db_frequency
579 Contact: linux-iio@vger.kernel.org
581 If a known or controllable low pass filter is applied
582 to the underlying data channel, then this parameter
583 gives the 3dB frequency of the filter in Hz.
585 What: /sys/.../in_accel_filter_high_pass_3db_frequency
586 What: /sys/.../in_anglvel_filter_high_pass_3db_frequency
587 What: /sys/.../in_magn_filter_high_pass_3db_frequency
589 Contact: linux-iio@vger.kernel.org
591 If a known or controllable high pass filter is applied
592 to the underlying data channel, then this parameter
593 gives the 3dB frequency of the filter in Hz.
595 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
596 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw
597 KernelVersion: 2.6.37
598 Contact: linux-iio@vger.kernel.org
600 Raw (unscaled, no bias etc.) output voltage for
601 channel Y. The number must always be specified and
602 unique if the output corresponds to a single channel.
603 While DAC like devices typically use out_voltage,
604 a continuous frequency generating device, such as
605 a DDS or PLL should use out_altvoltage.
607 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw
608 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw
609 KernelVersion: 2.6.37
610 Contact: linux-iio@vger.kernel.org
612 Raw (unscaled, no bias etc.) output voltage for an aggregate of
613 channel Y, channel Z, etc. This interface is available in cases
614 where a single output sets the value for multiple channels
617 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode
618 What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
619 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode
620 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode
621 KernelVersion: 2.6.38
622 Contact: linux-iio@vger.kernel.org
624 Specifies the output powerdown mode.
625 DAC output stage is disconnected from the amplifier and
626 1kohm_to_gnd: connected to ground via an 1kOhm resistor,
627 2.5kohm_to_gnd: connected to ground via a 2.5kOhm resistor,
628 6kohm_to_gnd: connected to ground via a 6kOhm resistor,
629 20kohm_to_gnd: connected to ground via a 20kOhm resistor,
630 90kohm_to_gnd: connected to ground via a 90kOhm resistor,
631 100kohm_to_gnd: connected to ground via an 100kOhm resistor,
632 125kohm_to_gnd: connected to ground via an 125kOhm resistor,
633 500kohm_to_gnd: connected to ground via a 500kOhm resistor,
634 640kohm_to_gnd: connected to ground via a 640kOhm resistor,
635 three_state: left floating.
636 For a list of available output power down options read
637 outX_powerdown_mode_available. If Y is not present the
638 mode is shared across all outputs.
640 What: /sys/.../iio:deviceX/out_voltageY_powerdown_mode_available
641 What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available
642 What: /sys/.../iio:deviceX/out_altvoltageY_powerdown_mode_available
643 What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available
644 KernelVersion: 2.6.38
645 Contact: linux-iio@vger.kernel.org
647 Lists all available output power down modes.
648 If Y is not present the mode is shared across all outputs.
650 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
651 What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown
652 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
653 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown
654 KernelVersion: 2.6.38
655 Contact: linux-iio@vger.kernel.org
657 Writing 1 causes output Y to enter the power down mode specified
658 by the corresponding outY_powerdown_mode. DAC output stage is
659 disconnected from the amplifier. Clearing returns to normal
660 operation. Y may be suppressed if all outputs are controlled
663 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency
665 Contact: linux-iio@vger.kernel.org
667 Output frequency for channel Y in Hz. The number must always be
668 specified and unique if the output corresponds to a single
670 Some drivers have additional constraints:
671 ADF4371 has an integrated VCO with fundamendal output
672 frequency ranging from 4000000000 Hz 8000000000 Hz.
674 out_altvoltage0_frequency:
675 A divide by 1, 2, 4, 8, 16, 32 or circuit generates
676 frequencies from 62500000 Hz to 8000000000 Hz.
677 out_altvoltage1_frequency:
678 This channel duplicates the channel 0 frequency
679 out_altvoltage2_frequency:
680 A frequency doubler generates frequencies from
681 8000000000 Hz to 16000000000 Hz.
682 out_altvoltage3_frequency:
683 A frequency quadrupler generates frequencies from
684 16000000000 Hz to 32000000000 Hz.
686 Note: writes to one of the channels will affect the frequency of
687 all the other channels, since it involves changing the VCO
688 fundamental output frequency.
690 What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase
692 Contact: linux-iio@vger.kernel.org
694 Phase in radians of one frequency/clock output Y
695 (out_altvoltageY) relative to another frequency/clock output
696 (out_altvoltageZ) of the device X. The number must always be
697 specified and unique if the output corresponds to a single
700 What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw
703 Contact: Johan Hovold <jhovold@gmail.com>
705 Set/get output current for channel Y. Units after application
706 of scale and offset are milliamps.
707 For some devices current channels are used to specify
708 current supplied to elements used in taking a measurement
709 of a different type. E.g. LED currents.
711 What: /sys/bus/iio/devices/iio:deviceX/events
712 KernelVersion: 2.6.35
713 Contact: linux-iio@vger.kernel.org
715 Configuration of which hardware generated events are passed up
718 What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
719 What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
720 What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
721 What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
722 What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
723 What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
724 What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en
725 What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en
726 What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en
727 What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en
728 What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en
729 What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en
730 What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en
731 What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en
732 What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en
733 What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en
734 What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en
735 What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en
736 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_rising_en
737 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_falling_en
738 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_rising_en
739 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_falling_en
740 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_en
741 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_en
742 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_rising_en
743 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_falling_en
744 What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en
745 What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en
746 What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en
747 What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en
748 What: /sys/.../iio:deviceX/events/in_voltageY_thresh_either_en
749 What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en
750 What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en
751 What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_rising_en
752 What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_falling_en
753 KernelVersion: 2.6.37
754 Contact: linux-iio@vger.kernel.org
756 Event generated when channel passes a threshold in the specified
757 (_rising|_falling) direction. If the direction is not specified,
758 then either the device will report an event which ever direction
759 a single threshold value is passed in (e.g.
760 <type>[Y][_name]_<raw|input>_thresh_value) or
761 <type>[Y][_name]_<raw|input>_thresh_rising_value and
762 <type>[Y][_name]_<raw|input>_thresh_falling_value may take
763 different values, but the device can only enable both thresholds
766 Note the driver will assume the last p events requested are
767 to be enabled where p is how many it supports (which may vary
768 depending on the exact set requested. So if you want to be
769 sure you have set what you think you have, check the contents of
770 these attributes after everything is configured. Drivers may
771 have to buffer any parameters so that they are consistent when
772 a given event type is enabled at a future point (and not those for
773 whatever event was previously enabled).
775 What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en
776 What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en
777 What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en
778 What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en
779 What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en
780 What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en
781 What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en
782 What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en
783 What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en
784 What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en
785 What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en
786 What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en
787 What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en
788 What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en
789 What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en
790 What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en
791 What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en
792 What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en
793 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_rising_en
794 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_falling_en
795 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_rising_en
796 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_falling_en
797 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_rising_en
798 What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_falling_en
799 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_rising_en
800 What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_falling_en
801 What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en
802 What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en
803 What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en
804 What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en
805 What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en
806 What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en
807 KernelVersion: 2.6.37
808 Contact: linux-iio@vger.kernel.org
810 Event generated when channel passes a threshold on the rate of
811 change (1st differential) in the specified (_rising|_falling)
812 direction. If the direction is not specified, then either the
813 device will report an event which ever direction a single
814 threshold value is passed in (e.g.
815 <type>[Y][_name]_<raw|input>_roc_value) or
816 <type>[Y][_name]_<raw|input>_roc_rising_value and
817 <type>[Y][_name]_<raw|input>_roc_falling_value may take
818 different values, but the device can only enable both rate of
819 change thresholds or neither.
821 Note the driver will assume the last p events requested are
822 to be enabled where p is however many it supports (which may
823 vary depending on the exact set requested. So if you want to be
824 sure you have set what you think you have, check the contents of
825 these attributes after everything is configured. Drivers may
826 have to buffer any parameters so that they are consistent when
827 a given event type is enabled a future point (and not those for
828 whatever event was previously enabled).
830 What: /sys/.../events/in_capacitanceY_adaptive_thresh_rising_en
831 What: /sys/.../events/in_capacitanceY_adaptive_thresh_falling_en
833 Contact: linux-iio@vger.kernel.org
835 Adaptive thresholds are similar to normal fixed thresholds
836 but the value is expressed as an offset from a value which
837 provides a low frequency approximation of the channel itself.
838 Thus these detect if a rapid change occurs in the specified
839 direction which crosses tracking value + offset.
840 Tracking value calculation is devices specific.
842 What: /sys/.../in_capacitanceY_adaptive_thresh_rising_timeout
843 What: /sys/.../in_capacitanceY_adaptive_thresh_falling_timeout
845 Contact: linux-iio@vger.kernel.org
847 When adaptive thresholds are used, the tracking signal
848 may adjust too slowly to step changes in the raw signal.
849 Thus these specify the time in seconds for which the
850 difference between the slow tracking signal and the raw
851 signal is allowed to remain out-of-range before a reset
852 event occurs in which the tracking signal is made equal
853 to the raw signal, allowing slow tracking to resume and the
854 adaptive threshold event detection to function as expected.
856 What: /sys/.../events/in_accel_thresh_rising_value
857 What: /sys/.../events/in_accel_thresh_falling_value
858 What: /sys/.../events/in_accel_x_raw_thresh_rising_value
859 What: /sys/.../events/in_accel_x_raw_thresh_falling_value
860 What: /sys/.../events/in_accel_y_raw_thresh_rising_value
861 What: /sys/.../events/in_accel_y_raw_thresh_falling_value
862 What: /sys/.../events/in_accel_z_raw_thresh_rising_value
863 What: /sys/.../events/in_accel_z_raw_thresh_falling_value
864 What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value
865 What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value
866 What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value
867 What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value
868 What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value
869 What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value
870 What: /sys/.../events/in_magn_x_raw_thresh_rising_value
871 What: /sys/.../events/in_magn_x_raw_thresh_falling_value
872 What: /sys/.../events/in_magn_y_raw_thresh_rising_value
873 What: /sys/.../events/in_magn_y_raw_thresh_falling_value
874 What: /sys/.../events/in_magn_z_raw_thresh_rising_value
875 What: /sys/.../events/in_magn_z_raw_thresh_falling_value
876 What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_rising_value
877 What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_falling_value
878 What: /sys/.../events/in_rot_from_north_true_raw_thresh_rising_value
879 What: /sys/.../events/in_rot_from_north_true_raw_thresh_falling_value
880 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_rising_value
881 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_falling_value
882 What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_rising_value
883 What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_falling_value
884 What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value
885 What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value
886 What: /sys/.../events/in_voltageY_raw_thresh_rising_value
887 What: /sys/.../events/in_voltageY_raw_thresh_falling_value
888 What: /sys/.../events/in_tempY_raw_thresh_rising_value
889 What: /sys/.../events/in_tempY_raw_thresh_falling_value
890 What: /sys/.../events/in_illuminance0_thresh_falling_value
891 What: /sys/.../events/in_illuminance0_thresh_rising_value
892 What: /sys/.../events/in_proximity0_thresh_falling_value
893 What: /sys/.../events/in_proximity0_thresh_rising_value
894 What: /sys/.../events/in_illuminance_thresh_rising_value
895 What: /sys/.../events/in_illuminance_thresh_falling_value
896 What: /sys/.../events/in_capacitanceY_thresh_rising_value
897 What: /sys/.../events/in_capacitanceY_thresh_falling_value
898 What: /sys/.../events/in_capacitanceY_thresh_adaptive_rising_value
899 What: /sys/.../events/in_capacitanceY_thresh_falling_rising_value
900 KernelVersion: 2.6.37
901 Contact: linux-iio@vger.kernel.org
903 Specifies the value of threshold that the device is comparing
904 against for the events enabled by
905 <type>Y[_name]_thresh[_rising|falling]_en.
907 If separate attributes exist for the two directions, but
908 direction is not specified for this attribute, then a single
909 threshold value applies to both directions.
911 The raw or input element of the name indicates whether the
912 value is in raw device units or in processed units (as _raw
913 and _input do on sysfs direct channel read attributes).
915 What: /sys/.../events/in_accel_scale
916 What: /sys/.../events/in_accel_peak_scale
917 What: /sys/.../events/in_anglvel_scale
918 What: /sys/.../events/in_magn_scale
919 What: /sys/.../events/in_rot_from_north_magnetic_scale
920 What: /sys/.../events/in_rot_from_north_true_scale
921 What: /sys/.../events/in_voltage_scale
922 What: /sys/.../events/in_voltage_supply_scale
923 What: /sys/.../events/in_temp_scale
924 What: /sys/.../events/in_illuminance_scale
925 What: /sys/.../events/in_proximity_scale
927 Contact: linux-iio@vger.kernel.org
929 Specifies the conversion factor from the standard units
930 to device specific units used to set the event trigger
933 What: /sys/.../events/in_accel_x_thresh_rising_hysteresis
934 What: /sys/.../events/in_accel_x_thresh_falling_hysteresis
935 What: /sys/.../events/in_accel_x_thresh_either_hysteresis
936 What: /sys/.../events/in_accel_y_thresh_rising_hysteresis
937 What: /sys/.../events/in_accel_y_thresh_falling_hysteresis
938 What: /sys/.../events/in_accel_y_thresh_either_hysteresis
939 What: /sys/.../events/in_accel_z_thresh_rising_hysteresis
940 What: /sys/.../events/in_accel_z_thresh_falling_hysteresis
941 What: /sys/.../events/in_accel_z_thresh_either_hysteresis
942 What: /sys/.../events/in_anglvel_x_thresh_rising_hysteresis
943 What: /sys/.../events/in_anglvel_x_thresh_falling_hysteresis
944 What: /sys/.../events/in_anglvel_x_thresh_either_hysteresis
945 What: /sys/.../events/in_anglvel_y_thresh_rising_hysteresis
946 What: /sys/.../events/in_anglvel_y_thresh_falling_hysteresis
947 What: /sys/.../events/in_anglvel_y_thresh_either_hysteresis
948 What: /sys/.../events/in_anglvel_z_thresh_rising_hysteresis
949 What: /sys/.../events/in_anglvel_z_thresh_falling_hysteresis
950 What: /sys/.../events/in_anglvel_z_thresh_either_hysteresis
951 What: /sys/.../events/in_magn_x_thresh_rising_hysteresis
952 What: /sys/.../events/in_magn_x_thresh_falling_hysteresis
953 What: /sys/.../events/in_magn_x_thresh_either_hysteresis
954 What: /sys/.../events/in_magn_y_thresh_rising_hysteresis
955 What: /sys/.../events/in_magn_y_thresh_falling_hysteresis
956 What: /sys/.../events/in_magn_y_thresh_either_hysteresis
957 What: /sys/.../events/in_magn_z_thresh_rising_hysteresis
958 What: /sys/.../events/in_magn_z_thresh_falling_hysteresis
959 What: /sys/.../events/in_magn_z_thresh_either_hysteresis
960 What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_hysteresis
961 What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_hysteresis
962 What: /sys/.../events/in_rot_from_north_magnetic_thresh_either_hysteresis
963 What: /sys/.../events/in_rot_from_north_true_thresh_rising_hysteresis
964 What: /sys/.../events/in_rot_from_north_true_thresh_falling_hysteresis
965 What: /sys/.../events/in_rot_from_north_true_thresh_either_hysteresis
966 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_hysteresis
967 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_hysteresis
968 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_either_hysteresis
969 What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_hysteresis
970 What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_hysteresis
971 What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_either_hysteresis
972 What: /sys/.../events/in_voltageY_thresh_rising_hysteresis
973 What: /sys/.../events/in_voltageY_thresh_falling_hysteresis
974 What: /sys/.../events/in_voltageY_thresh_either_hysteresis
975 What: /sys/.../events/in_tempY_thresh_rising_hysteresis
976 What: /sys/.../events/in_tempY_thresh_falling_hysteresis
977 What: /sys/.../events/in_tempY_thresh_either_hysteresis
978 What: /sys/.../events/in_illuminance0_thresh_falling_hysteresis
979 What: /sys/.../events/in_illuminance0_thresh_rising_hysteresis
980 What: /sys/.../events/in_illuminance0_thresh_either_hysteresis
981 What: /sys/.../events/in_proximity0_thresh_falling_hysteresis
982 What: /sys/.../events/in_proximity0_thresh_rising_hysteresis
983 What: /sys/.../events/in_proximity0_thresh_either_hysteresis
985 Contact: linux-iio@vger.kernel.org
987 Specifies the hysteresis of threshold that the device is comparing
988 against for the events enabled by
989 <type>Y[_name]_thresh[_(rising|falling)]_hysteresis.
990 If separate attributes exist for the two directions, but
991 direction is not specified for this attribute, then a single
992 hysteresis value applies to both directions.
994 For falling events the hysteresis is added to the _value attribute for
995 this event to get the upper threshold for when the event goes back to
996 normal, for rising events the hysteresis is subtracted from the _value
997 attribute. E.g. if in_voltage0_raw_thresh_rising_value is set to 1200
998 and in_voltage0_raw_thresh_rising_hysteresis is set to 50. The event
999 will get activated once in_voltage0_raw goes above 1200 and will become
1000 deactivated again once the value falls below 1150.
1002 What: /sys/.../events/in_accel_x_raw_roc_rising_value
1003 What: /sys/.../events/in_accel_x_raw_roc_falling_value
1004 What: /sys/.../events/in_accel_y_raw_roc_rising_value
1005 What: /sys/.../events/in_accel_y_raw_roc_falling_value
1006 What: /sys/.../events/in_accel_z_raw_roc_rising_value
1007 What: /sys/.../events/in_accel_z_raw_roc_falling_value
1008 What: /sys/.../events/in_anglvel_x_raw_roc_rising_value
1009 What: /sys/.../events/in_anglvel_x_raw_roc_falling_value
1010 What: /sys/.../events/in_anglvel_y_raw_roc_rising_value
1011 What: /sys/.../events/in_anglvel_y_raw_roc_falling_value
1012 What: /sys/.../events/in_anglvel_z_raw_roc_rising_value
1013 What: /sys/.../events/in_anglvel_z_raw_roc_falling_value
1014 What: /sys/.../events/in_magn_x_raw_roc_rising_value
1015 What: /sys/.../events/in_magn_x_raw_roc_falling_value
1016 What: /sys/.../events/in_magn_y_raw_roc_rising_value
1017 What: /sys/.../events/in_magn_y_raw_roc_falling_value
1018 What: /sys/.../events/in_magn_z_raw_roc_rising_value
1019 What: /sys/.../events/in_magn_z_raw_roc_falling_value
1020 What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_rising_value
1021 What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_falling_value
1022 What: /sys/.../events/in_rot_from_north_true_raw_roc_rising_value
1023 What: /sys/.../events/in_rot_from_north_true_raw_roc_falling_value
1024 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_rising_value
1025 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_falling_value
1026 What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_rising_value
1027 What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_falling_value
1028 What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value
1029 What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value
1030 What: /sys/.../events/in_voltageY_raw_roc_rising_value
1031 What: /sys/.../events/in_voltageY_raw_roc_falling_value
1032 What: /sys/.../events/in_tempY_raw_roc_rising_value
1033 What: /sys/.../events/in_tempY_raw_roc_falling_value
1034 KernelVersion: 2.6.37
1035 Contact: linux-iio@vger.kernel.org
1037 Specifies the value of rate of change threshold that the
1038 device is comparing against for the events enabled by
1039 <type>[Y][_name]_roc[_rising|falling]_en.
1041 If separate attributes exist for the two directions,
1042 but direction is not specified for this attribute,
1043 then a single threshold value applies to both directions.
1044 The raw or input element of the name indicates whether the
1045 value is in raw device units or in processed units (as _raw
1046 and _input do on sysfs direct channel read attributes).
1048 What: /sys/.../events/in_accel_x_thresh_rising_period
1049 What: /sys/.../events/in_accel_x_thresh_falling_period
1050 What: /sys/.../events/in_accel_x_roc_rising_period
1051 What: /sys/.../events/in_accel_x_roc_falling_period
1052 What: /sys/.../events/in_accel_y_thresh_rising_period
1053 What: /sys/.../events/in_accel_y_thresh_falling_period
1054 What: /sys/.../events/in_accel_y_roc_rising_period
1055 What: /sys/.../events/in_accel_y_roc_falling_period
1056 What: /sys/.../events/in_accel_z_thresh_rising_period
1057 What: /sys/.../events/in_accel_z_thresh_falling_period
1058 What: /sys/.../events/in_accel_z_roc_rising_period
1059 What: /sys/.../events/in_accel_z_roc_falling_period
1060 What: /sys/.../events/in_anglvel_x_thresh_rising_period
1061 What: /sys/.../events/in_anglvel_x_thresh_falling_period
1062 What: /sys/.../events/in_anglvel_x_roc_rising_period
1063 What: /sys/.../events/in_anglvel_x_roc_falling_period
1064 What: /sys/.../events/in_anglvel_y_thresh_rising_period
1065 What: /sys/.../events/in_anglvel_y_thresh_falling_period
1066 What: /sys/.../events/in_anglvel_y_roc_rising_period
1067 What: /sys/.../events/in_anglvel_y_roc_falling_period
1068 What: /sys/.../events/in_anglvel_z_thresh_rising_period
1069 What: /sys/.../events/in_anglvel_z_thresh_falling_period
1070 What: /sys/.../events/in_anglvel_z_roc_rising_period
1071 What: /sys/.../events/in_anglvel_z_roc_falling_period
1072 What: /sys/.../events/in_magn_x_thresh_rising_period
1073 What: /sys/.../events/in_magn_x_thresh_falling_period
1074 What: /sys/.../events/in_magn_x_roc_rising_period
1075 What: /sys/.../events/in_magn_x_roc_falling_period
1076 What: /sys/.../events/in_magn_y_thresh_rising_period
1077 What: /sys/.../events/in_magn_y_thresh_falling_period
1078 What: /sys/.../events/in_magn_y_roc_rising_period
1079 What: /sys/.../events/in_magn_y_roc_falling_period
1080 What: /sys/.../events/in_magn_z_thresh_rising_period
1081 What: /sys/.../events/in_magn_z_thresh_falling_period
1082 What: /sys/.../events/in_magn_z_roc_rising_period
1083 What: /sys/.../events/in_magn_z_roc_falling_period
1084 What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_period
1085 What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_period
1086 What: /sys/.../events/in_rot_from_north_magnetic_roc_rising_period
1087 What: /sys/.../events/in_rot_from_north_magnetic_roc_falling_period
1088 What: /sys/.../events/in_rot_from_north_true_thresh_rising_period
1089 What: /sys/.../events/in_rot_from_north_true_thresh_falling_period
1090 What: /sys/.../events/in_rot_from_north_true_roc_rising_period
1091 What: /sys/.../events/in_rot_from_north_true_roc_falling_period
1092 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_period
1093 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_period
1094 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_rising_period
1095 What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_falling_period
1096 What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_period
1097 What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_period
1098 What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_rising_period
1099 What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_falling_period
1100 What: /sys/.../events/in_voltageY_supply_thresh_rising_period
1101 What: /sys/.../events/in_voltageY_supply_thresh_falling_period
1102 What: /sys/.../events/in_voltageY_supply_roc_rising_period
1103 What: /sys/.../events/in_voltageY_supply_roc_falling_period
1104 What: /sys/.../events/in_voltageY_thresh_rising_period
1105 What: /sys/.../events/in_voltageY_thresh_falling_period
1106 What: /sys/.../events/in_voltageY_roc_rising_period
1107 What: /sys/.../events/in_voltageY_roc_falling_period
1108 What: /sys/.../events/in_tempY_thresh_rising_period
1109 What: /sys/.../events/in_tempY_thresh_falling_period
1110 What: /sys/.../events/in_tempY_roc_rising_period
1111 What: /sys/.../events/in_tempY_roc_falling_period
1112 What: /sys/.../events/in_accel_x&y&z_mag_falling_period
1113 What: /sys/.../events/in_intensity0_thresh_period
1114 What: /sys/.../events/in_proximity0_thresh_period
1115 What: /sys/.../events/in_activity_still_thresh_rising_period
1116 What: /sys/.../events/in_activity_still_thresh_falling_period
1117 What: /sys/.../events/in_activity_walking_thresh_rising_period
1118 What: /sys/.../events/in_activity_walking_thresh_falling_period
1119 What: /sys/.../events/in_activity_jogging_thresh_rising_period
1120 What: /sys/.../events/in_activity_jogging_thresh_falling_period
1121 What: /sys/.../events/in_activity_running_thresh_rising_period
1122 What: /sys/.../events/in_activity_running_thresh_falling_period
1123 What: /sys/.../events/in_illuminance_thresh_either_period
1124 KernelVersion: 2.6.37
1125 Contact: linux-iio@vger.kernel.org
1127 Period of time (in seconds) for which the condition must be
1128 met before an event is generated. If direction is not
1129 specified then this period applies to both directions.
1131 What: /sys/.../events/in_accel_thresh_rising_low_pass_filter_3db
1132 What: /sys/.../events/in_anglvel_thresh_rising_low_pass_filter_3db
1133 What: /sys/.../events/in_magn_thresh_rising_low_pass_filter_3db
1135 Contact: linux-iio@vger.kernel.org
1137 If a low pass filter can be applied to the event generation
1138 this property gives its 3db frequency in Hz.
1139 A value of zero disables the filter.
1141 What: /sys/.../events/in_accel_thresh_rising_high_pass_filter_3db
1142 What: /sys/.../events/in_anglvel_thresh_rising_high_pass_filter_3db
1143 What: /sys/.../events/in_magn_thresh_rising_high_pass_filter_3db
1145 Contact: linux-iio@vger.kernel.org
1147 If a high pass filter can be applied to the event generation
1148 this property gives its 3db frequency in Hz.
1149 A value of zero disables the filter.
1151 What: /sys/.../events/in_activity_still_thresh_rising_en
1152 What: /sys/.../events/in_activity_still_thresh_falling_en
1153 What: /sys/.../events/in_activity_walking_thresh_rising_en
1154 What: /sys/.../events/in_activity_walking_thresh_falling_en
1155 What: /sys/.../events/in_activity_jogging_thresh_rising_en
1156 What: /sys/.../events/in_activity_jogging_thresh_falling_en
1157 What: /sys/.../events/in_activity_running_thresh_rising_en
1158 What: /sys/.../events/in_activity_running_thresh_falling_en
1160 Contact: linux-iio@vger.kernel.org
1162 Enables or disables activity events. Depending on direction
1163 an event is generated when sensor ENTERS or LEAVES a given state.
1165 What: /sys/.../events/in_activity_still_thresh_rising_value
1166 What: /sys/.../events/in_activity_still_thresh_falling_value
1167 What: /sys/.../events/in_activity_walking_thresh_rising_value
1168 What: /sys/.../events/in_activity_walking_thresh_falling_value
1169 What: /sys/.../events/in_activity_jogging_thresh_rising_value
1170 What: /sys/.../events/in_activity_jogging_thresh_falling_value
1171 What: /sys/.../events/in_activity_running_thresh_rising_value
1172 What: /sys/.../events/in_activity_running_thresh_falling_value
1174 Contact: linux-iio@vger.kernel.org
1176 Confidence value (in units as percentage) to be used
1177 for deciding when an event should be generated. E.g for
1178 running: If the confidence value reported by the sensor
1179 is greater than in_activity_running_thresh_rising_value
1180 then the sensor ENTERS running state. Conversely, if the
1181 confidence value reported by the sensor is lower than
1182 in_activity_running_thresh_falling_value then the sensor
1183 is LEAVING running state.
1185 What: /sys/.../iio:deviceX/events/in_accel_mag_en
1186 What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en
1187 What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en
1188 What: /sys/.../iio:deviceX/events/in_accel_x_mag_en
1189 What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en
1190 What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en
1191 What: /sys/.../iio:deviceX/events/in_accel_y_mag_en
1192 What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en
1193 What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en
1194 What: /sys/.../iio:deviceX/events/in_accel_z_mag_en
1195 What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en
1196 What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en
1197 What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en
1198 What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en
1199 KernelVersion: 2.6.37
1200 Contact: linux-iio@vger.kernel.org
1202 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the
1203 magnitude of the channel is compared to the threshold, not its
1206 What: /sys/.../events/in_accel_raw_mag_value
1207 What: /sys/.../events/in_accel_x_raw_mag_rising_value
1208 What: /sys/.../events/in_accel_y_raw_mag_rising_value
1209 What: /sys/.../events/in_accel_z_raw_mag_rising_value
1210 KernelVersion: 2.6.37
1211 Contact: linux-iio@vger.kernel.org
1213 The value to which the magnitude of the channel is compared. If
1214 number or direction is not specified, applies to all channels of
1217 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_en
1218 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_en
1219 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_en
1220 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_en
1221 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_en
1222 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_en
1224 Contact: linux-iio@vger.kernel.org
1226 Similar to in_accel_mag[_y][_rising|_falling]_en, but the event
1227 value is relative to a reference magnitude. The reference magnitude
1228 includes the graviational acceleration.
1230 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_value
1231 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_value
1232 What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_value
1233 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_value
1234 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_value
1235 What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_value
1237 Contact: linux-iio@vger.kernel.org
1239 The value to which the reference magnitude of the channel is
1240 compared. If the axis is not specified, it applies to all channels
1243 What: /sys/.../events/in_steps_change_en
1245 Contact: linux-iio@vger.kernel.org
1247 Event generated when channel passes a threshold on the absolute
1248 change in value. E.g. for steps: a step change event is
1249 generated each time the user takes N steps, where N is set using
1250 in_steps_change_value.
1252 What: /sys/.../events/in_steps_change_value
1254 Contact: linux-iio@vger.kernel.org
1256 Specifies the value of change threshold that the
1257 device is comparing against for the events enabled by
1258 <type>[Y][_name]_roc[_rising|falling|]_en. E.g. for steps:
1259 if set to 3, a step change event will be generated every 3
1262 What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
1263 KernelVersion: 2.6.35
1264 Contact: linux-iio@vger.kernel.org
1266 The name of the trigger source being used, as per string given
1267 in /sys/class/iio/triggerY/name.
1269 What: /sys/bus/iio/devices/iio:deviceX/bufferY/length
1271 Contact: linux-iio@vger.kernel.org
1273 Number of scans contained by the buffer.
1275 What: /sys/bus/iio/devices/iio:deviceX/bufferY/enable
1277 Contact: linux-iio@vger.kernel.org
1279 Actually start the buffer capture up. Will start trigger
1280 if first device and appropriate.
1282 Note that it might be impossible to configure other attributes,
1283 (e.g.: events, scale, sampling rate) if they impact the currently
1284 active buffer capture session.
1286 What: /sys/bus/iio/devices/iio:deviceX/bufferY
1288 Contact: linux-iio@vger.kernel.org
1290 Directory containing interfaces for elements that will be
1291 captured for a single triggered sample set in the buffer.
1293 Since kernel 5.11 the scan_elements attributes are merged into
1294 the bufferY directory, to be configurable per buffer.
1296 What: /sys/.../iio:deviceX/bufferY/in_accel_x_en
1297 What: /sys/.../iio:deviceX/bufferY/in_accel_y_en
1298 What: /sys/.../iio:deviceX/bufferY/in_accel_z_en
1299 What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_en
1300 What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_en
1301 What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_en
1302 What: /sys/.../iio:deviceX/bufferY/in_magn_x_en
1303 What: /sys/.../iio:deviceX/bufferY/in_magn_y_en
1304 What: /sys/.../iio:deviceX/bufferY/in_magn_z_en
1305 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_en
1306 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_en
1307 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_en
1308 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_en
1309 What: /sys/.../iio:deviceX/bufferY/in_timestamp_en
1310 What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_en
1311 What: /sys/.../iio:deviceX/bufferY/in_voltageY_en
1312 What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en
1313 What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_en
1314 What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_en
1315 What: /sys/.../iio:deviceX/bufferY/in_voltage_i_en
1316 What: /sys/.../iio:deviceX/bufferY/in_voltage_q_en
1317 What: /sys/.../iio:deviceX/bufferY/in_incli_x_en
1318 What: /sys/.../iio:deviceX/bufferY/in_incli_y_en
1319 What: /sys/.../iio:deviceX/bufferY/in_pressureY_en
1320 What: /sys/.../iio:deviceX/bufferY/in_pressure_en
1321 What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_en
1322 What: /sys/.../iio:deviceX/bufferY/in_proximity_en
1324 Contact: linux-iio@vger.kernel.org
1326 Scan element control for triggered data capture.
1328 What: /sys/.../iio:deviceX/bufferY/in_accel_type
1329 What: /sys/.../iio:deviceX/bufferY/in_anglvel_type
1330 What: /sys/.../iio:deviceX/bufferY/in_magn_type
1331 What: /sys/.../iio:deviceX/bufferY/in_incli_type
1332 What: /sys/.../iio:deviceX/bufferY/in_voltageY_type
1333 What: /sys/.../iio:deviceX/bufferY/in_voltage_type
1334 What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_type
1335 What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_type
1336 What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_type
1337 What: /sys/.../iio:deviceX/bufferY/in_voltage_i_type
1338 What: /sys/.../iio:deviceX/bufferY/in_voltage_q_type
1339 What: /sys/.../iio:deviceX/bufferY/in_timestamp_type
1340 What: /sys/.../iio:deviceX/bufferY/in_pressureY_type
1341 What: /sys/.../iio:deviceX/bufferY/in_pressure_type
1342 What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_type
1343 What: /sys/.../iio:deviceX/bufferY/in_proximity_type
1345 Contact: linux-iio@vger.kernel.org
1347 Description of the scan element data storage within the buffer
1348 and hence the form in which it is read from user-space.
1349 Form is [be|le]:[s|u]bits/storagebits[>>shift].
1350 be or le specifies big or little endian. s or u specifies if
1351 signed (2's complement) or unsigned. bits is the number of bits
1352 of data and storagebits is the space (after padding) that it
1353 occupies in the buffer. shift if specified, is the shift that
1354 needs to be applied prior to masking out unused bits. Some
1355 devices put their data in the middle of the transferred elements
1356 with additional information on both sides. Note that some
1357 devices will have additional information in the unused bits
1358 so to get a clean value, the bits value must be used to mask
1359 the buffer output value appropriately. The storagebits value
1360 also specifies the data alignment. So s48/64>>2 will be a
1361 signed 48 bit integer stored in a 64 bit location aligned to
1362 a 64 bit boundary. To obtain the clean value, shift right 2
1363 and apply a mask to zero the top 16 bits of the result.
1364 For other storage combinations this attribute will be extended
1367 What: /sys/.../iio:deviceX/scan_elements/in_accel_type_available
1368 KernelVersion: 2.6.37
1369 Contact: linux-iio@vger.kernel.org
1371 If the type parameter can take one of a small set of values,
1372 this attribute lists them.
1374 What: /sys/.../iio:deviceX/bufferY/in_voltageY_index
1375 What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_index
1376 What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_index
1377 What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_index
1378 What: /sys/.../iio:deviceX/bufferY/in_voltage_i_index
1379 What: /sys/.../iio:deviceX/bufferY/in_voltage_q_index
1380 What: /sys/.../iio:deviceX/bufferY/in_accel_x_index
1381 What: /sys/.../iio:deviceX/bufferY/in_accel_y_index
1382 What: /sys/.../iio:deviceX/bufferY/in_accel_z_index
1383 What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_index
1384 What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_index
1385 What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_index
1386 What: /sys/.../iio:deviceX/bufferY/in_magn_x_index
1387 What: /sys/.../iio:deviceX/bufferY/in_magn_y_index
1388 What: /sys/.../iio:deviceX/bufferY/in_magn_z_index
1389 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_index
1390 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_index
1391 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_index
1392 What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_index
1393 What: /sys/.../iio:deviceX/bufferY/in_incli_x_index
1394 What: /sys/.../iio:deviceX/bufferY/in_incli_y_index
1395 What: /sys/.../iio:deviceX/bufferY/in_timestamp_index
1396 What: /sys/.../iio:deviceX/bufferY/in_pressureY_index
1397 What: /sys/.../iio:deviceX/bufferY/in_pressure_index
1398 What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_index
1399 What: /sys/.../iio:deviceX/bufferY/in_proximity_index
1401 Contact: linux-iio@vger.kernel.org
1403 A single positive integer specifying the position of this
1404 scan element in the buffer. Note these are not dependent on
1405 what is enabled and may not be contiguous. Thus for user-space
1406 to establish the full layout these must be used in conjunction
1407 with all _en attributes to establish which channels are present,
1408 and the relevant _type attributes to establish the data storage
1411 What: /sys/.../iio:deviceX/in_activity_still_input
1412 What: /sys/.../iio:deviceX/in_activity_walking_input
1413 What: /sys/.../iio:deviceX/in_activity_jogging_input
1414 What: /sys/.../iio:deviceX/in_activity_running_input
1416 Contact: linux-iio@vger.kernel.org
1418 This attribute is used to read the confidence for an activity
1419 expressed in units as percentage.
1421 What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw
1422 KernelVersion: 2.6.38
1423 Contact: linux-iio@vger.kernel.org
1425 This attribute is used to read the amount of quadrature error
1426 present in the device at a given time.
1428 What: /sys/.../iio:deviceX/in_accelX_power_mode
1430 Contact: linux-iio@vger.kernel.org
1432 Specifies the chip power mode.
1433 low_noise: reduce noise level from ADC,
1434 low_power: enable low current consumption.
1435 For a list of available output power modes read
1436 in_accel_power_mode_available.
1438 What: /sys/.../iio:deviceX/in_energy_input
1439 What: /sys/.../iio:deviceX/in_energy_raw
1441 Contact: linux-iio@vger.kernel.org
1443 This attribute is used to read the energy value reported by the
1444 device (e.g.: human activity sensors report energy burnt by the
1445 user). Units after application of scale are Joules.
1447 What: /sys/.../iio:deviceX/in_distance_input
1448 What: /sys/.../iio:deviceX/in_distance_raw
1450 Contact: linux-iio@vger.kernel.org
1452 This attribute is used to read the measured distance to an object
1453 or the distance covered by the user since the last reboot while
1454 activated. Units after application of scale are meters.
1456 What: /sys/bus/iio/devices/iio:deviceX/store_eeprom
1457 KernelVersion: 3.4.0
1458 Contact: linux-iio@vger.kernel.org
1460 Writing '1' stores the current device configuration into
1461 on-chip EEPROM. After power-up or chip reset the device will
1462 automatically load the saved configuration.
1464 What: /sys/.../iio:deviceX/in_proximity_raw
1465 What: /sys/.../iio:deviceX/in_proximity_input
1466 What: /sys/.../iio:deviceX/in_proximityY_raw
1468 Contact: linux-iio@vger.kernel.org
1470 Proximity measurement indicating that some
1471 object is near the sensor, usually by observing
1472 reflectivity of infrared or ultrasound emitted.
1474 Often these sensors are unit less and as such conversion
1475 to SI units is not possible. Higher proximity measurements
1476 indicate closer objects, and vice versa. Units after
1477 application of scale and offset are meters.
1479 What: /sys/.../iio:deviceX/in_illuminance_input
1480 What: /sys/.../iio:deviceX/in_illuminance_raw
1481 What: /sys/.../iio:deviceX/in_illuminanceY_input
1482 What: /sys/.../iio:deviceX/in_illuminanceY_raw
1483 What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw
1484 What: /sys/.../iio:deviceX/in_illuminance_ir_raw
1485 What: /sys/.../iio:deviceX/in_illuminance_clear_raw
1487 Contact: linux-iio@vger.kernel.org
1489 Illuminance measurement, units after application of scale
1492 What: /sys/.../iio:deviceX/in_intensityY_raw
1493 What: /sys/.../iio:deviceX/in_intensityY_ir_raw
1494 What: /sys/.../iio:deviceX/in_intensityY_both_raw
1495 What: /sys/.../iio:deviceX/in_intensityY_uv_raw
1496 What: /sys/.../iio:deviceX/in_intensityY_duv_raw
1498 Contact: linux-iio@vger.kernel.org
1500 Unit-less light intensity. Modifiers both and ir indicate
1501 that measurements contain visible and infrared light
1502 components or just infrared light, respectively. Modifier
1503 uv indicates that measurements contain ultraviolet light
1504 components. Modifier duv indicates that measurements
1505 contain deep ultraviolet light components.
1507 What: /sys/.../iio:deviceX/in_uvindex_input
1509 Contact: linux-iio@vger.kernel.org
1511 UV light intensity index measuring the human skin's response to
1512 different wavelength of sunlight weighted according to the
1513 standardised CIE Erythemal Action Spectrum. UV index values range
1514 from 0 (low) to >=11 (extreme).
1516 What: /sys/.../iio:deviceX/in_intensity_integration_time
1517 What: /sys/.../iio:deviceX/in_intensity_red_integration_time
1518 What: /sys/.../iio:deviceX/in_intensity_green_integration_time
1519 What: /sys/.../iio:deviceX/in_intensity_blue_integration_time
1520 What: /sys/.../iio:deviceX/in_intensity_clear_integration_time
1521 What: /sys/.../iio:deviceX/in_illuminance_integration_time
1523 Contact: linux-iio@vger.kernel.org
1525 This attribute is used to get/set the integration time in
1526 seconds. If shared across all channels of a given type,
1527 <type>_integration_time is used.
1529 What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time
1531 Contact: linux-iio@vger.kernel.org
1533 Number of seconds in which to compute speed.
1535 What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw
1537 Contact: linux-iio@vger.kernel.org
1539 Raw value of quaternion components using a format
1540 x y z w. Here x, y, and z component represents the axis about
1541 which a rotation will occur and w component represents the
1544 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_raw
1545 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_raw
1546 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_raw
1547 What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_raw
1549 Contact: linux-iio@vger.kernel.org
1551 Raw value of rotation from true/magnetic north measured with
1552 or without compensation from tilt sensors.
1554 What: /sys/bus/iio/devices/iio:deviceX/in_currentX_raw
1555 What: /sys/bus/iio/devices/iio:deviceX/in_currentX_i_raw
1556 What: /sys/bus/iio/devices/iio:deviceX/in_currentX_q_raw
1558 Contact: linux-iio@vger.kernel.org
1560 Raw current measurement from channel X. Units are in milliamps
1561 after application of scale and offset. If no offset or scale is
1562 present, output should be considered as processed with the
1565 Channels with 'i' and 'q' modifiers always exist in pairs and both
1566 channels refer to the same signal. The 'i' channel contains the in-phase
1567 component of the signal while the 'q' channel contains the quadrature
1570 What: /sys/.../iio:deviceX/in_energy_en
1571 What: /sys/.../iio:deviceX/in_distance_en
1572 What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_en
1573 What: /sys/.../iio:deviceX/in_steps_en
1575 Contact: linux-iio@vger.kernel.org
1577 Activates a device feature that runs in firmware/hardware.
1578 E.g. for steps: the pedometer saves power while not used;
1579 when activated, it will count the steps taken by the user in
1580 firmware and export them through in_steps_input.
1582 What: /sys/.../iio:deviceX/in_steps_input
1584 Contact: linux-iio@vger.kernel.org
1586 This attribute is used to read the number of steps taken by the user
1587 since the last reboot while activated.
1589 What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_input
1590 What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_raw
1592 Contact: linux-iio@vger.kernel.org
1594 This attribute is used to read the current speed value of the
1595 user (which is the norm or magnitude of the velocity vector).
1596 Units after application of scale are m/s.
1598 What: /sys/.../iio:deviceX/in_steps_debounce_count
1600 Contact: linux-iio@vger.kernel.org
1602 Specifies the number of steps that must occur within
1603 in_steps_filter_debounce_time for the pedometer to decide the
1604 consumer is making steps.
1606 What: /sys/.../iio:deviceX/in_steps_debounce_time
1608 Contact: linux-iio@vger.kernel.org
1610 Specifies number of seconds in which we compute the steps
1611 that occur in order to decide if the consumer is making steps.
1613 What: /sys/bus/iio/devices/iio:deviceX/bufferY/watermark
1615 Contact: linux-iio@vger.kernel.org
1617 A single positive integer specifying the maximum number of scan
1618 elements to wait for.
1620 Poll will block until the watermark is reached.
1622 Blocking read will wait until the minimum between the requested
1623 read amount or the low water mark is available.
1625 Non-blocking read will retrieve the available samples from the
1626 buffer even if there are less samples then watermark level. This
1627 allows the application to block on poll with a timeout and read
1628 the available samples after the timeout expires and thus have a
1629 maximum delay guarantee.
1631 What: /sys/bus/iio/devices/iio:deviceX/bufferY/data_available
1633 Contact: linux-iio@vger.kernel.org
1635 A read-only value indicating the bytes of data available in the
1636 buffer. In the case of an output buffer, this indicates the
1637 amount of empty space available to write data to. In the case of
1638 an input buffer, this indicates the amount of data available for
1641 What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled
1643 Contact: linux-iio@vger.kernel.org
1645 A read-only boolean value that indicates if the hardware fifo is
1646 currently enabled or disabled. If the device does not have a
1647 hardware fifo this entry is not present.
1648 The hardware fifo is enabled when the buffer is enabled if the
1649 current hardware fifo watermark level is set and other current
1650 device settings allows it (e.g. if a trigger is set that samples
1651 data differently that the hardware fifo does then hardware fifo
1654 If the hardware fifo is enabled and the level of the hardware
1655 fifo reaches the hardware fifo watermark level the device will
1656 flush its hardware fifo to the device buffer. Doing a non
1657 blocking read on the device when no samples are present in the
1658 device buffer will also force a flush.
1660 When the hardware fifo is enabled there is no need to use a
1661 trigger to use buffer mode since the watermark settings
1662 guarantees that the hardware fifo is flushed to the device
1665 What: /sys/bus/iio/devices/iio:device*/buffer/hwfifo_timeout
1667 Contact: linux-iio@vger.kernel.org
1669 A read/write property to provide capability to delay reporting of
1670 samples till a timeout is reached. This allows host processors to
1671 sleep, while the sensor is storing samples in its internal fifo.
1672 The maximum timeout in seconds can be specified by setting
1673 hwfifo_timeout.The current delay can be read by reading
1674 hwfifo_timeout. A value of 0 means that there is no timeout.
1676 What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark
1678 Contact: linux-iio@vger.kernel.org
1680 Read-only entry that contains a single integer specifying the
1681 current watermark level for the hardware fifo. If the device
1682 does not have a hardware fifo this entry is not present.
1683 The watermark level for the hardware fifo is set by the driver
1684 based on the value set by the user in buffer/watermark but
1685 taking into account hardware limitations (e.g. most hardware
1686 buffers are limited to 32-64 samples, some hardware buffers
1687 watermarks are fixed or have minimum levels). A value of 0
1688 means that the hardware watermark is unset.
1690 What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_min
1692 Contact: linux-iio@vger.kernel.org
1694 A single positive integer specifying the minimum watermark level
1695 for the hardware fifo of this device. If the device does not
1696 have a hardware fifo this entry is not present.
1698 If the user sets buffer/watermark to a value less than this one,
1699 then the hardware watermark will remain unset.
1701 What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_max
1703 Contact: linux-iio@vger.kernel.org
1705 A single positive integer specifying the maximum watermark level
1706 for the hardware fifo of this device. If the device does not
1707 have a hardware fifo this entry is not present.
1709 If the user sets buffer/watermark to a value greater than this
1710 one, then the hardware watermark will be capped at this value.
1712 What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_available
1714 Contact: linux-iio@vger.kernel.org
1716 A list of positive integers specifying the available watermark
1717 levels for the hardware fifo. This entry is optional and if it
1718 is not present it means that all the values between
1719 hwfifo_watermark_min and hwfifo_watermark_max are supported.
1721 If the user sets buffer/watermark to a value greater than
1722 hwfifo_watermak_min but not equal to any of the values in this
1723 list, the driver will chose an appropriate value for the
1724 hardware fifo watermark level.
1726 What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibemissivity
1727 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_calibemissivity
1728 What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibemissivity
1729 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibemissivity
1731 Contact: linux-iio@vger.kernel.org
1733 The emissivity ratio of the surface in the field of view of the
1734 contactless temperature sensor. Emissivity varies from 0 to 1,
1735 with 1 being the emissivity of a black body.
1737 What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_oversampling_ratio
1738 What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_oversampling_ratio
1739 What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_oversampling_ratio
1741 Contact: linux-iio@vger.kernel.org
1743 Hardware applied number of measurements for acquiring one
1744 data point. The HW will do <type>[_name]_oversampling_ratio
1745 measurements and return the average value as output data. Each
1746 value resulted from <type>[_name]_oversampling_ratio measurements
1747 is considered as one sample for <type>[_name]_sampling_frequency.
1749 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_raw
1750 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_raw
1751 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_raw
1752 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_co2_raw
1753 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_ethanol_raw
1754 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_ethanol_raw
1755 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_h2_raw
1756 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_h2_raw
1757 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_o2_raw
1758 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_o2_raw
1759 What: /sys/bus/iio/devices/iio:deviceX/in_concentration_voc_raw
1760 What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_voc_raw
1762 Contact: linux-iio@vger.kernel.org
1764 Raw (unscaled no offset etc.) reading of a substance. Units
1765 after application of scale and offset are percents.
1767 What: /sys/bus/iio/devices/iio:deviceX/in_resistance_raw
1768 What: /sys/bus/iio/devices/iio:deviceX/in_resistanceX_raw
1769 What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw
1770 What: /sys/bus/iio/devices/iio:deviceX/out_resistanceX_raw
1772 Contact: linux-iio@vger.kernel.org
1774 Raw (unscaled no offset etc.) resistance reading that can be processed
1777 What: /sys/bus/iio/devices/iio:deviceX/heater_enable
1778 KernelVersion: 4.1.0
1779 Contact: linux-iio@vger.kernel.org
1781 '1' (enable) or '0' (disable) specifying the enable
1782 of heater function. Same reading values apply.
1784 This ABI is especially applicable for humidity sensors
1785 to heatup the device and get rid of any condensation
1786 in some humidity environment
1788 What: /sys/bus/iio/devices/iio:deviceX/in_ph_raw
1790 Contact: linux-iio@vger.kernel.org
1792 Raw (unscaled no offset etc.) pH reading of a substance as a negative
1793 base-10 logarithm of hydrodium ions in a litre of water.
1795 What: /sys/bus/iio/devices/iio:deviceX/mount_matrix
1796 What: /sys/bus/iio/devices/iio:deviceX/in_mount_matrix
1797 What: /sys/bus/iio/devices/iio:deviceX/out_mount_matrix
1798 What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_mount_matrix
1799 What: /sys/bus/iio/devices/iio:deviceX/in_accel_mount_matrix
1801 Contact: linux-iio@vger.kernel.org
1803 Mounting matrix for IIO sensors. This is a rotation matrix which
1804 informs userspace about sensor chip's placement relative to the
1805 main hardware it is mounted on.
1807 Main hardware placement is defined according to the local
1808 reference frame related to the physical quantity the sensor
1811 Given that the rotation matrix is defined in a board specific
1812 way (platform data and / or device-tree), the main hardware
1813 reference frame definition is left to the implementor's choice
1814 (see below for a magnetometer example).
1816 Applications should apply this rotation matrix to samples so
1817 that when main hardware reference frame is aligned onto local
1818 reference frame, then sensor chip reference frame is also
1819 perfectly aligned with it.
1821 Matrix is a 3x3 unitary matrix and typically looks like
1822 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
1823 [1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware
1824 are perfectly aligned with each other.
1826 For example, a mounting matrix for a magnetometer sensor informs
1827 userspace about sensor chip's ORIENTATION relative to the main
1830 More specifically, main hardware orientation is defined with
1831 respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where :
1833 * Y is in the ground plane and positive towards magnetic North ;
1834 * X is in the ground plane, perpendicular to the North axis and
1835 positive towards the East ;
1836 * Z is perpendicular to the ground plane and positive upwards.
1838 An implementor might consider that for a hand-held device, a
1839 'natural' orientation would be 'front facing camera at the top'.
1840 The main hardware reference frame could then be described as :
1842 * Y is in the plane of the screen and is positive towards the
1844 * X is in the plane of the screen, perpendicular to Y axis, and
1845 positive towards the right hand side of the screen ;
1846 * Z is perpendicular to the screen plane and positive out of the
1849 Another example for a quadrotor UAV might be :
1851 * Y is in the plane of the propellers and positive towards the
1853 * X is in the plane of the propellers, perpendicular to Y axis,
1854 and positive towards the starboard side of the UAV ;
1855 * Z is perpendicular to propellers plane and positive upwards.
1857 What: /sys/bus/iio/devices/iio:deviceX/in_electricalconductivity_raw
1859 Contact: linux-iio@vger.kernel.org
1861 Raw (unscaled no offset etc.) electric conductivity reading that
1862 can be processed to siemens per meter.
1864 What: /sys/bus/iio/devices/iio:deviceX/in_countY_raw
1866 Contact: linux-iio@vger.kernel.org
1868 This interface is deprecated; please use the Counter subsystem.
1870 Raw counter device counts from channel Y. For quadrature
1871 counters, multiplication by an available [Y]_scale results in
1872 the counts of a single quadrature signal phase from channel Y.
1874 What: /sys/bus/iio/devices/iio:deviceX/in_indexY_raw
1876 Contact: linux-iio@vger.kernel.org
1878 This interface is deprecated; please use the Counter subsystem.
1880 Raw counter device index value from channel Y. This attribute
1881 provides an absolute positional reference (e.g. a pulse once per
1882 revolution) which may be used to home positional systems as
1885 What: /sys/bus/iio/devices/iio:deviceX/in_count_count_direction_available
1887 Contact: linux-iio@vger.kernel.org
1889 This interface is deprecated; please use the Counter subsystem.
1891 A list of possible counting directions which are:
1893 - "up" : counter device is increasing.
1894 - "down": counter device is decreasing.
1896 What: /sys/bus/iio/devices/iio:deviceX/in_countY_count_direction
1898 Contact: linux-iio@vger.kernel.org
1900 This interface is deprecated; please use the Counter subsystem.
1902 Raw counter device counters direction for channel Y.
1904 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_label
1905 What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_label
1907 Contact: linux-iio@vger.kernel.org
1909 Optional symbolic label to a device channel.
1910 If a label is defined for this channel add that to the channel
1911 specific attributes. This is useful for userspace to be able to
1912 better identify an individual channel.
1914 What: /sys/bus/iio/devices/iio:deviceX/in_phaseY_raw
1916 Contact: linux-iio@vger.kernel.org
1918 Raw (unscaled) phase difference reading from channel Y
1919 that can be processed to radians.
1921 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm1_input
1922 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm1_input
1923 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm2p5_input
1924 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm2p5_input
1925 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm4_input
1926 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm4_input
1927 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm10_input
1928 What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm10_input
1930 Contact: linux-iio@vger.kernel.org
1932 Mass concentration reading of particulate matter in ug / m3.
1933 pmX consists of particles with aerodynamic diameter less or
1934 equal to X micrometers.
1936 What: /sys/bus/iio/devices/iio:deviceX/events/in_illuminance_period_available
1939 Contact: linux-iio@vger.kernel.org
1941 List of valid periods (in seconds) for which the light intensity
1942 must be above the threshold level before interrupt is asserted.
1944 What: /sys/bus/iio/devices/iio:deviceX/in_filter_notch_center_frequency
1946 Contact: linux-iio@vger.kernel.org
1948 Center frequency in Hz for a notch filter. Used i.e. for line
1951 What: /sys/bus/iio/devices/iio:deviceX/in_temp_thermocouple_type
1953 Contact: linux-iio@vger.kernel.org
1955 One of the following thermocouple types: B, E, J, K, N, R, S, T.
1957 What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibambient
1958 What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibambient
1960 Contact: linux-iio@vger.kernel.org
1962 Calibrated ambient temperature for object temperature
1963 calculation in milli degrees Celsius.
1965 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_raw
1966 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_raw
1967 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_raw
1969 Contact: linux-iio@vger.kernel.org
1971 Unscaled light intensity according to CIE 1931/DIN 5033 color space.
1972 Units after application of scale are nano nanowatts per square meter.
1974 What: /sys/bus/iio/devices/iio:deviceX/in_anglY_label
1976 Contact: linux-iio@vger.kernel.org
1978 Optional symbolic label for channel Y.
1979 For Intel hid hinge sensor, the label values are:
1980 hinge, keyboard, screen. It means the three channels
1981 each correspond respectively to hinge angle, keyboard angle,
1984 What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_hysteresis_relative
1985 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hysteresis_relative
1987 Contact: linux-iio@vger.kernel.org
1989 Specify the percent for light sensor relative to the channel
1990 absolute value that a data field should change before an event
1991 is generated. Units are a percentage of the prior reading.
1993 What: /sys/bus/iio/devices/iio:deviceX/calibration_auto_enable
1996 Contact: linux-iio@vger.kernel.org
1998 Some sensors have the ability to apply auto calibration at
1999 runtime. For example, it may be necessary to compensate for
2000 contaminant build-up in a measurement chamber or optical
2001 element deterioration that would otherwise lead to sensor drift.
2003 Writing 1 or 0 to this attribute will respectively activate or
2004 deactivate this auto calibration function.
2006 Upon reading, the current status is returned.
2008 What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value
2011 Contact: linux-iio@vger.kernel.org
2013 Some sensors have the ability to apply a manual calibration using
2014 a known measurement value, perhaps obtained from an external
2017 Writing a value to this function will force such a calibration
2018 change. For the scd30 the value should be from the range
2021 Note for the scd30 that a valid value may only be obtained once
2022 it is has been written. Until then any read back of this value
2023 should be ignored. As for the scd4x an error will be returned
2024 immediately if the manual calibration has failed.
2026 What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value_available
2028 Contact: linux-iio@vger.kernel.org
2030 Available range for the forced calibration value, expressed as:
2032 - a range specified as "[min step max]"
projects / releases.git / blob