Lines Matching +full:fifo +full:- +full:watermark +full:- +full:aligned
3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
38 Contact: linux-iio@vger.kernel.org
44 The contents of the label are free-form, but there are some
51 * "proximity-wifi"
52 * "proximity-lte"
53 * "proximity-wifi-lte"
54 * "proximity-wifi-left"
55 * "proximity-wifi-right"
60 The "-left" and "-right" labels are for devices with multiple
66 * "proximity-palmrest" indicates proximity to the keyboard's palmrest
67 * "proximity-palmrest-left" indicates proximity to the left part of the palmrest
68 * "proximity-palmrest-right" indicates proximity to the right part of the palmrest
69 * "proximity-lap" indicates the device is being used on someone's lap
71 Note "proximity-lap" is special in that its value may be
75 For accelerometers used in 2-in-1s with 360° (yoga-style) hinges,
79 * "accel-base"
80 * "accel-display"
84 Contact: linux-iio@vger.kernel.org
94 Contact: linux-iio@vger.kernel.org
111 Contact: linux-iio@vger.kernel.org
116 - a small discrete set of values like "0 2 4 6 8"
117 - a range with minimum, step and maximum frequencies like
122 Contact: linux-iio@vger.kernel.org
129 Contact: linux-iio@vger.kernel.org
138 Contact: linux-iio@vger.kernel.org
148 channels refer to the same signal. The 'i' channel contains the in-phase
152 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
154 Contact: linux-iio@vger.kernel.org
157 channel Y - channel Z where these channel numbers apply to the
166 Contact: linux-iio@vger.kernel.org
177 Contact: linux-iio@vger.kernel.org
186 Contact: linux-iio@vger.kernel.org
191 What: /sys/.../iio:deviceX/in_capacitanceY-in_capacitanceZ_raw
193 Contact: linux-iio@vger.kernel.org
196 channel Y - channel Z where these channel numbers apply to the
209 Contact: linux-iio@vger.kernel.org
215 between ambient (reference) and distant temperature for contact-
221 Contact: linux-iio@vger.kernel.org
229 Contact: linux-iio@vger.kernel.org
240 Contact: linux-iio@vger.kernel.org
249 Contact: linux-iio@vger.kernel.org
257 Contact: linux-iio@vger.kernel.org
270 Contact: linux-iio@vger.kernel.org
281 Contact: linux-iio@vger.kernel.org
291 Contact: linux-iio@vger.kernel.org
301 Contact: linux-iio@vger.kernel.org
309 Contact: linux-iio@vger.kernel.org
317 Contact: linux-iio@vger.kernel.org
325 Contact: linux-iio@vger.kernel.org
331 Contact: linux-iio@vger.kernel.org
338 Contact: linux-iio@vger.kernel.org
344 Contact: linux-iio@vger.kernel.org
376 Contact: linux-iio@vger.kernel.org
399 What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
433 Contact: linux-iio@vger.kernel.org
454 Contact: linux-iio@vger.kernel.org
465 Contact: linux-iio@vger.kernel.org
469 - a small discrete set of values like "0 2 4 6 8"
470 - a range specified as "[min step max]"
491 Contact: linux-iio@vger.kernel.org
502 Contact: linux-iio@vger.kernel.org
513 Contact: linux-iio@vger.kernel.org
522 Contact: linux-iio@vger.kernel.org
530 Contact: linux-iio@vger.kernel.org
542 What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
549 Contact: linux-iio@vger.kernel.org
561 Contact: linux-iio@vger.kernel.org
568 Contact: linux-iio@vger.kernel.org
577 Contact: linux-iio@vger.kernel.org
587 Contact: linux-iio@vger.kernel.org
596 Contact: linux-iio@vger.kernel.org
608 Contact: linux-iio@vger.kernel.org
620 Contact: linux-iio@vger.kernel.org
643 Contact: linux-iio@vger.kernel.org
653 Contact: linux-iio@vger.kernel.org
663 Contact: linux-iio@vger.kernel.org
690 Contact: linux-iio@vger.kernel.org
711 Contact: linux-iio@vger.kernel.org
714 to user-space.
752 Contact: linux-iio@vger.kernel.org
806 Contact: linux-iio@vger.kernel.org
831 Contact: linux-iio@vger.kernel.org
843 Contact: linux-iio@vger.kernel.org
849 signal is allowed to remain out-of-range before a reset
899 Contact: linux-iio@vger.kernel.org
925 Contact: linux-iio@vger.kernel.org
983 Contact: linux-iio@vger.kernel.org
1033 Contact: linux-iio@vger.kernel.org
1123 Contact: linux-iio@vger.kernel.org
1133 Contact: linux-iio@vger.kernel.org
1143 Contact: linux-iio@vger.kernel.org
1158 Contact: linux-iio@vger.kernel.org
1172 Contact: linux-iio@vger.kernel.org
1198 Contact: linux-iio@vger.kernel.org
1209 Contact: linux-iio@vger.kernel.org
1217 Contact: linux-iio@vger.kernel.org
1226 Contact: linux-iio@vger.kernel.org
1236 Contact: linux-iio@vger.kernel.org
1243 Contact: linux-iio@vger.kernel.org
1249 Contact: linux-iio@vger.kernel.org
1256 Contact: linux-iio@vger.kernel.org
1280 What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en
1292 Contact: linux-iio@vger.kernel.org
1313 Contact: linux-iio@vger.kernel.org
1316 and hence the form in which it is read from user-space.
1329 signed 48 bit integer stored in a 64 bit location aligned to
1337 Contact: linux-iio@vger.kernel.org
1369 Contact: linux-iio@vger.kernel.org
1373 what is enabled and may not be contiguous. Thus for user-space
1384 Contact: linux-iio@vger.kernel.org
1391 Contact: linux-iio@vger.kernel.org
1398 Contact: linux-iio@vger.kernel.org
1409 Contact: linux-iio@vger.kernel.org
1418 Contact: linux-iio@vger.kernel.org
1426 Contact: linux-iio@vger.kernel.org
1429 on-chip EEPROM. After power-up or chip reset the device will
1436 Contact: linux-iio@vger.kernel.org
1455 Contact: linux-iio@vger.kernel.org
1466 Contact: linux-iio@vger.kernel.org
1468 Unit-less light intensity. Modifiers both and ir indicate
1477 Contact: linux-iio@vger.kernel.org
1491 Contact: linux-iio@vger.kernel.org
1499 Contact: linux-iio@vger.kernel.org
1505 Contact: linux-iio@vger.kernel.org
1517 Contact: linux-iio@vger.kernel.org
1526 Contact: linux-iio@vger.kernel.org
1534 channels refer to the same signal. The 'i' channel contains the in-phase
1543 Contact: linux-iio@vger.kernel.org
1552 Contact: linux-iio@vger.kernel.org
1560 Contact: linux-iio@vger.kernel.org
1568 Contact: linux-iio@vger.kernel.org
1576 Contact: linux-iio@vger.kernel.org
1581 What: /sys/bus/iio/devices/iio:deviceX/bufferY/watermark
1583 Contact: linux-iio@vger.kernel.org
1588 Poll will block until the watermark is reached.
1593 Non-blocking read will retrieve the available samples from the
1594 buffer even if there are less samples then watermark level. This
1601 Contact: linux-iio@vger.kernel.org
1603 A read-only value indicating the bytes of data available in the
1611 Contact: linux-iio@vger.kernel.org
1613 A read-only boolean value that indicates if the hardware fifo is
1615 hardware fifo this entry is not present.
1616 The hardware fifo is enabled when the buffer is enabled if the
1617 current hardware fifo watermark level is set and other current
1619 data differently that the hardware fifo does then hardware fifo
1622 If the hardware fifo is enabled and the level of the hardware
1623 fifo reaches the hardware fifo watermark level the device will
1624 flush its hardware fifo to the device buffer. Doing a non
1628 When the hardware fifo is enabled there is no need to use a
1629 trigger to use buffer mode since the watermark settings
1630 guarantees that the hardware fifo is flushed to the device
1635 Contact: linux-iio@vger.kernel.org
1639 sleep, while the sensor is storing samples in its internal fifo.
1646 Contact: linux-iio@vger.kernel.org
1648 Read-only entry that contains a single integer specifying the
1649 current watermark level for the hardware fifo. If the device
1650 does not have a hardware fifo this entry is not present.
1651 The watermark level for the hardware fifo is set by the driver
1652 based on the value set by the user in buffer/watermark but
1654 buffers are limited to 32-64 samples, some hardware buffers
1656 means that the hardware watermark is unset.
1660 Contact: linux-iio@vger.kernel.org
1662 A single positive integer specifying the minimum watermark level
1663 for the hardware fifo of this device. If the device does not
1664 have a hardware fifo this entry is not present.
1666 If the user sets buffer/watermark to a value less than this one,
1667 then the hardware watermark will remain unset.
1671 Contact: linux-iio@vger.kernel.org
1673 A single positive integer specifying the maximum watermark level
1674 for the hardware fifo of this device. If the device does not
1675 have a hardware fifo this entry is not present.
1677 If the user sets buffer/watermark to a value greater than this
1678 one, then the hardware watermark will be capped at this value.
1682 Contact: linux-iio@vger.kernel.org
1684 A list of positive integers specifying the available watermark
1685 levels for the hardware fifo. This entry is optional and if it
1689 If the user sets buffer/watermark to a value greater than
1692 hardware fifo watermark level.
1699 Contact: linux-iio@vger.kernel.org
1709 Contact: linux-iio@vger.kernel.org
1730 Contact: linux-iio@vger.kernel.org
1740 Contact: linux-iio@vger.kernel.org
1747 Contact: linux-iio@vger.kernel.org
1758 Contact: linux-iio@vger.kernel.org
1761 base-10 logarithm of hydrodium ions in a litre of water.
1769 Contact: linux-iio@vger.kernel.org
1780 way (platform data and / or device-tree), the main hardware
1785 that when main hardware reference frame is aligned onto local
1787 perfectly aligned with it.
1790 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
1792 are perfectly aligned with each other.
1806 An implementor might consider that for a hand-held device, a
1820 front-view camera;
1827 Contact: linux-iio@vger.kernel.org
1834 Contact: linux-iio@vger.kernel.org
1844 Contact: linux-iio@vger.kernel.org
1855 Contact: linux-iio@vger.kernel.org
1861 - "up" : counter device is increasing.
1862 - "down": counter device is decreasing.
1866 Contact: linux-iio@vger.kernel.org
1875 Contact: linux-iio@vger.kernel.org
1884 Contact: linux-iio@vger.kernel.org
1898 Contact: linux-iio@vger.kernel.org
1907 Contact: linux-iio@vger.kernel.org
1914 Contact: linux-iio@vger.kernel.org
1921 Contact: linux-iio@vger.kernel.org
1928 Contact: linux-iio@vger.kernel.org
1937 Contact: linux-iio@vger.kernel.org
1944 Contact: linux-iio@vger.kernel.org
1955 Contact: linux-iio@vger.kernel.org