187 lines · plain
1What: /sys/bus/iio/devices/iio:deviceX/buffer/length2KernelVersion: 2.6.353Contact: linux-iio@vger.kernel.org4Description:5 Number of scans contained by the buffer.6 7 Since Kernel 5.11, multiple buffers are supported.8 so, it is better to use, instead:9 10 /sys/bus/iio/devices/iio:deviceX/bufferY/length11 12What: /sys/bus/iio/devices/iio:deviceX/buffer/enable13KernelVersion: 2.6.3514Contact: linux-iio@vger.kernel.org15Description:16 Actually start the buffer capture up. Will start trigger17 if first device and appropriate.18 19 Since Kernel 5.11, multiple buffers are supported.20 so, it is better to use, instead:21 22 /sys/bus/iio/devices/iio:deviceX/bufferY/enable23 24What: /sys/bus/iio/devices/iio:deviceX/scan_elements25KernelVersion: 2.6.3726Contact: linux-iio@vger.kernel.org27Description:28 Directory containing interfaces for elements that will be29 captured for a single triggered sample set in the buffer.30 31 Since kernel 5.11 the scan_elements attributes are merged into32 the bufferY directory, to be configurable per buffer.33 34What: /sys/.../iio:deviceX/scan_elements/in_accel_x_en35What: /sys/.../iio:deviceX/scan_elements/in_accel_y_en36What: /sys/.../iio:deviceX/scan_elements/in_accel_z_en37What: /sys/.../iio:deviceX/scan_elements/in_anglvel_x_en38What: /sys/.../iio:deviceX/scan_elements/in_anglvel_y_en39What: /sys/.../iio:deviceX/scan_elements/in_anglvel_z_en40What: /sys/.../iio:deviceX/scan_elements/in_magn_x_en41What: /sys/.../iio:deviceX/scan_elements/in_magn_y_en42What: /sys/.../iio:deviceX/scan_elements/in_magn_z_en43What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_en44What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_en45What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_tilt_comp_en46What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_tilt_comp_en47What: /sys/.../iio:deviceX/scan_elements/in_timestamp_en48What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_en49What: /sys/.../iio:deviceX/scan_elements/in_voltageY_en50What: /sys/.../iio:deviceX/scan_elements/in_voltageY-voltageZ_en51What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_en52What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_en53What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_en54What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_en55What: /sys/.../iio:deviceX/scan_elements/in_incli_x_en56What: /sys/.../iio:deviceX/scan_elements/in_incli_y_en57What: /sys/.../iio:deviceX/scan_elements/in_pressureY_en58What: /sys/.../iio:deviceX/scan_elements/in_pressure_en59What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_en60What: /sys/.../iio:deviceX/scan_elements/in_proximity_en61KernelVersion: 2.6.3762Contact: linux-iio@vger.kernel.org63Description:64 Scan element control for triggered data capture.65 66 Since kernel 5.11 the scan_elements attributes are merged into67 the bufferY directory, to be configurable per buffer.68 69What: /sys/.../iio:deviceX/scan_elements/in_accel_type70What: /sys/.../iio:deviceX/scan_elements/in_anglvel_type71What: /sys/.../iio:deviceX/scan_elements/in_magn_type72What: /sys/.../iio:deviceX/scan_elements/in_incli_type73What: /sys/.../iio:deviceX/scan_elements/in_voltageY_type74What: /sys/.../iio:deviceX/scan_elements/in_voltage_type75What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_type76What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_type77What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_type78What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_type79What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_type80What: /sys/.../iio:deviceX/scan_elements/in_timestamp_type81What: /sys/.../iio:deviceX/scan_elements/in_pressureY_type82What: /sys/.../iio:deviceX/scan_elements/in_pressure_type83What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_type84What: /sys/.../iio:deviceX/scan_elements/in_proximity_type85KernelVersion: 2.6.3786Contact: linux-iio@vger.kernel.org87Description:88 Description of the scan element data storage within the buffer89 and hence the form in which it is read from user-space.90 Form is [be|le]:[s|u]bits/storagebits[>>shift].91 be or le specifies big or little endian. s or u specifies if92 signed (2's complement) or unsigned. bits is the number of bits93 of data and storagebits is the space (after padding) that it94 occupies in the buffer. shift if specified, is the shift that95 needs to be applied prior to masking out unused bits. Some96 devices put their data in the middle of the transferred elements97 with additional information on both sides. Note that some98 devices will have additional information in the unused bits99 so to get a clean value, the bits value must be used to mask100 the buffer output value appropriately. The storagebits value101 also specifies the data alignment. So s48/64>>2 will be a102 signed 48 bit integer stored in a 64 bit location aligned to103 a 64 bit boundary. To obtain the clean value, shift right 2104 and apply a mask to zero the top 16 bits of the result.105 For other storage combinations this attribute will be extended106 appropriately.107 108 Since kernel 5.11 the scan_elements attributes are merged into109 the bufferY directory, to be configurable per buffer.110 111What: /sys/.../iio:deviceX/scan_elements/in_voltageY_index112What: /sys/.../iio:deviceX/scan_elements/in_voltageY_supply_index113What: /sys/.../iio:deviceX/scan_elements/in_voltageY_i_index114What: /sys/.../iio:deviceX/scan_elements/in_voltageY_q_index115What: /sys/.../iio:deviceX/scan_elements/in_voltage_i_index116What: /sys/.../iio:deviceX/scan_elements/in_voltage_q_index117What: /sys/.../iio:deviceX/scan_elements/in_accel_x_index118What: /sys/.../iio:deviceX/scan_elements/in_accel_y_index119What: /sys/.../iio:deviceX/scan_elements/in_accel_z_index120What: /sys/.../iio:deviceX/scan_elements/in_anglvel_x_index121What: /sys/.../iio:deviceX/scan_elements/in_anglvel_y_index122What: /sys/.../iio:deviceX/scan_elements/in_anglvel_z_index123What: /sys/.../iio:deviceX/scan_elements/in_magn_x_index124What: /sys/.../iio:deviceX/scan_elements/in_magn_y_index125What: /sys/.../iio:deviceX/scan_elements/in_magn_z_index126What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_index127What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_index128What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_magnetic_tilt_comp_index129What: /sys/.../iio:deviceX/scan_elements/in_rot_from_north_true_tilt_comp_index130What: /sys/.../iio:deviceX/scan_elements/in_incli_x_index131What: /sys/.../iio:deviceX/scan_elements/in_incli_y_index132What: /sys/.../iio:deviceX/scan_elements/in_timestamp_index133What: /sys/.../iio:deviceX/scan_elements/in_pressureY_index134What: /sys/.../iio:deviceX/scan_elements/in_pressure_index135What: /sys/.../iio:deviceX/scan_elements/in_rot_quaternion_index136What: /sys/.../iio:deviceX/scan_elements/in_proximity_index137KernelVersion: 2.6.37138Description:139 A single positive integer specifying the position of this140 scan element in the buffer. Note these are not dependent on141 what is enabled and may not be contiguous. Thus for user-space142 to establish the full layout these must be used in conjunction143 with all _en attributes to establish which channels are present,144 and the relevant _type attributes to establish the data storage145 format.146 147 Since kernel 5.11 the scan_elements attributes are merged into148 the bufferY directory, to be configurable per buffer.149 150What: /sys/bus/iio/devices/iio:deviceX/buffer/watermark151KernelVersion: 4.2152Contact: linux-iio@vger.kernel.org153Description:154 A single positive integer specifying the maximum number of scan155 elements to wait for.156 157 Poll will block until the watermark is reached.158 159 Blocking read will wait until the minimum between the requested160 read amount or the low water mark is available.161 162 Non-blocking read will retrieve the available samples from the163 buffer even if there are less samples then watermark level. This164 allows the application to block on poll with a timeout and read165 the available samples after the timeout expires and thus have a166 maximum delay guarantee.167 168 Since Kernel 5.11, multiple buffers are supported.169 so, it is better to use, instead:170 171 /sys/bus/iio/devices/iio:deviceX/bufferY/watermark172 173What: /sys/bus/iio/devices/iio:deviceX/buffer/data_available174KernelVersion: 4.16175Contact: linux-iio@vger.kernel.org176Description:177 A read-only value indicating the bytes of data available in the178 buffer. In the case of an output buffer, this indicates the179 amount of empty space available to write data to. In the case of180 an input buffer, this indicates the amount of data available for181 reading.182 183 Since Kernel 5.11, multiple buffers are supported.184 so, it is better to use, instead:185 186 /sys/bus/iio/devices/iio:deviceX/bufferY/data_available187