2342 lines · plain
1What: /sys/bus/iio/devices/iio:deviceX2KernelVersion: 2.6.353Contact: linux-iio@vger.kernel.org4Description:5 Hardware chip or device accessed by one communication port.6 Corresponds to a grouping of sensor channels. X is the IIO7 index of the device.8 9What: /sys/bus/iio/devices/triggerX10KernelVersion: 2.6.3511Contact: linux-iio@vger.kernel.org12Description: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 device15 based on hardware generated events (e.g. data ready) or16 provided by a separate driver for other hardware (e.g.17 periodic timer, GPIO or high resolution timer).18 19 Contains trigger type specific elements. These do not20 generalize well and hence are not documented in this file.21 X is the IIO index of the trigger.22 23What: /sys/bus/iio/devices/iio:deviceX/buffer24KernelVersion: 2.6.3525Contact: linux-iio@vger.kernel.org26Description:27 Directory of attributes relating to the buffer for the device.28 29What: /sys/bus/iio/devices/iio:deviceX/name30KernelVersion: 2.6.3531Contact: linux-iio@vger.kernel.org32Description:33 Description of the physical chip / device for device X.34 Typically a part number.35 36What: /sys/bus/iio/devices/iio:deviceX/label37KernelVersion: 5.838Contact: linux-iio@vger.kernel.org39Description:40 Optional symbolic label for a device.41 This is useful for userspace to be able to better identify an42 individual device.43 44 The contents of the label are free-form, but there are some45 standardized uses:46 47 For proximity sensors which give the proximity (of a person) to48 a certain wlan or wwan antenna the following standardized labels49 are used:50 51 * "proximity-wifi"52 * "proximity-lte"53 * "proximity-wifi-lte"54 * "proximity-wifi-left"55 * "proximity-wifi-right"56 57 These are used to indicate to userspace that these proximity58 sensors may be used to tune transmit power to ensure that59 Specific Absorption Rate (SAR) limits are honored.60 The "-left" and "-right" labels are for devices with multiple61 antennas.62 63 In some laptops/tablets the standardized proximity sensor labels64 instead indicate proximity to a specific part of the device:65 66 * "proximity-palmrest" indicates proximity to the keyboard's palmrest67 * "proximity-palmrest-left" indicates proximity to the left part of the palmrest68 * "proximity-palmrest-right" indicates proximity to the right part of the palmrest69 * "proximity-lap" indicates the device is being used on someone's lap70 71 Note "proximity-lap" is special in that its value may be72 calculated by firmware from other sensor readings, rather then73 being a raw sensor reading.74 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:78 79 * "accel-base"80 * "accel-display"81 82 For devices where an accelerometer is housed in the swivel camera subassembly83 (for AR application), the following standardized label is used:84 85 * "accel-camera"86 87What: /sys/bus/iio/devices/iio:deviceX/current_timestamp_clock88KernelVersion: 4.589Contact: linux-iio@vger.kernel.org90Description:91 String identifying current posix clock used to timestamp92 buffered samples and events for device X.93 94What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency95What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency96What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency97What: /sys/bus/iio/devices/triggerX/sampling_frequency98KernelVersion: 2.6.3599Contact: linux-iio@vger.kernel.org100Description:101 Some devices have internal clocks. This parameter sets the102 resulting sampling frequency. In many devices this103 parameter has an effect on input filters etc. rather than104 simply controlling when the input is sampled. As this105 affects data ready triggers, hardware buffers and the sysfs106 direct access interfaces, it may be found in any of the107 relevant directories. If it affects all of the above108 then it is to be found in the base device directory.109 110 The stm32-timer-trigger has the additional characteristic that111 a sampling_frequency of 0 is defined to stop sampling.112 113What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available114What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency_available115What: /sys/bus/iio/devices/iio:deviceX/in_proximity_sampling_frequency_available116What: /sys/.../iio:deviceX/buffer/sampling_frequency_available117What: /sys/bus/iio/devices/triggerX/sampling_frequency_available118KernelVersion: 2.6.35119Contact: linux-iio@vger.kernel.org120Description:121 When the internal sampling clock can only take a specific set of122 frequencies, we can specify the available values with:123 124 - a small discrete set of values like "0 2 4 6 8"125 - a range with minimum, step and maximum frequencies like126 "[min step max]"127 128What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio129KernelVersion: 2.6.38130Contact: linux-iio@vger.kernel.org131Description:132 Hardware dependent ADC oversampling. Controls the sampling ratio133 of the digital filter if available.134 135What: /sys/bus/iio/devices/iio:deviceX/oversampling_ratio_available136KernelVersion: 2.6.38137Contact: linux-iio@vger.kernel.org138Description:139 Hardware dependent values supported by the oversampling filter.140 141What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_raw142What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_raw143What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_raw144What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_raw145KernelVersion: 2.6.35146Contact: linux-iio@vger.kernel.org147Description:148 Raw (unscaled no bias removal etc.) voltage measurement from149 channel Y. In special cases where the channel does not150 correspond to externally available input one of the named151 versions may be used. The number must always be specified and152 unique to allow association with event codes. Units after153 application of scale and offset are millivolts.154 155 Channels with 'i' and 'q' modifiers always exist in pairs and both156 channels refer to the same signal. The 'i' channel contains the in-phase157 component of the signal while the 'q' channel contains the quadrature158 component.159 160What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw161KernelVersion: 2.6.35162Contact: linux-iio@vger.kernel.org163Description:164 Raw (unscaled) differential voltage measurement equivalent to165 channel Y - channel Z where these channel numbers apply to the166 physically equivalent inputs when non differential readings are167 separately available. In differential only parts, then all that168 is required is a consistent labeling. Units after application169 of scale and offset are millivolts.170 171What: /sys/bus/iio/devices/iio:deviceX/in_currentY_raw172What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_raw173KernelVersion: 3.17174Contact: linux-iio@vger.kernel.org175Description:176 Raw (unscaled no bias removal etc.) current measurement from177 channel Y. In special cases where the channel does not178 correspond to externally available input one of the named179 versions may be used. The number must always be specified and180 unique to allow association with event codes. Units after181 application of scale and offset are milliamps.182 183What: /sys/bus/iio/devices/iio:deviceX/in_powerY_raw184KernelVersion: 4.5185Contact: linux-iio@vger.kernel.org186Description:187 Raw (unscaled no bias removal etc.) power measurement from188 channel Y. The number must always be specified and189 unique to allow association with event codes. Units after190 application of scale and offset are milliwatts.191 192What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_raw193KernelVersion: 3.2194Contact: linux-iio@vger.kernel.org195Description:196 Raw capacitance measurement from channel Y. Units after197 application of scale and offset are nanofarads.198 199What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_raw200KernelVersion: 3.2201Contact: linux-iio@vger.kernel.org202Description:203 Raw differential capacitance measurement equivalent to204 channel Y - channel Z where these channel numbers apply to the205 physically equivalent inputs when non differential readings are206 separately available. In differential only parts, then all that207 is required is a consistent labeling. Units after application208 of scale and offset are nanofarads.209 210What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_zeropoint211KernelVersion: 6.1212Contact: linux-iio@vger.kernel.org213Description:214 For differential channels, this an offset that is applied215 equally to both inputs. As the reading is of the difference216 between the two inputs, this should not be applied to the _raw217 reading by userspace (unlike _offset) and unlike calibbias218 it does not affect the differential value measured because219 the effect of _zeropoint cancels out across the two inputs220 that make up the differential pair. It's purpose is to bring221 the individual signals, before the differential is measured,222 within the measurement range of the device. The naming is223 chosen because if the separate inputs that make the224 differential pair are drawn on a graph in their225 _raw units, this is the value that the zero point on the226 measurement axis represents. It is expressed with the227 same scaling as _raw.228 229What: /sys/bus/iio/devices/iio:deviceX/in_temp_raw230What: /sys/bus/iio/devices/iio:deviceX/in_tempX_raw231What: /sys/bus/iio/devices/iio:deviceX/in_temp_x_raw232What: /sys/bus/iio/devices/iio:deviceX/in_temp_y_raw233What: /sys/bus/iio/devices/iio:deviceX/in_temp_ambient_raw234What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_raw235KernelVersion: 2.6.35236Contact: linux-iio@vger.kernel.org237Description:238 Raw (unscaled no bias removal etc.) temperature measurement.239 If an axis is specified it generally means that the temperature240 sensor is associated with one part of a compound device (e.g.241 a gyroscope axis). The ambient and object modifiers distinguish242 between ambient (reference) and distant temperature for contact-243 less measurements. Units after application of scale and offset244 are milli degrees Celsius.245 246What: /sys/bus/iio/devices/iio:deviceX/in_tempY_input247What: /sys/bus/iio/devices/iio:deviceX/in_temp_input248KernelVersion: 2.6.38249Contact: linux-iio@vger.kernel.org250Description:251 Scaled temperature measurement in milli degrees Celsius.252 253What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw254What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_raw255What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_raw256KernelVersion: 2.6.35257Contact: linux-iio@vger.kernel.org258Description:259 Acceleration in direction x, y or z (may be arbitrarily assigned260 but should match other such assignments on device).261 Has all of the equivalent parameters as per voltageY. Units262 after application of scale and offset are m/s^2.263 264What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_x_raw265What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_y_raw266What: /sys/bus/iio/devices/iio:deviceX/in_accel_linear_z_raw267KernelVersion: 6.1268Contact: linux-iio@vger.kernel.org269Description:270 As per in_accel_X_raw attributes, but minus the271 acceleration due to gravity.272 273What: /sys/bus/iio/devices/iio:deviceX/in_gravity_x_raw274What: /sys/bus/iio/devices/iio:deviceX/in_gravity_y_raw275What: /sys/bus/iio/devices/iio:deviceX/in_gravity_z_raw276KernelVersion: 4.11277Contact: linux-iio@vger.kernel.org278Description:279 Gravity in direction x, y or z (may be arbitrarily assigned280 but should match other such assignments on device).281 Units after application of scale and offset are m/s^2.282 283What: /sys/bus/iio/devices/iio:deviceX/in_deltaangl_x_raw284What: /sys/bus/iio/devices/iio:deviceX/in_deltaangl_y_raw285What: /sys/bus/iio/devices/iio:deviceX/in_deltaangl_z_raw286KernelVersion: 6.5287Contact: linux-iio@vger.kernel.org288Description:289 Angular displacement between two consecutive samples on x, y or290 z (may be arbitrarily assigned but should match other such291 assignments on device).292 In order to compute the total angular displacement during a293 desired period of time, the application should sum-up the delta294 angle samples acquired during that time.295 Units after application of scale and offset are radians.296 297What: /sys/bus/iio/devices/iio:deviceX/in_deltavelocity_x_raw298What: /sys/bus/iio/devices/iio:deviceX/in_deltavelocity_y_raw299What: /sys/bus/iio/devices/iio:deviceX/in_deltavelocity_z_raw300KernelVersion: 6.5301Contact: linux-iio@vger.kernel.org302Description:303 The linear velocity change between two consecutive samples on x,304 y or z (may be arbitrarily assigned but should match other such305 assignments on device).306 In order to compute the total linear velocity change during a307 desired period of time, the application should sum-up the delta308 velocity samples acquired during that time.309 Units after application of scale and offset are meters per310 second.311 312What: /sys/bus/iio/devices/iio:deviceX/in_angl_raw313What: /sys/bus/iio/devices/iio:deviceX/in_anglY_raw314KernelVersion: 4.17315Contact: linux-iio@vger.kernel.org316Description:317 Angle of rotation. Units after application of scale and offset318 are radians.319 320What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_x_raw321What: /sys/bus/iio/devices/iio:deviceX/in_positionrelative_y_raw322KernelVersion: 4.19323Contact: linux-iio@vger.kernel.org324Description:325 Relative position in direction x or y on a pad (may be326 arbitrarily assigned but should match other such assignments on327 device).328 Units after application of scale and offset are milli percents329 from the pad's size in both directions. Should be calibrated by330 the consumer.331 332What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_raw333What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_raw334What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_raw335KernelVersion: 2.6.35336Contact: linux-iio@vger.kernel.org337Description:338 Angular velocity about axis x, y or z (may be arbitrarily339 assigned). Has all the equivalent parameters as per voltageY.340 Units after application of scale and offset are radians per341 second.342 343What: /sys/bus/iio/devices/iio:deviceX/in_incli_x_raw344What: /sys/bus/iio/devices/iio:deviceX/in_incli_y_raw345What: /sys/bus/iio/devices/iio:deviceX/in_incli_z_raw346KernelVersion: 2.6.35347Contact: linux-iio@vger.kernel.org348Description:349 Inclination raw reading about axis x, y or z (may be350 arbitrarily assigned). Data converted by application of offset351 and scale to degrees.352 353What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_raw354What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_raw355What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_raw356KernelVersion: 2.6.35357Contact: linux-iio@vger.kernel.org358Description:359 Magnetic field along axis x, y or z (may be arbitrarily360 assigned). Data converted by application of offset361 then scale to Gauss.362 363What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_peak_raw364What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_peak_raw365What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_peak_raw366What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_peak_raw367What: /sys/bus/iio/devices/iio:deviceX/in_temp_peak_raw368KernelVersion: 2.6.36369Contact: linux-iio@vger.kernel.org370Description:371 Highest value since some reset condition. These372 attributes allow access to this and are otherwise373 the direct equivalent of the <type>Y[_name]_raw attributes.374 375What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_trough_raw376What: /sys/bus/iio/devices/iio:deviceX/in_temp_trough_raw377KernelVersion: 6.7378Contact: linux-iio@vger.kernel.org379Description:380 Lowest value since some reset condition. These381 attributes allow access to this and are otherwise382 the direct equivalent of the <type>Y[_name]_raw attributes.383 384What: /sys/bus/iio/devices/iio:deviceX/in_accel_xyz_squared_peak_raw385KernelVersion: 2.6.36386Contact: linux-iio@vger.kernel.org387Description:388 A computed peak value based on the sum squared magnitude of389 the underlying value in the specified directions.390 391What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_raw392What: /sys/bus/iio/devices/iio:deviceX/in_pressure_raw393KernelVersion: 3.8394Contact: linux-iio@vger.kernel.org395Description:396 Raw pressure measurement from channel Y. Units after397 application of scale and offset are kilopascal.398 399What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_input400What: /sys/bus/iio/devices/iio:deviceX/in_pressure_input401KernelVersion: 3.8402Contact: linux-iio@vger.kernel.org403Description:404 Scaled pressure measurement from channel Y, in kilopascal.405 406What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_raw407KernelVersion: 3.14408Contact: linux-iio@vger.kernel.org409Description:410 Raw humidity measurement of air. Units after application of411 scale and offset are milli percent.412 413What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_input414KernelVersion: 3.14415Contact: linux-iio@vger.kernel.org416Description:417 Scaled humidity measurement in milli percent.418 419What: /sys/bus/iio/devices/iio:deviceX/in_X_mean_raw420KernelVersion: 3.5421Contact: linux-iio@vger.kernel.org422Description:423 Averaged raw measurement from channel X. The number of values424 used for averaging is device specific. The converting rules for425 normal raw values also applies to the averaged raw values.426 427What: /sys/bus/iio/devices/iio:deviceX/in_accel_offset428What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_offset429What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_offset430What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_offset431What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_offset432What: /sys/bus/iio/devices/iio:deviceX/in_voltage_offset433What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_offset434What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_offset435What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_offset436What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_offset437What: /sys/bus/iio/devices/iio:deviceX/in_currentY_offset438What: /sys/bus/iio/devices/iio:deviceX/in_current_offset439What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_offset440What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_offset441What: /sys/bus/iio/devices/iio:deviceX/in_current_q_offset442What: /sys/bus/iio/devices/iio:deviceX/in_current_i_offset443What: /sys/bus/iio/devices/iio:deviceX/in_tempY_offset444What: /sys/bus/iio/devices/iio:deviceX/in_temp_offset445What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_offset446What: /sys/bus/iio/devices/iio:deviceX/in_pressure_offset447What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_offset448What: /sys/bus/iio/devices/iio:deviceX/in_magn_offset449What: /sys/bus/iio/devices/iio:deviceX/in_rot_offset450What: /sys/bus/iio/devices/iio:deviceX/in_angl_offset451What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceX_offset452KernelVersion: 2.6.35453Contact: linux-iio@vger.kernel.org454Description:455 If known for a device, offset to be added to <type>[Y]_raw prior456 to scaling by <type>[Y]_scale in order to obtain value in the457 <type> units as specified in <type>[Y]_raw documentation.458 Not present if the offset is always 0 or unknown. If Y or459 axis <x|y|z> is not present, then the offset applies to all460 in channels of <type>.461 May be writable if a variable offset can be applied on the462 device. Note that this is different to calibbias which463 is for devices (or drivers) that apply offsets to compensate464 for variation between different instances of the part, typically465 adjusted by using some hardware supported calibration procedure.466 Calibbias is applied internally, offset is applied in userspace467 to the _raw output.468 469What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_scale470What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_scale471What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_scale472What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_scale473What: /sys/bus/iio/devices/iio:deviceX/in_voltage_scale474What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_scale475What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_scale476What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale477What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_scale478What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale479What: /sys/bus/iio/devices/iio:deviceX/in_currentY_scale480What: /sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale481What: /sys/bus/iio/devices/iio:deviceX/in_current_scale482What: /sys/bus/iio/devices/iio:deviceX/in_currentY_i_scale483What: /sys/bus/iio/devices/iio:deviceX/in_currentY_q_scale484What: /sys/bus/iio/devices/iio:deviceX/in_current_i_scale485What: /sys/bus/iio/devices/iio:deviceX/in_current_q_scale486What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale487What: /sys/bus/iio/devices/iio:deviceX/in_accel_peak_scale488What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_scale489What: /sys/bus/iio/devices/iio:deviceX/in_energy_scale490What: /sys/bus/iio/devices/iio:deviceX/in_distance_scale491What: /sys/bus/iio/devices/iio:deviceX/in_magn_scale492What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_scale493What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_scale494What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_scale495What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_scale496What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_scale497What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_scale498What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_scale499What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_scale500What: /sys/bus/iio/devices/iio:deviceX/in_pressure_scale501What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelative_scale502What: /sys/bus/iio/devices/iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_scale503What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_scale504What: /sys/bus/iio/devices/iio:deviceX/in_countY_scale505What: /sys/bus/iio/devices/iio:deviceX/in_deltaangl_scale506What: /sys/bus/iio/devices/iio:deviceX/in_deltavelocity_scale507What: /sys/bus/iio/devices/iio:deviceX/in_angl_scale508What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_scale509What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_scale510What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_scale511What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_scale512KernelVersion: 2.6.35513Contact: linux-iio@vger.kernel.org514Description:515 If known for a device, scale to be applied to <type>Y[_name]_raw516 post addition of <type>[Y][_name]_offset in order to obtain the517 measured value in <type> units as specified in518 <type>[Y][_name]_raw documentation. If shared across all in519 channels then Y and <x|y|z> are not present and the value is520 called <type>[Y][_name]_scale. The peak modifier means this521 value is applied to <type>Y[_name]_peak_raw values.522 523What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibbias524What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibbias525What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibbias526What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_i_calibbias527What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_q_calibbias528What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibbias529What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibbias530What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibbias531What: /sys/bus/iio/devices/iio:deviceX/in_capacitance_calibbias532What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibbias533What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibbias534What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_calibbias535What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_calibbias536What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_calibbias537What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_calibbias538What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibbias539What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibbias540What: /sys/bus/iio/devices/iio:deviceX/in_proximity_calibbias541What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibbias542What: /sys/bus/iio/devices/iio:deviceX/in_resistance_calibbias543What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibbias544What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibbias545What: /sys/bus/iio/devices/iio:deviceX/out_currentY_calibbias546What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_calibbias547KernelVersion: 2.6.35548Contact: linux-iio@vger.kernel.org549Description:550 Hardware applied calibration offset (assumed to fix production551 inaccuracies).552 icm42600: For this device values are real physical offsets553 expressed in SI units (m/s^2 for accelerometers and rad/s554 for gyroscope)/555 556What: /sys/bus/iio/devices/iio:deviceX/in_accel_calibbias_available557What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_calibbias_available558What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibbias_available559What: /sys/bus/iio/devices/iio:deviceX/in_proximity_calibbias_available560What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibbias_available561What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_calibbias_available562KernelVersion: 5.8563Contact: linux-iio@vger.kernel.org564Description:565 Available values of calibbias. Maybe expressed as either of:566 567 - a small discrete set of values like "0 2 4 6 8"568 - a range specified as "[min step max]"569 570What: /sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale571What: /sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale572What: /sys/bus/iio/devices/iio:deviceX/in_accel_z_calibscale573What: /sys/bus/iio/devices/iio:deviceX/in_altvoltage_calibscale574What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_x_calibscale575What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_y_calibscale576What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_z_calibscale577What: /sys/bus/iio/devices/iio:deviceX/in_capacitance_calibscale578What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_calibscale579What: /sys/bus/iio/devices/iio:deviceX/in_illuminance0_calibscale580What: /sys/bus/iio/devices/iio:deviceX/in_intensity_both_calibscale581What: /sys/bus/iio/devices/iio:deviceX/in_intensity_calibscale582What: /sys/bus/iio/devices/iio:deviceX/in_intensity_ir_calibscale583What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_calibscale584What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_calibscale585What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_calibscale586What: /sys/bus/iio/devices/iio:deviceX/in_pressure_calibscale587What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_calibscale588What: /sys/bus/iio/devices/iio:deviceX/in_proximity0_calibscale589What: /sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale590What: /sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale591What: /sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale592What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale593What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale594What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale595What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_supply_calibscale596What: /sys/bus/iio/devices/iio:deviceX/out_currentY_calibscale597What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_calibscale598KernelVersion: 2.6.35599Contact: linux-iio@vger.kernel.org600Description:601 Hardware applied calibration scale factor (assumed to fix602 production inaccuracies). If shared across all channels,603 <type>_calibscale is used.604 605What: /sys/bus/iio/devices/iio:deviceX/in_illuminanceY_calibscale_available606What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_calibscale_available607What: /sys/bus/iio/devices/iio:deviceX/in_proximityY_calibscale_available608What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_calibscale_available609KernelVersion: 4.8610Contact: linux-iio@vger.kernel.org611Description:612 Available values of calibscale. Maybe expressed as either of:613 614 - a small discrete set of values like "1 8 16"615 - a range specified as "[min step max]"616 617 If shared across all channels, <type>_calibscale_available is used.618 619What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender620What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender621What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender622What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender623KernelVersion: 4.0624Contact: linux-iio@vger.kernel.org625Description:626 Gender of the user (e.g.: male, female) used by some pedometers627 to compute the stride length, distance, speed and activity628 type.629 630What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibgender_available631What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibgender_available632What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibgender_available633What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibgender_available634KernelVersion: 4.0635Contact: linux-iio@vger.kernel.org636Description:637 Lists all available gender values (e.g.: male, female).638 639What: /sys/bus/iio/devices/iio:deviceX/in_activity_calibheight640What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibheight641What: /sys/bus/iio/devices/iio:deviceX/in_distance_calibheight642What: /sys/bus/iio/devices/iio:deviceX/in_velocity_calibheight643KernelVersion: 3.19644Contact: linux-iio@vger.kernel.org645Description:646 Height of the user (in meters) used by some pedometers647 to compute the stride length, distance, speed and activity648 type.649 650What: /sys/bus/iio/devices/iio:deviceX/in_energy_calibweight651KernelVersion: 4.0652Contact: linux-iio@vger.kernel.org653Description:654 Weight of the user (in kg). It is needed by some pedometers655 to compute the calories burnt by the user.656 657What: /sys/bus/iio/devices/iio:deviceX/in_accel_scale_available658What: /sys/.../iio:deviceX/in_anglvel_scale_available659What: /sys/.../iio:deviceX/in_magn_scale_available660What: /sys/.../iio:deviceX/in_illuminance_scale_available661What: /sys/.../iio:deviceX/in_intensity_scale_available662What: /sys/.../iio:deviceX/in_proximity_scale_available663What: /sys/.../iio:deviceX/in_voltageX_scale_available664What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available665What: /sys/.../iio:deviceX/out_voltageX_scale_available666What: /sys/.../iio:deviceX/out_altvoltageX_scale_available667What: /sys/.../iio:deviceX/in_capacitance_scale_available668What: /sys/.../iio:deviceX/in_pressure_scale_available669What: /sys/.../iio:deviceX/in_pressureY_scale_available670KernelVersion: 2.6.35671Contact: linux-iio@vger.kernel.org672Description:673 If a discrete set of scale values is available, they674 are listed in this attribute. Unlike illumination,675 multiplying intensity by intensity_scale does not676 yield value with any standardized unit.677 678What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_hardwaregain679What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain680What: /sys/bus/iio/devices/iio:deviceX/in_intensity_red_hardwaregain681What: /sys/bus/iio/devices/iio:deviceX/in_intensity_green_hardwaregain682What: /sys/bus/iio/devices/iio:deviceX/in_intensity_blue_hardwaregain683What: /sys/bus/iio/devices/iio:deviceX/in_intensity_clear_hardwaregain684KernelVersion: 2.6.35685Contact: linux-iio@vger.kernel.org686Description:687 Hardware applied gain factor. If shared across all channels,688 <type>_hardwaregain is used.689 690What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hardwaregain_available691KernelVersion: 5.10692Contact: linux-iio@vger.kernel.org693Description:694 Lists all available hardware applied gain factors. Shared across all695 channels.696 697What: /sys/.../in_accel_filter_low_pass_3db_frequency698What: /sys/.../in_magn_filter_low_pass_3db_frequency699What: /sys/.../in_anglvel_filter_low_pass_3db_frequency700KernelVersion: 3.2701Contact: linux-iio@vger.kernel.org702Description:703 If a known or controllable low pass filter is applied704 to the underlying data channel, then this parameter705 gives the 3dB frequency of the filter in Hz.706 707What: /sys/.../in_accel_filter_high_pass_3db_frequency708What: /sys/.../in_anglvel_filter_high_pass_3db_frequency709What: /sys/.../in_magn_filter_high_pass_3db_frequency710KernelVersion: 4.2711Contact: linux-iio@vger.kernel.org712Description:713 If a known or controllable high pass filter is applied714 to the underlying data channel, then this parameter715 gives the 3dB frequency of the filter in Hz.716 717What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw718What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_raw719KernelVersion: 2.6.37720Contact: linux-iio@vger.kernel.org721Description:722 Raw (unscaled, no bias etc.) output voltage for723 channel Y. The number must always be specified and724 unique if the output corresponds to a single channel.725 While DAC like devices typically use out_voltage,726 a continuous frequency generating device, such as727 a DDS or PLL should use out_altvoltage.728 729What: /sys/bus/iio/devices/iio:deviceX/out_voltageY&Z_raw730What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY&Z_raw731KernelVersion: 2.6.37732Contact: linux-iio@vger.kernel.org733Description:734 Raw (unscaled, no bias etc.) output voltage for an aggregate of735 channel Y, channel Z, etc. This interface is available in cases736 where a single output sets the value for multiple channels737 simultaneously.738 739What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown_mode740What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode741What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown_mode742What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown_mode743KernelVersion: 2.6.38744Contact: linux-iio@vger.kernel.org745Description:746 Specifies the output powerdown mode.747 DAC output stage is disconnected from the amplifier and748 1kohm_to_gnd: connected to ground via an 1kOhm resistor,749 2.5kohm_to_gnd: connected to ground via a 2.5kOhm resistor,750 6kohm_to_gnd: connected to ground via a 6kOhm resistor,751 20kohm_to_gnd: connected to ground via a 20kOhm resistor,752 42kohm_to_gnd: connected to ground via a 42kOhm resistor,753 90kohm_to_gnd: connected to ground via a 90kOhm resistor,754 100kohm_to_gnd: connected to ground via an 100kOhm resistor,755 125kohm_to_gnd: connected to ground via an 125kOhm resistor,756 500kohm_to_gnd: connected to ground via a 500kOhm resistor,757 640kohm_to_gnd: connected to ground via a 640kOhm resistor,758 three_state: left floating.759 For a list of available output power down options read760 outX_powerdown_mode_available. If Y is not present the761 mode is shared across all outputs.762 763What: /sys/.../iio:deviceX/out_voltageY_powerdown_mode_available764What: /sys/.../iio:deviceX/out_voltage_powerdown_mode_available765What: /sys/.../iio:deviceX/out_altvoltageY_powerdown_mode_available766What: /sys/.../iio:deviceX/out_altvoltage_powerdown_mode_available767KernelVersion: 2.6.38768Contact: linux-iio@vger.kernel.org769Description:770 Lists all available output power down modes.771 If Y is not present the mode is shared across all outputs.772 773What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown774What: /sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown775What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown776What: /sys/bus/iio/devices/iio:deviceX/out_altvoltage_powerdown777KernelVersion: 2.6.38778Contact: linux-iio@vger.kernel.org779Description:780 Writing 1 causes output Y to enter the power down mode specified781 by the corresponding outY_powerdown_mode. DAC output stage is782 disconnected from the amplifier. Clearing returns to normal783 operation. Y may be suppressed if all outputs are controlled784 together.785 786What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency787KernelVersion: 3.4.0788Contact: linux-iio@vger.kernel.org789Description:790 Output frequency for channel Y in Hz. The number must always be791 specified and unique if the output corresponds to a single792 channel.793 Some drivers have additional constraints:794 ADF4371 has an integrated VCO with fundamendal output795 frequency ranging from 4000000000 Hz 8000000000 Hz.796 797 out_altvoltage0_frequency:798 A divide by 1, 2, 4, 8, 16, 32 or circuit generates799 frequencies from 62500000 Hz to 8000000000 Hz.800 out_altvoltage1_frequency:801 This channel duplicates the channel 0 frequency802 out_altvoltage2_frequency:803 A frequency doubler generates frequencies from804 8000000000 Hz to 16000000000 Hz.805 out_altvoltage3_frequency:806 A frequency quadrupler generates frequencies from807 16000000000 Hz to 32000000000 Hz.808 809 Note: writes to one of the channels will affect the frequency of810 all the other channels, since it involves changing the VCO811 fundamental output frequency.812 813What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_phase814KernelVersion: 3.4.0815Contact: linux-iio@vger.kernel.org816Description:817 Phase in radians of one frequency/clock output Y818 (out_altvoltageY) relative to another frequency/clock output819 (out_altvoltageZ) of the device X. The number must always be820 specified and unique if the output corresponds to a single821 channel.822 823What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw824Date: May 2012825KernelVersion: 3.5826Contact: Johan Hovold <jhovold@gmail.com>827Description:828 Set/get output current for channel Y. Units after application829 of scale and offset are milliamps.830 For some devices current channels are used to specify831 current supplied to elements used in taking a measurement832 of a different type. E.g. LED currents.833 834What: /sys/bus/iio/devices/iio:deviceX/events835KernelVersion: 2.6.35836Contact: linux-iio@vger.kernel.org837Description:838 Configuration of which hardware generated events are passed up839 to user-space.840 841What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en842What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en843What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en844What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en845What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en846What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en847What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_rising_en848What: /sys/.../iio:deviceX/events/in_anglvel_x_thresh_falling_en849What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_rising_en850What: /sys/.../iio:deviceX/events/in_anglvel_y_thresh_falling_en851What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_rising_en852What: /sys/.../iio:deviceX/events/in_anglvel_z_thresh_falling_en853What: /sys/.../iio:deviceX/events/in_magn_x_thresh_rising_en854What: /sys/.../iio:deviceX/events/in_magn_x_thresh_falling_en855What: /sys/.../iio:deviceX/events/in_magn_y_thresh_rising_en856What: /sys/.../iio:deviceX/events/in_magn_y_thresh_falling_en857What: /sys/.../iio:deviceX/events/in_magn_z_thresh_rising_en858What: /sys/.../iio:deviceX/events/in_magn_z_thresh_falling_en859What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_rising_en860What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_thresh_falling_en861What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_rising_en862What: /sys/.../iio:deviceX/events/in_rot_from_north_true_thresh_falling_en863What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_en864What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_en865What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_rising_en866What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_thresh_falling_en867What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_rising_en868What: /sys/.../iio:deviceX/events/in_voltageY_supply_thresh_falling_en869What: /sys/.../iio:deviceX/events/in_voltageY_thresh_rising_en870What: /sys/.../iio:deviceX/events/in_voltageY_thresh_falling_en871What: /sys/.../iio:deviceX/events/in_voltageY_thresh_either_en872What: /sys/.../iio:deviceX/events/in_tempY_thresh_rising_en873What: /sys/.../iio:deviceX/events/in_tempY_thresh_falling_en874What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_rising_en875What: /sys/.../iio:deviceX/events/in_capacitanceY_thresh_falling_en876KernelVersion: 2.6.37877Contact: linux-iio@vger.kernel.org878Description:879 Event generated when channel passes a threshold in the specified880 (_rising|_falling) direction. If the direction is not specified,881 then either the device will report an event which ever direction882 a single threshold value is passed in (e.g.883 <type>[Y][_name]_<raw|input>_thresh_value) or884 <type>[Y][_name]_<raw|input>_thresh_rising_value and885 <type>[Y][_name]_<raw|input>_thresh_falling_value may take886 different values, but the device can only enable both thresholds887 or neither.888 889 Note the driver will assume the last p events requested are890 to be enabled where p is how many it supports (which may vary891 depending on the exact set requested. So if you want to be892 sure you have set what you think you have, check the contents of893 these attributes after everything is configured. Drivers may894 have to buffer any parameters so that they are consistent when895 a given event type is enabled at a future point (and not those for896 whatever event was previously enabled).897 898What: /sys/.../iio:deviceX/events/in_accel_x_roc_rising_en899What: /sys/.../iio:deviceX/events/in_accel_x_roc_falling_en900What: /sys/.../iio:deviceX/events/in_accel_y_roc_rising_en901What: /sys/.../iio:deviceX/events/in_accel_y_roc_falling_en902What: /sys/.../iio:deviceX/events/in_accel_z_roc_rising_en903What: /sys/.../iio:deviceX/events/in_accel_z_roc_falling_en904What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_rising_en905What: /sys/.../iio:deviceX/events/in_anglvel_x_roc_falling_en906What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_rising_en907What: /sys/.../iio:deviceX/events/in_anglvel_y_roc_falling_en908What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_rising_en909What: /sys/.../iio:deviceX/events/in_anglvel_z_roc_falling_en910What: /sys/.../iio:deviceX/events/in_magn_x_roc_rising_en911What: /sys/.../iio:deviceX/events/in_magn_x_roc_falling_en912What: /sys/.../iio:deviceX/events/in_magn_y_roc_rising_en913What: /sys/.../iio:deviceX/events/in_magn_y_roc_falling_en914What: /sys/.../iio:deviceX/events/in_magn_z_roc_rising_en915What: /sys/.../iio:deviceX/events/in_magn_z_roc_falling_en916What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_rising_en917What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_roc_falling_en918What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_rising_en919What: /sys/.../iio:deviceX/events/in_rot_from_north_true_roc_falling_en920What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_rising_en921What: /sys/.../iio:deviceX/events/in_rot_from_north_magnetic_tilt_comp_roc_falling_en922What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_rising_en923What: /sys/.../iio:deviceX/events/in_rot_from_north_true_tilt_comp_roc_falling_en924What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_rising_en925What: /sys/.../iio:deviceX/events/in_voltageY_supply_roc_falling_en926What: /sys/.../iio:deviceX/events/in_voltageY_roc_rising_en927What: /sys/.../iio:deviceX/events/in_voltageY_roc_falling_en928What: /sys/.../iio:deviceX/events/in_tempY_roc_rising_en929What: /sys/.../iio:deviceX/events/in_tempY_roc_falling_en930KernelVersion: 2.6.37931Contact: linux-iio@vger.kernel.org932Description:933 Event generated when channel passes a threshold on the rate of934 change (1st differential) in the specified (_rising|_falling)935 direction. If the direction is not specified, then either the936 device will report an event which ever direction a single937 threshold value is passed in (e.g.938 <type>[Y][_name]_<raw|input>_roc_value) or939 <type>[Y][_name]_<raw|input>_roc_rising_value and940 <type>[Y][_name]_<raw|input>_roc_falling_value may take941 different values, but the device can only enable both rate of942 change thresholds or neither.943 944 Note the driver will assume the last p events requested are945 to be enabled where p is however many it supports (which may946 vary depending on the exact set requested. So if you want to be947 sure you have set what you think you have, check the contents of948 these attributes after everything is configured. Drivers may949 have to buffer any parameters so that they are consistent when950 a given event type is enabled a future point (and not those for951 whatever event was previously enabled).952 953What: /sys/.../events/in_capacitanceY_adaptive_thresh_rising_en954What: /sys/.../events/in_capacitanceY_adaptive_thresh_falling_en955KernelVersion: 5.13956Contact: linux-iio@vger.kernel.org957Description:958 Adaptive thresholds are similar to normal fixed thresholds959 but the value is expressed as an offset from a value which960 provides a low frequency approximation of the channel itself.961 Thus these detect if a rapid change occurs in the specified962 direction which crosses tracking value + offset.963 Tracking value calculation is devices specific.964 965What: /sys/.../in_capacitanceY_adaptive_thresh_rising_timeout966What: /sys/.../in_capacitanceY_adaptive_thresh_falling_timeout967KernelVersion: 5.11968Contact: linux-iio@vger.kernel.org969Description:970 When adaptive thresholds are used, the tracking signal971 may adjust too slowly to step changes in the raw signal.972 Thus these specify the time in seconds for which the973 difference between the slow tracking signal and the raw974 signal is allowed to remain out-of-range before a reset975 event occurs in which the tracking signal is made equal976 to the raw signal, allowing slow tracking to resume and the977 adaptive threshold event detection to function as expected.978 979What: /sys/.../events/in_accel_thresh_rising_value980What: /sys/.../events/in_accel_thresh_falling_value981What: /sys/.../events/in_accel_x_raw_thresh_rising_value982What: /sys/.../events/in_accel_x_raw_thresh_falling_value983What: /sys/.../events/in_accel_y_raw_thresh_rising_value984What: /sys/.../events/in_accel_y_raw_thresh_falling_value985What: /sys/.../events/in_accel_z_raw_thresh_rising_value986What: /sys/.../events/in_accel_z_raw_thresh_falling_value987What: /sys/.../events/in_anglvel_x_raw_thresh_rising_value988What: /sys/.../events/in_anglvel_x_raw_thresh_falling_value989What: /sys/.../events/in_anglvel_y_raw_thresh_rising_value990What: /sys/.../events/in_anglvel_y_raw_thresh_falling_value991What: /sys/.../events/in_anglvel_z_raw_thresh_rising_value992What: /sys/.../events/in_anglvel_z_raw_thresh_falling_value993What: /sys/.../events/in_magn_x_raw_thresh_rising_value994What: /sys/.../events/in_magn_x_raw_thresh_falling_value995What: /sys/.../events/in_magn_y_raw_thresh_rising_value996What: /sys/.../events/in_magn_y_raw_thresh_falling_value997What: /sys/.../events/in_magn_z_raw_thresh_rising_value998What: /sys/.../events/in_magn_z_raw_thresh_falling_value999What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_rising_value1000What: /sys/.../events/in_rot_from_north_magnetic_raw_thresh_falling_value1001What: /sys/.../events/in_rot_from_north_true_raw_thresh_rising_value1002What: /sys/.../events/in_rot_from_north_true_raw_thresh_falling_value1003What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_rising_value1004What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_thresh_falling_value1005What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_rising_value1006What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_thresh_falling_value1007What: /sys/.../events/in_voltageY_supply_raw_thresh_rising_value1008What: /sys/.../events/in_voltageY_supply_raw_thresh_falling_value1009What: /sys/.../events/in_voltageY_raw_thresh_rising_value1010What: /sys/.../events/in_voltageY_raw_thresh_falling_value1011What: /sys/.../events/in_tempY_raw_thresh_rising_value1012What: /sys/.../events/in_tempY_raw_thresh_falling_value1013What: /sys/.../events/in_illuminance0_thresh_falling_value1014What: /sys/.../events/in_illuminance0_thresh_rising_value1015What: /sys/.../events/in_proximity0_thresh_falling_value1016What: /sys/.../events/in_proximity0_thresh_rising_value1017What: /sys/.../events/in_illuminance_thresh_rising_value1018What: /sys/.../events/in_illuminance_thresh_falling_value1019What: /sys/.../events/in_capacitanceY_thresh_rising_value1020What: /sys/.../events/in_capacitanceY_thresh_falling_value1021What: /sys/.../events/in_capacitanceY_thresh_adaptive_rising_value1022What: /sys/.../events/in_capacitanceY_thresh_falling_rising_value1023KernelVersion: 2.6.371024Contact: linux-iio@vger.kernel.org1025Description:1026 Specifies the value of threshold that the device is comparing1027 against for the events enabled by1028 <type>Y[_name]_thresh[_rising|falling]_en.1029 1030 If separate attributes exist for the two directions, but1031 direction is not specified for this attribute, then a single1032 threshold value applies to both directions.1033 1034 The raw or input element of the name indicates whether the1035 value is in raw device units or in processed units (as _raw1036 and _input do on sysfs direct channel read attributes).1037 1038What: /sys/.../events/in_accel_scale1039What: /sys/.../events/in_accel_peak_scale1040What: /sys/.../events/in_anglvel_scale1041What: /sys/.../events/in_magn_scale1042What: /sys/.../events/in_rot_from_north_magnetic_scale1043What: /sys/.../events/in_rot_from_north_true_scale1044What: /sys/.../events/in_voltage_scale1045What: /sys/.../events/in_voltage_supply_scale1046What: /sys/.../events/in_temp_scale1047What: /sys/.../events/in_illuminance_scale1048What: /sys/.../events/in_proximity_scale1049KernelVersion: 3.211050Contact: linux-iio@vger.kernel.org1051Description:1052 Specifies the conversion factor from the standard units1053 to device specific units used to set the event trigger1054 threshold.1055 1056What: /sys/.../events/in_accel_x_thresh_rising_hysteresis1057What: /sys/.../events/in_accel_x_thresh_falling_hysteresis1058What: /sys/.../events/in_accel_x_thresh_either_hysteresis1059What: /sys/.../events/in_accel_y_thresh_rising_hysteresis1060What: /sys/.../events/in_accel_y_thresh_falling_hysteresis1061What: /sys/.../events/in_accel_y_thresh_either_hysteresis1062What: /sys/.../events/in_accel_z_thresh_rising_hysteresis1063What: /sys/.../events/in_accel_z_thresh_falling_hysteresis1064What: /sys/.../events/in_accel_z_thresh_either_hysteresis1065What: /sys/.../events/in_anglvel_x_thresh_rising_hysteresis1066What: /sys/.../events/in_anglvel_x_thresh_falling_hysteresis1067What: /sys/.../events/in_anglvel_x_thresh_either_hysteresis1068What: /sys/.../events/in_anglvel_y_thresh_rising_hysteresis1069What: /sys/.../events/in_anglvel_y_thresh_falling_hysteresis1070What: /sys/.../events/in_anglvel_y_thresh_either_hysteresis1071What: /sys/.../events/in_anglvel_z_thresh_rising_hysteresis1072What: /sys/.../events/in_anglvel_z_thresh_falling_hysteresis1073What: /sys/.../events/in_anglvel_z_thresh_either_hysteresis1074What: /sys/.../events/in_magn_x_thresh_rising_hysteresis1075What: /sys/.../events/in_magn_x_thresh_falling_hysteresis1076What: /sys/.../events/in_magn_x_thresh_either_hysteresis1077What: /sys/.../events/in_magn_y_thresh_rising_hysteresis1078What: /sys/.../events/in_magn_y_thresh_falling_hysteresis1079What: /sys/.../events/in_magn_y_thresh_either_hysteresis1080What: /sys/.../events/in_magn_z_thresh_rising_hysteresis1081What: /sys/.../events/in_magn_z_thresh_falling_hysteresis1082What: /sys/.../events/in_magn_z_thresh_either_hysteresis1083What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_hysteresis1084What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_hysteresis1085What: /sys/.../events/in_rot_from_north_magnetic_thresh_either_hysteresis1086What: /sys/.../events/in_rot_from_north_true_thresh_rising_hysteresis1087What: /sys/.../events/in_rot_from_north_true_thresh_falling_hysteresis1088What: /sys/.../events/in_rot_from_north_true_thresh_either_hysteresis1089What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_hysteresis1090What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_hysteresis1091What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_either_hysteresis1092What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_hysteresis1093What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_hysteresis1094What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_either_hysteresis1095What: /sys/.../events/in_voltageY_thresh_rising_hysteresis1096What: /sys/.../events/in_voltageY_thresh_falling_hysteresis1097What: /sys/.../events/in_voltageY_thresh_either_hysteresis1098What: /sys/.../events/in_tempY_thresh_rising_hysteresis1099What: /sys/.../events/in_tempY_thresh_falling_hysteresis1100What: /sys/.../events/in_tempY_thresh_either_hysteresis1101What: /sys/.../events/in_illuminance0_thresh_falling_hysteresis1102What: /sys/.../events/in_illuminance0_thresh_rising_hysteresis1103What: /sys/.../events/in_illuminance0_thresh_either_hysteresis1104What: /sys/.../events/in_proximity0_thresh_falling_hysteresis1105What: /sys/.../events/in_proximity0_thresh_rising_hysteresis1106What: /sys/.../events/in_proximity0_thresh_either_hysteresis1107KernelVersion: 3.131108Contact: linux-iio@vger.kernel.org1109Description:1110 Specifies the hysteresis of threshold that the device is comparing1111 against for the events enabled by1112 <type>Y[_name]_thresh[_(rising|falling)]_hysteresis.1113 If separate attributes exist for the two directions, but1114 direction is not specified for this attribute, then a single1115 hysteresis value applies to both directions.1116 1117 For falling events the hysteresis is added to the _value attribute for1118 this event to get the upper threshold for when the event goes back to1119 normal, for rising events the hysteresis is subtracted from the _value1120 attribute. E.g. if in_voltage0_raw_thresh_rising_value is set to 12001121 and in_voltage0_raw_thresh_rising_hysteresis is set to 50. The event1122 will get activated once in_voltage0_raw goes above 1200 and will become1123 deactivated again once the value falls below 1150.1124 1125What: /sys/.../events/in_accel_x_raw_roc_rising_value1126What: /sys/.../events/in_accel_x_raw_roc_falling_value1127What: /sys/.../events/in_accel_y_raw_roc_rising_value1128What: /sys/.../events/in_accel_y_raw_roc_falling_value1129What: /sys/.../events/in_accel_z_raw_roc_rising_value1130What: /sys/.../events/in_accel_z_raw_roc_falling_value1131What: /sys/.../events/in_anglvel_x_raw_roc_rising_value1132What: /sys/.../events/in_anglvel_x_raw_roc_falling_value1133What: /sys/.../events/in_anglvel_y_raw_roc_rising_value1134What: /sys/.../events/in_anglvel_y_raw_roc_falling_value1135What: /sys/.../events/in_anglvel_z_raw_roc_rising_value1136What: /sys/.../events/in_anglvel_z_raw_roc_falling_value1137What: /sys/.../events/in_magn_x_raw_roc_rising_value1138What: /sys/.../events/in_magn_x_raw_roc_falling_value1139What: /sys/.../events/in_magn_y_raw_roc_rising_value1140What: /sys/.../events/in_magn_y_raw_roc_falling_value1141What: /sys/.../events/in_magn_z_raw_roc_rising_value1142What: /sys/.../events/in_magn_z_raw_roc_falling_value1143What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_rising_value1144What: /sys/.../events/in_rot_from_north_magnetic_raw_roc_falling_value1145What: /sys/.../events/in_rot_from_north_true_raw_roc_rising_value1146What: /sys/.../events/in_rot_from_north_true_raw_roc_falling_value1147What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_rising_value1148What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_raw_roc_falling_value1149What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_rising_value1150What: /sys/.../events/in_rot_from_north_true_tilt_comp_raw_roc_falling_value1151What: /sys/.../events/in_voltageY_supply_raw_roc_rising_value1152What: /sys/.../events/in_voltageY_supply_raw_roc_falling_value1153What: /sys/.../events/in_voltageY_raw_roc_rising_value1154What: /sys/.../events/in_voltageY_raw_roc_falling_value1155What: /sys/.../events/in_tempY_raw_roc_rising_value1156What: /sys/.../events/in_tempY_raw_roc_falling_value1157KernelVersion: 2.6.371158Contact: linux-iio@vger.kernel.org1159Description:1160 Specifies the value of rate of change threshold that the1161 device is comparing against for the events enabled by1162 <type>[Y][_name]_roc[_rising|falling]_en.1163 1164 If separate attributes exist for the two directions,1165 but direction is not specified for this attribute,1166 then a single threshold value applies to both directions.1167 The raw or input element of the name indicates whether the1168 value is in raw device units or in processed units (as _raw1169 and _input do on sysfs direct channel read attributes).1170 1171What: /sys/.../events/in_accel_x_thresh_rising_period1172What: /sys/.../events/in_accel_x_thresh_falling_period1173What: /sys/.../events/in_accel_x_roc_rising_period1174What: /sys/.../events/in_accel_x_roc_falling_period1175What: /sys/.../events/in_accel_y_thresh_rising_period1176What: /sys/.../events/in_accel_y_thresh_falling_period1177What: /sys/.../events/in_accel_y_roc_rising_period1178What: /sys/.../events/in_accel_y_roc_falling_period1179What: /sys/.../events/in_accel_z_thresh_rising_period1180What: /sys/.../events/in_accel_z_thresh_falling_period1181What: /sys/.../events/in_accel_z_roc_rising_period1182What: /sys/.../events/in_accel_z_roc_falling_period1183What: /sys/.../events/in_anglvel_x_thresh_rising_period1184What: /sys/.../events/in_anglvel_x_thresh_falling_period1185What: /sys/.../events/in_anglvel_x_roc_rising_period1186What: /sys/.../events/in_anglvel_x_roc_falling_period1187What: /sys/.../events/in_anglvel_y_thresh_rising_period1188What: /sys/.../events/in_anglvel_y_thresh_falling_period1189What: /sys/.../events/in_anglvel_y_roc_rising_period1190What: /sys/.../events/in_anglvel_y_roc_falling_period1191What: /sys/.../events/in_anglvel_z_thresh_rising_period1192What: /sys/.../events/in_anglvel_z_thresh_falling_period1193What: /sys/.../events/in_anglvel_z_roc_rising_period1194What: /sys/.../events/in_anglvel_z_roc_falling_period1195What: /sys/.../events/in_magn_x_thresh_rising_period1196What: /sys/.../events/in_magn_x_thresh_falling_period1197What: /sys/.../events/in_magn_x_roc_rising_period1198What: /sys/.../events/in_magn_x_roc_falling_period1199What: /sys/.../events/in_magn_y_thresh_rising_period1200What: /sys/.../events/in_magn_y_thresh_falling_period1201What: /sys/.../events/in_magn_y_roc_rising_period1202What: /sys/.../events/in_magn_y_roc_falling_period1203What: /sys/.../events/in_magn_z_thresh_rising_period1204What: /sys/.../events/in_magn_z_thresh_falling_period1205What: /sys/.../events/in_magn_z_roc_rising_period1206What: /sys/.../events/in_magn_z_roc_falling_period1207What: /sys/.../events/in_rot_from_north_magnetic_thresh_rising_period1208What: /sys/.../events/in_rot_from_north_magnetic_thresh_falling_period1209What: /sys/.../events/in_rot_from_north_magnetic_roc_rising_period1210What: /sys/.../events/in_rot_from_north_magnetic_roc_falling_period1211What: /sys/.../events/in_rot_from_north_true_thresh_rising_period1212What: /sys/.../events/in_rot_from_north_true_thresh_falling_period1213What: /sys/.../events/in_rot_from_north_true_roc_rising_period1214What: /sys/.../events/in_rot_from_north_true_roc_falling_period1215What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_period1216What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_period1217What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_rising_period1218What: /sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_falling_period1219What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_period1220What: /sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_period1221What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_rising_period1222What: /sys/.../events/in_rot_from_north_true_tilt_comp_roc_falling_period1223What: /sys/.../events/in_voltageY_supply_thresh_rising_period1224What: /sys/.../events/in_voltageY_supply_thresh_falling_period1225What: /sys/.../events/in_voltageY_supply_roc_rising_period1226What: /sys/.../events/in_voltageY_supply_roc_falling_period1227What: /sys/.../events/in_voltageY_thresh_rising_period1228What: /sys/.../events/in_voltageY_thresh_falling_period1229What: /sys/.../events/in_voltageY_roc_rising_period1230What: /sys/.../events/in_voltageY_roc_falling_period1231What: /sys/.../events/in_tempY_thresh_rising_period1232What: /sys/.../events/in_tempY_thresh_falling_period1233What: /sys/.../events/in_tempY_roc_rising_period1234What: /sys/.../events/in_tempY_roc_falling_period1235What: /sys/.../events/in_accel_x&y&z_mag_falling_period1236What: /sys/.../events/in_intensity0_thresh_period1237What: /sys/.../events/in_proximity0_thresh_period1238What: /sys/.../events/in_activity_still_thresh_rising_period1239What: /sys/.../events/in_activity_still_thresh_falling_period1240What: /sys/.../events/in_activity_walking_thresh_rising_period1241What: /sys/.../events/in_activity_walking_thresh_falling_period1242What: /sys/.../events/in_activity_jogging_thresh_rising_period1243What: /sys/.../events/in_activity_jogging_thresh_falling_period1244What: /sys/.../events/in_activity_running_thresh_rising_period1245What: /sys/.../events/in_activity_running_thresh_falling_period1246What: /sys/.../events/in_illuminance_thresh_either_period1247KernelVersion: 2.6.371248Contact: linux-iio@vger.kernel.org1249Description:1250 Period of time (in seconds) for which the condition must be1251 met before an event is generated. If direction is not1252 specified then this period applies to both directions.1253 1254What: /sys/.../events/in_accel_thresh_rising_low_pass_filter_3db1255What: /sys/.../events/in_anglvel_thresh_rising_low_pass_filter_3db1256What: /sys/.../events/in_magn_thresh_rising_low_pass_filter_3db1257KernelVersion: 4.21258Contact: linux-iio@vger.kernel.org1259Description:1260 If a low pass filter can be applied to the event generation1261 this property gives its 3db frequency in Hz.1262 A value of zero disables the filter.1263 1264What: /sys/.../events/in_accel_thresh_rising_high_pass_filter_3db1265What: /sys/.../events/in_anglvel_thresh_rising_high_pass_filter_3db1266What: /sys/.../events/in_magn_thresh_rising_high_pass_filter_3db1267KernelVersion: 4.21268Contact: linux-iio@vger.kernel.org1269Description:1270 If a high pass filter can be applied to the event generation1271 this property gives its 3db frequency in Hz.1272 A value of zero disables the filter.1273 1274What: /sys/.../events/in_activity_still_thresh_rising_en1275What: /sys/.../events/in_activity_still_thresh_falling_en1276What: /sys/.../events/in_activity_walking_thresh_rising_en1277What: /sys/.../events/in_activity_walking_thresh_falling_en1278What: /sys/.../events/in_activity_jogging_thresh_rising_en1279What: /sys/.../events/in_activity_jogging_thresh_falling_en1280What: /sys/.../events/in_activity_running_thresh_rising_en1281What: /sys/.../events/in_activity_running_thresh_falling_en1282KernelVersion: 3.191283Contact: linux-iio@vger.kernel.org1284Description:1285 Enables or disables activity events. Depending on direction1286 an event is generated when sensor ENTERS or LEAVES a given state.1287 1288What: /sys/.../events/in_activity_still_thresh_rising_value1289What: /sys/.../events/in_activity_still_thresh_falling_value1290What: /sys/.../events/in_activity_walking_thresh_rising_value1291What: /sys/.../events/in_activity_walking_thresh_falling_value1292What: /sys/.../events/in_activity_jogging_thresh_rising_value1293What: /sys/.../events/in_activity_jogging_thresh_falling_value1294What: /sys/.../events/in_activity_running_thresh_rising_value1295What: /sys/.../events/in_activity_running_thresh_falling_value1296KernelVersion: 3.191297Contact: linux-iio@vger.kernel.org1298Description:1299 Confidence value (in units as percentage) to be used1300 for deciding when an event should be generated. E.g for1301 running: If the confidence value reported by the sensor1302 is greater than in_activity_running_thresh_rising_value1303 then the sensor ENTERS running state. Conversely, if the1304 confidence value reported by the sensor is lower than1305 in_activity_running_thresh_falling_value then the sensor1306 is LEAVING running state.1307 1308What: /sys/.../iio:deviceX/events/in_accel_mag_en1309What: /sys/.../iio:deviceX/events/in_accel_mag_rising_en1310What: /sys/.../iio:deviceX/events/in_accel_mag_falling_en1311What: /sys/.../iio:deviceX/events/in_accel_x_mag_en1312What: /sys/.../iio:deviceX/events/in_accel_x_mag_rising_en1313What: /sys/.../iio:deviceX/events/in_accel_x_mag_falling_en1314What: /sys/.../iio:deviceX/events/in_accel_y_mag_en1315What: /sys/.../iio:deviceX/events/in_accel_y_mag_rising_en1316What: /sys/.../iio:deviceX/events/in_accel_y_mag_falling_en1317What: /sys/.../iio:deviceX/events/in_accel_z_mag_en1318What: /sys/.../iio:deviceX/events/in_accel_z_mag_rising_en1319What: /sys/.../iio:deviceX/events/in_accel_z_mag_falling_en1320What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_rising_en1321What: /sys/.../iio:deviceX/events/in_accel_x&y&z_mag_falling_en1322KernelVersion: 2.6.371323Contact: linux-iio@vger.kernel.org1324Description:1325 Similar to in_accel_x_thresh[_rising|_falling]_en, but here the1326 magnitude of the channel is compared to the threshold, not its1327 signed value.1328 1329What: /sys/.../events/in_accel_raw_mag_value1330What: /sys/.../events/in_accel_x_raw_mag_rising_value1331What: /sys/.../events/in_accel_y_raw_mag_rising_value1332What: /sys/.../events/in_accel_z_raw_mag_rising_value1333KernelVersion: 2.6.371334Contact: linux-iio@vger.kernel.org1335Description:1336 The value to which the magnitude of the channel is compared. If1337 number or direction is not specified, applies to all channels of1338 this type.1339 1340What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_en1341What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_en1342What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_en1343What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_en1344What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_en1345What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_en1346KernelVersion: 5.181347Contact: linux-iio@vger.kernel.org1348Description:1349 Similar to in_accel_mag[_y][_rising|_falling]_en, but the event1350 value is relative to a reference magnitude. The reference magnitude1351 includes the graviational acceleration.1352 1353What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_value1354What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_value1355What: /sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_value1356What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_value1357What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_value1358What: /sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_value1359KernelVersion: 5.181360Contact: linux-iio@vger.kernel.org1361Description:1362 The value to which the reference magnitude of the channel is1363 compared. If the axis is not specified, it applies to all channels1364 of this type.1365 1366What: /sys/.../events/in_steps_change_en1367KernelVersion: 4.01368Contact: linux-iio@vger.kernel.org1369Description:1370 Event generated when channel passes a threshold on the absolute1371 change in value. E.g. for steps: a step change event is1372 generated each time the user takes N steps, where N is set using1373 in_steps_change_value.1374 1375What: /sys/.../events/in_steps_change_value1376KernelVersion: 4.01377Contact: linux-iio@vger.kernel.org1378Description:1379 Specifies the value of change threshold that the1380 device is comparing against for the events enabled by1381 <type>[Y][_name]_roc[_rising|falling|]_en. E.g. for steps:1382 if set to 3, a step change event will be generated every 31383 steps.1384 1385What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger1386KernelVersion: 2.6.351387Contact: linux-iio@vger.kernel.org1388Description:1389 The name of the trigger source being used, as per string given1390 in /sys/class/iio/triggerY/name.1391 1392What: /sys/bus/iio/devices/iio:deviceX/bufferY/length1393KernelVersion: 5.111394Contact: linux-iio@vger.kernel.org1395Description:1396 Number of scans contained by the buffer.1397 1398What: /sys/bus/iio/devices/iio:deviceX/bufferY/enable1399KernelVersion: 5.111400Contact: linux-iio@vger.kernel.org1401Description:1402 Actually start the buffer capture up. Will start trigger1403 if first device and appropriate.1404 1405 Note that it might be impossible to configure other attributes,1406 (e.g.: events, scale, sampling rate) if they impact the currently1407 active buffer capture session.1408 1409What: /sys/bus/iio/devices/iio:deviceX/bufferY1410KernelVersion: 5.111411Contact: linux-iio@vger.kernel.org1412Description:1413 Directory containing interfaces for elements that will be1414 captured for a single triggered sample set in the buffer.1415 1416 Since kernel 5.11 the scan_elements attributes are merged into1417 the bufferY directory, to be configurable per buffer.1418 1419What: /sys/.../iio:deviceX/bufferY/in_accel_x_en1420What: /sys/.../iio:deviceX/bufferY/in_accel_y_en1421What: /sys/.../iio:deviceX/bufferY/in_accel_z_en1422What: /sys/.../iio:deviceX/bufferY/in_deltaangl_x_en1423What: /sys/.../iio:deviceX/bufferY/in_deltaangl_y_en1424What: /sys/.../iio:deviceX/bufferY/in_deltaangl_z_en1425What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_x_en1426What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_y_en1427What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_z_en1428What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_en1429What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_en1430What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_en1431What: /sys/.../iio:deviceX/bufferY/in_magn_x_en1432What: /sys/.../iio:deviceX/bufferY/in_magn_y_en1433What: /sys/.../iio:deviceX/bufferY/in_magn_z_en1434What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_en1435What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_en1436What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_en1437What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_en1438What: /sys/.../iio:deviceX/bufferY/in_timestamp_en1439What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_en1440What: /sys/.../iio:deviceX/bufferY/in_voltageY_en1441What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en1442What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_en1443What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_en1444What: /sys/.../iio:deviceX/bufferY/in_voltage_i_en1445What: /sys/.../iio:deviceX/bufferY/in_voltage_q_en1446What: /sys/.../iio:deviceX/bufferY/in_incli_x_en1447What: /sys/.../iio:deviceX/bufferY/in_incli_y_en1448What: /sys/.../iio:deviceX/bufferY/in_pressureY_en1449What: /sys/.../iio:deviceX/bufferY/in_pressure_en1450What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_en1451What: /sys/.../iio:deviceX/bufferY/in_proximity_en1452KernelVersion: 5.111453Contact: linux-iio@vger.kernel.org1454Description:1455 Scan element control for triggered data capture.1456 1457What: /sys/.../iio:deviceX/bufferY/in_accel_type1458What: /sys/.../iio:deviceX/bufferY/in_deltaangl_type1459What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_type1460What: /sys/.../iio:deviceX/bufferY/in_anglvel_type1461What: /sys/.../iio:deviceX/bufferY/in_magn_type1462What: /sys/.../iio:deviceX/bufferY/in_incli_type1463What: /sys/.../iio:deviceX/bufferY/in_voltageY_type1464What: /sys/.../iio:deviceX/bufferY/in_voltage_type1465What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_type1466What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_type1467What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_type1468What: /sys/.../iio:deviceX/bufferY/in_voltage_i_type1469What: /sys/.../iio:deviceX/bufferY/in_voltage_q_type1470What: /sys/.../iio:deviceX/bufferY/in_timestamp_type1471What: /sys/.../iio:deviceX/bufferY/in_pressureY_type1472What: /sys/.../iio:deviceX/bufferY/in_pressure_type1473What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_type1474What: /sys/.../iio:deviceX/bufferY/in_proximity_type1475KernelVersion: 5.111476Contact: linux-iio@vger.kernel.org1477Description:1478 Description of the scan element data storage within the buffer1479 and hence the form in which it is read from user-space.1480 Form is [be|le]:[s|u]bits/storagebits[>>shift].1481 be or le specifies big or little endian. s or u specifies if1482 signed (2's complement) or unsigned. bits is the number of bits1483 of data and storagebits is the space (after padding) that it1484 occupies in the buffer. shift if specified, is the shift that1485 needs to be applied prior to masking out unused bits. Some1486 devices put their data in the middle of the transferred elements1487 with additional information on both sides. Note that some1488 devices will have additional information in the unused bits1489 so to get a clean value, the bits value must be used to mask1490 the buffer output value appropriately. The storagebits value1491 also specifies the data alignment. So s48/64>>2 will be a1492 signed 48 bit integer stored in a 64 bit location aligned to1493 a 64 bit boundary. To obtain the clean value, shift right 21494 and apply a mask to zero the top 16 bits of the result.1495 For other storage combinations this attribute will be extended1496 appropriately.1497 1498What: /sys/.../iio:deviceX/scan_elements/in_accel_type_available1499KernelVersion: 2.6.371500Contact: linux-iio@vger.kernel.org1501Description:1502 If the type parameter can take one of a small set of values,1503 this attribute lists them.1504 1505What: /sys/.../iio:deviceX/bufferY/in_voltageY_index1506What: /sys/.../iio:deviceX/bufferY/in_voltageY_supply_index1507What: /sys/.../iio:deviceX/bufferY/in_voltageY_i_index1508What: /sys/.../iio:deviceX/bufferY/in_voltageY_q_index1509What: /sys/.../iio:deviceX/bufferY/in_voltage_i_index1510What: /sys/.../iio:deviceX/bufferY/in_voltage_q_index1511What: /sys/.../iio:deviceX/bufferY/in_accel_x_index1512What: /sys/.../iio:deviceX/bufferY/in_accel_y_index1513What: /sys/.../iio:deviceX/bufferY/in_accel_z_index1514What: /sys/.../iio:deviceX/bufferY/in_deltaangl_x_index1515What: /sys/.../iio:deviceX/bufferY/in_deltaangl_y_index1516What: /sys/.../iio:deviceX/bufferY/in_deltaangl_z_index1517What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_x_index1518What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_y_index1519What: /sys/.../iio:deviceX/bufferY/in_deltavelocity_z_index1520What: /sys/.../iio:deviceX/bufferY/in_anglvel_x_index1521What: /sys/.../iio:deviceX/bufferY/in_anglvel_y_index1522What: /sys/.../iio:deviceX/bufferY/in_anglvel_z_index1523What: /sys/.../iio:deviceX/bufferY/in_magn_x_index1524What: /sys/.../iio:deviceX/bufferY/in_magn_y_index1525What: /sys/.../iio:deviceX/bufferY/in_magn_z_index1526What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_index1527What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_index1528What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_magnetic_tilt_comp_index1529What: /sys/.../iio:deviceX/bufferY/in_rot_from_north_true_tilt_comp_index1530What: /sys/.../iio:deviceX/bufferY/in_incli_x_index1531What: /sys/.../iio:deviceX/bufferY/in_incli_y_index1532What: /sys/.../iio:deviceX/bufferY/in_timestamp_index1533What: /sys/.../iio:deviceX/bufferY/in_pressureY_index1534What: /sys/.../iio:deviceX/bufferY/in_pressure_index1535What: /sys/.../iio:deviceX/bufferY/in_rot_quaternion_index1536What: /sys/.../iio:deviceX/bufferY/in_proximity_index1537KernelVersion: 5.111538Contact: linux-iio@vger.kernel.org1539Description:1540 A single positive integer specifying the position of this1541 scan element in the buffer. Note these are not dependent on1542 what is enabled and may not be contiguous. Thus for user-space1543 to establish the full layout these must be used in conjunction1544 with all _en attributes to establish which channels are present,1545 and the relevant _type attributes to establish the data storage1546 format.1547 1548What: /sys/.../iio:deviceX/in_activity_still_input1549What: /sys/.../iio:deviceX/in_activity_walking_input1550What: /sys/.../iio:deviceX/in_activity_jogging_input1551What: /sys/.../iio:deviceX/in_activity_running_input1552KernelVersion: 3.191553Contact: linux-iio@vger.kernel.org1554Description:1555 This attribute is used to read the confidence for an activity1556 expressed in units as percentage.1557 1558What: /sys/.../iio:deviceX/in_anglvel_z_quadrature_correction_raw1559KernelVersion: 2.6.381560Contact: linux-iio@vger.kernel.org1561Description:1562 This attribute is used to read the amount of quadrature error1563 present in the device at a given time.1564 1565What: /sys/.../iio:deviceX/in_accelX_power_mode1566KernelVersion: 3.111567Contact: linux-iio@vger.kernel.org1568Description:1569 Specifies the chip power mode.1570 low_noise: reduce noise level from ADC,1571 low_power: enable low current consumption.1572 For a list of available output power modes read1573 in_accel_power_mode_available.1574 1575What: /sys/.../iio:deviceX/in_energy_input1576What: /sys/.../iio:deviceX/in_energy_raw1577KernelVersion: 4.01578Contact: linux-iio@vger.kernel.org1579Description:1580 This attribute is used to read the energy value reported by the1581 device (e.g.: human activity sensors report energy burnt by the1582 user). Units after application of scale are Joules.1583 1584What: /sys/.../iio:deviceX/in_distance_input1585What: /sys/.../iio:deviceX/in_distance_raw1586KernelVersion: 4.01587Contact: linux-iio@vger.kernel.org1588Description:1589 This attribute is used to read the measured distance to an object1590 or the distance covered by the user since the last reboot while1591 activated. Units after application of scale are meters.1592 1593What: /sys/bus/iio/devices/iio:deviceX/store_eeprom1594KernelVersion: 3.4.01595Contact: linux-iio@vger.kernel.org1596Description:1597 Writing '1' stores the current device configuration into1598 on-chip EEPROM. After power-up or chip reset the device will1599 automatically load the saved configuration.1600 1601What: /sys/.../iio:deviceX/in_proximity_raw1602What: /sys/.../iio:deviceX/in_proximity_input1603What: /sys/.../iio:deviceX/in_proximityY_raw1604KernelVersion: 3.41605Contact: linux-iio@vger.kernel.org1606Description:1607 Proximity measurement indicating that some1608 object is near the sensor, usually by observing1609 reflectivity of infrared or ultrasound emitted.1610 1611 Often these sensors are unit less and as such conversion1612 to SI units is not possible. Higher proximity measurements1613 indicate closer objects, and vice versa. Units after1614 application of scale and offset are meters.1615 1616What: /sys/.../iio:deviceX/in_illuminance_input1617What: /sys/.../iio:deviceX/in_illuminance_raw1618What: /sys/.../iio:deviceX/in_illuminanceY_input1619What: /sys/.../iio:deviceX/in_illuminanceY_raw1620What: /sys/.../iio:deviceX/in_illuminanceY_mean_raw1621What: /sys/.../iio:deviceX/in_illuminance_ir_raw1622What: /sys/.../iio:deviceX/in_illuminance_clear_raw1623KernelVersion: 3.41624Contact: linux-iio@vger.kernel.org1625Description:1626 Illuminance measurement, units after application of scale1627 and offset are lux.1628 1629What: /sys/.../iio:deviceX/in_intensityY_raw1630What: /sys/.../iio:deviceX/in_intensityY_ir_raw1631What: /sys/.../iio:deviceX/in_intensityY_both_raw1632What: /sys/.../iio:deviceX/in_intensityY_uv_raw1633What: /sys/.../iio:deviceX/in_intensityY_uva_raw1634What: /sys/.../iio:deviceX/in_intensityY_uvb_raw1635What: /sys/.../iio:deviceX/in_intensityY_duv_raw1636KernelVersion: 3.41637Contact: linux-iio@vger.kernel.org1638Description:1639 Unit-less light intensity. Modifiers both and ir indicate1640 that measurements contain visible and infrared light1641 components or just infrared light, respectively. Modifier1642 uv indicates that measurements contain ultraviolet light1643 components. Modifiers uva, uvb and duv indicate that1644 measurements contain A, B or deep (C) ultraviolet light1645 components respectively.1646 1647What: /sys/.../iio:deviceX/in_uvindex_input1648KernelVersion: 4.61649Contact: linux-iio@vger.kernel.org1650Description:1651 UV light intensity index measuring the human skin's response to1652 different wavelength of sunlight weighted according to the1653 standardised CIE Erythemal Action Spectrum. UV index values range1654 from 0 (low) to >=11 (extreme).1655 1656What: /sys/.../iio:deviceX/in_intensity_integration_time1657What: /sys/.../iio:deviceX/in_intensity_red_integration_time1658What: /sys/.../iio:deviceX/in_intensity_green_integration_time1659What: /sys/.../iio:deviceX/in_intensity_blue_integration_time1660What: /sys/.../iio:deviceX/in_intensity_clear_integration_time1661What: /sys/.../iio:deviceX/in_illuminance_integration_time1662KernelVersion: 3.121663Contact: linux-iio@vger.kernel.org1664Description:1665 This attribute is used to get/set the integration time in1666 seconds. If shared across all channels of a given type,1667 <type>_integration_time is used.1668 1669What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_integration_time1670KernelVersion: 4.01671Contact: linux-iio@vger.kernel.org1672Description:1673 Number of seconds in which to compute speed.1674 1675What: /sys/bus/iio/devices/iio:deviceX/in_rot_quaternion_raw1676KernelVersion: 3.151677Contact: linux-iio@vger.kernel.org1678Description:1679 Raw value of quaternion components using a format1680 x y z w. Here x, y, and z component represents the axis about1681 which a rotation will occur and w component represents the1682 amount of rotation.1683 1684What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_tilt_comp_raw1685What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_tilt_comp_raw1686What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_magnetic_raw1687What: /sys/bus/iio/devices/iio:deviceX/in_rot_from_north_true_raw1688KernelVersion: 3.151689Contact: linux-iio@vger.kernel.org1690Description:1691 Raw value of rotation from true/magnetic north measured with1692 or without compensation from tilt sensors.1693 1694What: /sys/bus/iio/devices/iio:deviceX/in_currentX_raw1695What: /sys/bus/iio/devices/iio:deviceX/in_currentX_i_raw1696What: /sys/bus/iio/devices/iio:deviceX/in_currentX_q_raw1697KernelVersion: 3.181698Contact: linux-iio@vger.kernel.org1699Description:1700 Raw current measurement from channel X. Units are in milliamps1701 after application of scale and offset. If no offset or scale is1702 present, output should be considered as processed with the1703 unit in milliamps.1704 1705 Channels with 'i' and 'q' modifiers always exist in pairs and both1706 channels refer to the same signal. The 'i' channel contains the in-phase1707 component of the signal while the 'q' channel contains the quadrature1708 component.1709 1710What: /sys/.../iio:deviceX/in_energy_en1711What: /sys/.../iio:deviceX/in_distance_en1712What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_en1713What: /sys/.../iio:deviceX/in_steps_en1714KernelVersion: 3.191715Contact: linux-iio@vger.kernel.org1716Description:1717 Activates a device feature that runs in firmware/hardware.1718 E.g. for steps: the pedometer saves power while not used;1719 when activated, it will count the steps taken by the user in1720 firmware and export them through in_steps_input.1721 1722What: /sys/.../iio:deviceX/in_steps_input1723KernelVersion: 3.191724Contact: linux-iio@vger.kernel.org1725Description:1726 This attribute is used to read the number of steps taken by the user1727 since the last reboot while activated.1728 1729What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_input1730What: /sys/.../iio:deviceX/in_velocity_sqrt(x^2+y^2+z^2)_raw1731KernelVersion: 3.191732Contact: linux-iio@vger.kernel.org1733Description:1734 This attribute is used to read the current speed value of the1735 user (which is the norm or magnitude of the velocity vector).1736 Units after application of scale are m/s.1737 1738What: /sys/.../iio:deviceX/in_steps_debounce_count1739KernelVersion: 4.01740Contact: linux-iio@vger.kernel.org1741Description:1742 Specifies the number of steps that must occur within1743 in_steps_filter_debounce_time for the pedometer to decide the1744 consumer is making steps.1745 1746What: /sys/.../iio:deviceX/in_steps_debounce_time1747KernelVersion: 4.01748Contact: linux-iio@vger.kernel.org1749Description:1750 Specifies number of seconds in which we compute the steps1751 that occur in order to decide if the consumer is making steps.1752 1753What: /sys/bus/iio/devices/iio:deviceX/bufferY/watermark1754KernelVersion: 5.111755Contact: linux-iio@vger.kernel.org1756Description:1757 A single positive integer specifying the maximum number of scan1758 elements to wait for.1759 1760 Poll will block until the watermark is reached.1761 1762 Blocking read will wait until the minimum between the requested1763 read amount or the low water mark is available.1764 1765 Non-blocking read will retrieve the available samples from the1766 buffer even if there are less samples then watermark level. This1767 allows the application to block on poll with a timeout and read1768 the available samples after the timeout expires and thus have a1769 maximum delay guarantee.1770 1771What: /sys/bus/iio/devices/iio:deviceX/bufferY/data_available1772KernelVersion: 5.111773Contact: linux-iio@vger.kernel.org1774Description:1775 A read-only value indicating the bytes of data available in the1776 buffer. In the case of an output buffer, this indicates the1777 amount of empty space available to write data to. In the case of1778 an input buffer, this indicates the amount of data available for1779 reading.1780 1781What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled1782KernelVersion: 4.21783Contact: linux-iio@vger.kernel.org1784Description:1785 A read-only boolean value that indicates if the hardware fifo is1786 currently enabled or disabled. If the device does not have a1787 hardware fifo this entry is not present.1788 The hardware fifo is enabled when the buffer is enabled if the1789 current hardware fifo watermark level is set and other current1790 device settings allows it (e.g. if a trigger is set that samples1791 data differently that the hardware fifo does then hardware fifo1792 will not enabled).1793 1794 If the hardware fifo is enabled and the level of the hardware1795 fifo reaches the hardware fifo watermark level the device will1796 flush its hardware fifo to the device buffer. Doing a non1797 blocking read on the device when no samples are present in the1798 device buffer will also force a flush.1799 1800 When the hardware fifo is enabled there is no need to use a1801 trigger to use buffer mode since the watermark settings1802 guarantees that the hardware fifo is flushed to the device1803 buffer.1804 1805What: /sys/bus/iio/devices/iio:device*/buffer/hwfifo_timeout1806KernelVersion: 4.121807Contact: linux-iio@vger.kernel.org1808Description:1809 A read/write property to provide capability to delay reporting of1810 samples till a timeout is reached. This allows host processors to1811 sleep, while the sensor is storing samples in its internal fifo.1812 The maximum timeout in seconds can be specified by setting1813 hwfifo_timeout.The current delay can be read by reading1814 hwfifo_timeout. A value of 0 means that there is no timeout.1815 1816What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark1817KernelVersion: 4.21818Contact: linux-iio@vger.kernel.org1819Description:1820 Read-only entry that contains a single integer specifying the1821 current watermark level for the hardware fifo. If the device1822 does not have a hardware fifo this entry is not present.1823 The watermark level for the hardware fifo is set by the driver1824 based on the value set by the user in buffer/watermark but1825 taking into account hardware limitations (e.g. most hardware1826 buffers are limited to 32-64 samples, some hardware buffers1827 watermarks are fixed or have minimum levels). A value of 01828 means that the hardware watermark is unset.1829 1830What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_min1831KernelVersion: 4.21832Contact: linux-iio@vger.kernel.org1833Description:1834 A single positive integer specifying the minimum watermark level1835 for the hardware fifo of this device. If the device does not1836 have a hardware fifo this entry is not present.1837 1838 If the user sets buffer/watermark to a value less than this one,1839 then the hardware watermark will remain unset.1840 1841What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_max1842KernelVersion: 4.21843Contact: linux-iio@vger.kernel.org1844Description:1845 A single positive integer specifying the maximum watermark level1846 for the hardware fifo of this device. If the device does not1847 have a hardware fifo this entry is not present.1848 1849 If the user sets buffer/watermark to a value greater than this1850 one, then the hardware watermark will be capped at this value.1851 1852What: /sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_watermark_available1853KernelVersion: 4.21854Contact: linux-iio@vger.kernel.org1855Description:1856 A list of positive integers specifying the available watermark1857 levels for the hardware fifo. This entry is optional and if it1858 is not present it means that all the values between1859 hwfifo_watermark_min and hwfifo_watermark_max are supported.1860 1861 If the user sets buffer/watermark to a value greater than1862 hwfifo_watermak_min but not equal to any of the values in this1863 list, the driver will chose an appropriate value for the1864 hardware fifo watermark level.1865 1866What: /sys/bus/iio/devices/iio:deviceX/in_temp_calibemissivity1867What: /sys/bus/iio/devices/iio:deviceX/in_tempX_calibemissivity1868What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibemissivity1869What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibemissivity1870KernelVersion: 4.11871Contact: linux-iio@vger.kernel.org1872Description:1873 The emissivity ratio of the surface in the field of view of the1874 contactless temperature sensor. Emissivity varies from 0 to 1,1875 with 1 being the emissivity of a black body.1876 1877What: /sys/bus/iio/devices/iio:deviceX/in_magn_x_oversampling_ratio1878What: /sys/bus/iio/devices/iio:deviceX/in_magn_y_oversampling_ratio1879What: /sys/bus/iio/devices/iio:deviceX/in_magn_z_oversampling_ratio1880KernelVersion: 4.21881Contact: linux-iio@vger.kernel.org1882Description:1883 Hardware applied number of measurements for acquiring one1884 data point. The HW will do <type>[_name]_oversampling_ratio1885 measurements and return the average value as output data. Each1886 value resulted from <type>[_name]_oversampling_ratio measurements1887 is considered as one sample for <type>[_name]_sampling_frequency.1888 1889What: /sys/bus/iio/devices/iio:deviceX/in_concentration_raw1890What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_raw1891What: /sys/bus/iio/devices/iio:deviceX/in_concentration_co2_raw1892What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_co2_raw1893What: /sys/bus/iio/devices/iio:deviceX/in_concentration_ethanol_raw1894What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_ethanol_raw1895What: /sys/bus/iio/devices/iio:deviceX/in_concentration_h2_raw1896What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_h2_raw1897What: /sys/bus/iio/devices/iio:deviceX/in_concentration_o2_raw1898What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_o2_raw1899What: /sys/bus/iio/devices/iio:deviceX/in_concentration_voc_raw1900What: /sys/bus/iio/devices/iio:deviceX/in_concentrationX_voc_raw1901KernelVersion: 4.31902Contact: linux-iio@vger.kernel.org1903Description:1904 Raw (unscaled no offset etc.) reading of a substance. Units1905 after application of scale and offset are percents.1906 1907What: /sys/bus/iio/devices/iio:deviceX/in_resistance_raw1908What: /sys/bus/iio/devices/iio:deviceX/in_resistanceX_raw1909What: /sys/bus/iio/devices/iio:deviceX/out_resistance_raw1910What: /sys/bus/iio/devices/iio:deviceX/out_resistanceX_raw1911KernelVersion: 4.31912Contact: linux-iio@vger.kernel.org1913Description:1914 Raw (unscaled no offset etc.) resistance reading.1915 Units after application of scale and offset are ohms.1916 1917What: /sys/bus/iio/devices/iio:deviceX/heater_enable1918KernelVersion: 4.1.01919Contact: linux-iio@vger.kernel.org1920Description:1921 '1' (enable) or '0' (disable) specifying the enable1922 of heater function. Same reading values apply.1923 1924 This ABI is especially applicable for humidity sensors1925 to heatup the device and get rid of any condensation1926 in some humidity environment1927 1928What: /sys/bus/iio/devices/iio:deviceX/in_ph_raw1929KernelVersion: 4.51930Contact: linux-iio@vger.kernel.org1931Description:1932 Raw (unscaled no offset etc.) pH reading of a substance as a negative1933 base-10 logarithm of hydrodium ions in a litre of water.1934 1935What: /sys/bus/iio/devices/iio:deviceX/mount_matrix1936What: /sys/bus/iio/devices/iio:deviceX/in_mount_matrix1937What: /sys/bus/iio/devices/iio:deviceX/out_mount_matrix1938What: /sys/bus/iio/devices/iio:deviceX/in_anglvel_mount_matrix1939What: /sys/bus/iio/devices/iio:deviceX/in_accel_mount_matrix1940KernelVersion: 4.61941Contact: linux-iio@vger.kernel.org1942Description:1943 Mounting matrix for IIO sensors. This is a rotation matrix which1944 informs userspace about sensor chip's placement relative to the1945 main hardware it is mounted on.1946 1947 Main hardware placement is defined according to the local1948 reference frame related to the physical quantity the sensor1949 measures.1950 1951 Given that the rotation matrix is defined in a board specific1952 way (platform data and / or device-tree), the main hardware1953 reference frame definition is left to the implementor's choice1954 (see below for a magnetometer example).1955 1956 Applications should apply this rotation matrix to samples so1957 that when main hardware reference frame is aligned onto local1958 reference frame, then sensor chip reference frame is also1959 perfectly aligned with it.1960 1961 Matrix is a 3x3 unitary matrix and typically looks like1962 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix1963 [1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware1964 are perfectly aligned with each other.1965 1966 For example, a mounting matrix for a magnetometer sensor informs1967 userspace about sensor chip's ORIENTATION relative to the main1968 hardware.1969 1970 More specifically, main hardware orientation is defined with1971 respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where :1972 1973 * Y is in the ground plane and positive towards magnetic North ;1974 * X is in the ground plane, perpendicular to the North axis and1975 positive towards the East ;1976 * Z is perpendicular to the ground plane and positive upwards.1977 1978 An implementor might consider that for a hand-held device, a1979 'natural' orientation would be 'front facing camera at the top'.1980 The main hardware reference frame could then be described as :1981 1982 * Y is in the plane of the screen and is positive towards the1983 top of the screen ;1984 * X is in the plane of the screen, perpendicular to Y axis, and1985 positive towards the right hand side of the screen ;1986 * Z is perpendicular to the screen plane and positive out of the1987 screen.1988 1989 Another example for a quadrotor UAV might be :1990 1991 * Y is in the plane of the propellers and positive towards the1992 front-view camera;1993 * X is in the plane of the propellers, perpendicular to Y axis,1994 and positive towards the starboard side of the UAV ;1995 * Z is perpendicular to propellers plane and positive upwards.1996 1997What: /sys/bus/iio/devices/iio:deviceX/in_electricalconductivity_raw1998KernelVersion: 4.81999Contact: linux-iio@vger.kernel.org2000Description:2001 Raw (unscaled no offset etc.) electric conductivity reading.2002 Units after application of scale and offset are siemens per2003 meter.2004 2005What: /sys/bus/iio/devices/iio:deviceX/in_countY_raw2006KernelVersion: 4.102007Contact: linux-iio@vger.kernel.org2008Description:2009 This interface is deprecated; please use the Counter subsystem.2010 2011 Raw counter device counts from channel Y. For quadrature2012 counters, multiplication by an available [Y]_scale results in2013 the counts of a single quadrature signal phase from channel Y.2014 2015What: /sys/bus/iio/devices/iio:deviceX/in_indexY_raw2016KernelVersion: 4.102017Contact: linux-iio@vger.kernel.org2018Description:2019 This interface is deprecated; please use the Counter subsystem.2020 2021 Raw counter device index value from channel Y. This attribute2022 provides an absolute positional reference (e.g. a pulse once per2023 revolution) which may be used to home positional systems as2024 required.2025 2026What: /sys/bus/iio/devices/iio:deviceX/in_count_count_direction_available2027KernelVersion: 4.122028Contact: linux-iio@vger.kernel.org2029Description:2030 This interface is deprecated; please use the Counter subsystem.2031 2032 A list of possible counting directions which are:2033 2034 - "up" : counter device is increasing.2035 - "down": counter device is decreasing.2036 2037What: /sys/bus/iio/devices/iio:deviceX/in_countY_count_direction2038KernelVersion: 4.122039Contact: linux-iio@vger.kernel.org2040Description:2041 This interface is deprecated; please use the Counter subsystem.2042 2043 Raw counter device counters direction for channel Y.2044 2045What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_label2046What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_label2047KernelVersion: 5.82048Contact: linux-iio@vger.kernel.org2049Description:2050 Optional symbolic label to a device channel.2051 If a label is defined for this channel add that to the channel2052 specific attributes. This is useful for userspace to be able to2053 better identify an individual channel.2054 2055What: /sys/bus/iio/devices/iio:deviceX/in_phaseY_raw2056KernelVersion: 4.182057Contact: linux-iio@vger.kernel.org2058Description:2059 Raw (unscaled) phase difference reading from channel Y.2060 Units after application of scale and offset are radians.2061 2062What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm1_input2063What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm1_input2064What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm2p5_input2065What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm2p5_input2066What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm4_input2067What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm4_input2068What: /sys/bus/iio/devices/iio:deviceX/in_massconcentration_pm10_input2069What: /sys/bus/iio/devices/iio:deviceX/in_massconcentrationY_pm10_input2070KernelVersion: 4.222071Contact: linux-iio@vger.kernel.org2072Description:2073 Mass concentration reading of particulate matter in ug / m3.2074 pmX consists of particles with aerodynamic diameter less or2075 equal to X micrometers.2076 2077What: /sys/bus/iio/devices/iio:deviceX/events/in_illuminance_period_available2078Date: November 20192079KernelVersion: 5.42080Contact: linux-iio@vger.kernel.org2081Description:2082 List of valid periods (in seconds) for which the light intensity2083 must be above the threshold level before interrupt is asserted.2084 2085What: /sys/bus/iio/devices/iio:deviceX/in_filter_notch_center_frequency2086KernelVersion: 5.52087Contact: linux-iio@vger.kernel.org2088Description:2089 Center frequency in Hz for a notch filter. Used i.e. for line2090 noise suppression.2091 2092What: /sys/bus/iio/devices/iio:deviceX/in_temp_thermocouple_type2093KernelVersion: 5.52094Contact: linux-iio@vger.kernel.org2095Description:2096 One of the following thermocouple types: B, E, J, K, N, R, S, T.2097 2098What: /sys/bus/iio/devices/iio:deviceX/in_temp_object_calibambient2099What: /sys/bus/iio/devices/iio:deviceX/in_tempX_object_calibambient2100KernelVersion: 5.102101Contact: linux-iio@vger.kernel.org2102Description:2103 Calibrated ambient temperature for object temperature2104 calculation in milli degrees Celsius.2105 2106What: /sys/bus/iio/devices/iio:deviceX/in_intensity_x_raw2107What: /sys/bus/iio/devices/iio:deviceX/in_intensity_y_raw2108What: /sys/bus/iio/devices/iio:deviceX/in_intensity_z_raw2109KernelVersion: 5.102110Contact: linux-iio@vger.kernel.org2111Description:2112 Unscaled light intensity according to CIE 1931/DIN 5033 color space.2113 Units after application of scale are nano nanowatts per square meter.2114 2115What: /sys/bus/iio/devices/iio:deviceX/in_anglY_label2116KernelVersion: 5.122117Contact: linux-iio@vger.kernel.org2118Description:2119 Optional symbolic label for channel Y.2120 For Intel hid hinge sensor, the label values are:2121 hinge, keyboard, screen. It means the three channels2122 each correspond respectively to hinge angle, keyboard angle,2123 and screen angle.2124 2125What: /sys/bus/iio/devices/iio:deviceX/in_illuminance_hysteresis_relative2126What: /sys/bus/iio/devices/iio:deviceX/in_intensity_hysteresis_relative2127KernelVersion: 5.122128Contact: linux-iio@vger.kernel.org2129Description:2130 Specify the percent for light sensor relative to the channel2131 absolute value that a data field should change before an event2132 is generated. Units are a percentage of the prior reading.2133 2134What: /sys/bus/iio/devices/iio:deviceX/calibration_auto_enable2135Date: June 20202136KernelVersion: 5.82137Contact: linux-iio@vger.kernel.org2138Description:2139 Some sensors have the ability to apply auto calibration at2140 runtime. For example, it may be necessary to compensate for2141 contaminant build-up in a measurement chamber or optical2142 element deterioration that would otherwise lead to sensor drift.2143 2144 Writing 1 or 0 to this attribute will respectively activate or2145 deactivate this auto calibration function.2146 2147 Upon reading, the current status is returned.2148 2149What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value2150Date: June 20202151KernelVersion: 5.82152Contact: linux-iio@vger.kernel.org2153Description:2154 Some sensors have the ability to apply a manual calibration using2155 a known measurement value, perhaps obtained from an external2156 reference device.2157 2158 Writing a value to this function will force such a calibration2159 change. For the scd30 the value should be from the range2160 [400 1 2000].2161 2162 Note for the scd30 that a valid value may only be obtained once2163 it is has been written. Until then any read back of this value2164 should be ignored. As for the scd4x an error will be returned2165 immediately if the manual calibration has failed.2166 2167What: /sys/bus/iio/devices/iio:deviceX/calibration_forced_value_available2168KernelVersion: 5.152169Contact: linux-iio@vger.kernel.org2170Description:2171 Available range for the forced calibration value, expressed as:2172 2173 - a range specified as "[min step max]"2174 2175What: /sys/bus/iio/devices/iio:deviceX/in_voltageX_sampling_frequency2176What: /sys/bus/iio/devices/iio:deviceX/in_powerY_sampling_frequency2177What: /sys/bus/iio/devices/iio:deviceX/in_currentZ_sampling_frequency2178KernelVersion: 5.202179Contact: linux-iio@vger.kernel.org2180Description:2181 Some devices have separate controls of sampling frequency for2182 individual channels. If multiple channels are enabled in a scan,2183 then the sampling_frequency of the scan may be computed from the2184 per channel sampling frequencies.2185 2186What: /sys/.../events/in_accel_gesture_singletap_en2187What: /sys/.../events/in_accel_gesture_doubletap_en2188KernelVersion: 6.12189Contact: linux-iio@vger.kernel.org2190Description:2191 Device generates an event on a single or double tap.2192 2193What: /sys/.../events/in_accel_gesture_singletap_value2194What: /sys/.../events/in_accel_gesture_doubletap_value2195KernelVersion: 6.12196Contact: linux-iio@vger.kernel.org2197Description:2198 Specifies the threshold value that the device is comparing2199 against to generate the tap gesture event. The lower2200 threshold value increases the sensitivity of tap detection.2201 Units and the exact meaning of value are device-specific.2202 2203What: /sys/.../events/in_accel_gesture_tap_value_available2204KernelVersion: 6.12205Contact: linux-iio@vger.kernel.org2206Description:2207 Lists all available threshold values which can be used to2208 modify the sensitivity of the tap detection.2209 2210What: /sys/.../events/in_accel_gesture_singletap_reset_timeout2211What: /sys/.../events/in_accel_gesture_doubletap_reset_timeout2212KernelVersion: 6.12213Contact: linux-iio@vger.kernel.org2214Description:2215 Specifies the timeout value in seconds for the tap detector2216 to not to look for another tap event after the event as2217 occurred. Basically the minimum quiet time between the two2218 single-tap's or two double-tap's.2219 2220What: /sys/.../events/in_accel_gesture_tap_reset_timeout_available2221KernelVersion: 6.12222Contact: linux-iio@vger.kernel.org2223Description:2224 Lists all available tap reset timeout values. Units in seconds.2225 2226What: /sys/.../events/in_accel_gesture_doubletap_tap2_min_delay2227KernelVersion: 6.12228Contact: linux-iio@vger.kernel.org2229Description:2230 Specifies the minimum quiet time in seconds between the two2231 taps of a double tap.2232 2233What: /sys/.../events/in_accel_gesture_doubletap_tap2_min_delay_available2234KernelVersion: 6.12235Contact: linux-iio@vger.kernel.org2236Description:2237 Lists all available delay values between two taps in the double2238 tap. Units in seconds.2239 2240What: /sys/.../events/in_accel_gesture_tap_maxtomin_time2241KernelVersion: 6.12242Contact: linux-iio@vger.kernel.org2243Description:2244 Specifies the maximum time difference allowed between upper2245 and lower peak of tap to consider it as the valid tap event.2246 Units in seconds.2247 2248What: /sys/.../events/in_accel_gesture_tap_maxtomin_time_available2249KernelVersion: 6.12250Contact: linux-iio@vger.kernel.org2251Description:2252 Lists all available time values between upper peak to lower2253 peak. Units in seconds.2254 2255What: /sys/bus/iio/devices/iio:deviceX/in_rot_yaw_raw2256What: /sys/bus/iio/devices/iio:deviceX/in_rot_pitch_raw2257What: /sys/bus/iio/devices/iio:deviceX/in_rot_roll_raw2258KernelVersion: 6.12259Contact: linux-iio@vger.kernel.org2260Description:2261 Raw (unscaled) euler angles readings. Units after2262 application of scale are deg.2263 2264What: /sys/bus/iio/devices/iio:deviceX/serialnumber2265KernelVersion: 6.12266Contact: linux-iio@vger.kernel.org2267Description:2268 An example format is 16-bytes, 2-digits-per-byte, HEX-string2269 representing the sensor unique ID number.2270 2271What: /sys/.../events/in_proximity_thresh_either_runningperiod2272KernelVersion: 6.62273Contact: linux-iio@vger.kernel.org2274Description:2275 A running period of time (in seconds) for which2276 in_proximity_thresh_either_runningcount amount of conditions2277 must occur before an event is generated. If direction is not2278 specified then this period applies to both directions.2279 2280What: /sys/.../events/in_proximity_thresh_either_runningcount2281KernelVersion: 6.62282Contact: linux-iio@vger.kernel.org2283Description:2284 Number of conditions that must occur, during a running2285 period, before an event is generated.2286 2287What: /sys/bus/iio/devices/iio:deviceX/in_colortemp_raw2288KernelVersion: 6.72289Contact: linux-iio@vger.kernel.org2290Description:2291 Represents light color temperature, which measures light color2292 temperature in Kelvin.2293 2294What: /sys/bus/iio/devices/iio:deviceX/in_chromaticity_x_raw2295What: /sys/bus/iio/devices/iio:deviceX/in_chromaticity_y_raw2296KernelVersion: 6.72297Contact: linux-iio@vger.kernel.org2298Description:2299 The x and y light color coordinate on the CIE 1931 chromaticity2300 diagram.2301 2302What: /sys/bus/iio/devices/iio:deviceX/events/in_altvoltageY_mag_either_label2303What: /sys/bus/iio/devices/iio:deviceX/events/in_altvoltageY_mag_rising_label2304What: /sys/bus/iio/devices/iio:deviceX/events/in_altvoltageY_thresh_falling_label2305What: /sys/bus/iio/devices/iio:deviceX/events/in_altvoltageY_thresh_rising_label2306What: /sys/bus/iio/devices/iio:deviceX/events/in_anglvelY_mag_rising_label2307What: /sys/bus/iio/devices/iio:deviceX/events/in_anglY_thresh_rising_label2308What: /sys/bus/iio/devices/iio:deviceX/events/in_phaseY_mag_rising_label2309KernelVersion: 6.72310Contact: linux-iio@vger.kernel.org2311Description:2312 Optional symbolic label to a device channel event.2313 If a label is defined for this event add that to the event2314 specific attributes. This is useful for userspace to be able to2315 better identify an individual event.2316 2317What: /sys/.../events/in_accel_gesture_tap_wait_timeout2318KernelVersion: 6.72319Contact: linux-iio@vger.kernel.org2320Description:2321 Enable tap gesture confirmation with timeout.2322 2323What: /sys/.../events/in_accel_gesture_tap_wait_dur2324KernelVersion: 6.72325Contact: linux-iio@vger.kernel.org2326Description:2327 Timeout value in seconds for tap gesture confirmation.2328 2329What: /sys/.../events/in_accel_gesture_tap_wait_dur_available2330KernelVersion: 6.72331Contact: linux-iio@vger.kernel.org2332Description:2333 List of available timeout value for tap gesture confirmation.2334 2335What: /sys/.../iio:deviceX/in_shunt_resistor2336What: /sys/.../iio:deviceX/in_current_shunt_resistor2337What: /sys/.../iio:deviceX/in_power_shunt_resistor2338KernelVersion: 6.102339Contact: linux-iio@vger.kernel.org2340Description:2341 The value of current sense resistor in Ohms.2342