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