Lines Matching full:mode

102  * Interaction with suspend mode
105  * SoC to go into suspend mode. It is the responsibility of applications
107  * events while the screen is off. While in suspend mode, and unless
108  * otherwise noted (batch mode, sensor particularities, ...), enabled sensors'
112  * suspend mode -- it's just that the data it returns are lost. As soon as
113  * the SoC gets out of suspend mode, operations resume as usual. Of course,
114  * in practice sensors shall be disabled while in suspend mode to
115  * save power, unless batch mode is active, in which case they must
117  * learn how suspend interacts with batch mode).
119  * In batch mode, and only when the flag SENSORS_BATCH_WAKE_UPON_FIFO_FULL is
172  * each sensor type has one and only one trigger mode associated to it.
194  * trigger-mode: n/a
227  * trigger-mode: continuous
262  * trigger-mode: continuous
280  * trigger-mode: continuous
320  * trigger-mode: continuous
340  * trigger-mode: on-change
349  * trigger-mode: continuous
361  * trigger-mode: on-change
373  * trigger-mode: continuous
386  * trigger-mode: continuous
403  * trigger-mode: continuous
452  * trigger-mode: on-change
462  * trigger-mode: on-change
471  * trigger-mode: continuous
510  * trigger-mode: continuous
534  * trigger-mode: continuous
577  * trigger-mode: one-shot
608  *  If a particular hardware cannot support this mode of operation then this
613  *  SoC in suspend mode when the device is at rest.
628  * trigger-mode: special
653  * trigger-mode: on-change
671  *  Unlike other sensors, while in suspend mode this sensor must stay active,
677  *    go into suspend mode, we don't want to be woken up, regardless of the
698  *  SoC in suspend mode when the device is at rest.
705  * trigger-mode: continuous
951     /* this value depends on the trigger mode:
960     /* number of events reserved for this sensor in the batch mode FIFO.
1033     int mode;  member