Lines Matching full:fifo
28 <p>?Batching? refers to storing sensor events in a hardware FIFO before reporting
35 <p>Batching happens when a sensor possesses a hardware FIFO
57 <li> or when the sensor doesn?t have a hardware FIFO (<code>sensor_t.fifoMaxEventCount =
68 sensors</a> must be stored into a wake-up FIFO. There can be one wake-up FIFO
69 per sensor, or, more commonly, one big shared wake-up FIFO where events from all wake-up
71 wake-up sensors having a dedicated FIFO, and the rest of the wake-up sensors
78 interleaved into the same FIFO. Wake-up events go in wake-up FIFOs, and
80 <p>For the wake-up FIFO, the ?one big shared FIFO? design provides the best power
81 benefits. For the non-wake-up FIFO, there is no preference between the ?one big
82 shared FIFO? and ?several small reserved FIFOs?. See <a
83 href="#fifo_allocation_priority">FIFO allocation priority</a> for suggestions
84 on how to dimension each FIFO.</p>
87 temporarily in their FIFO, as long as they are not delayed by more than
93 <p>If several sensors share the same FIFO and the <code>max_report_latency</code> of one of
94 them elapses, all events from the FIFO are reported, even if the
105 gyroscope do not share the same FIFO.</p>
115 <p>When a non-wake-up FIFO fills up, it must wrap around and behave like a
118 <p>When a wake-up FIFO fills up, or when the <code>max_report_latency</code> of one of the
133 entirely come out of suspend and start flushing the FIFO. Enough head room must
134 be allocated in the FIFO to allow the device to entirely come out of suspend
135 without the wake-up FIFO overflowing. No events shall be lost, and the
142 FIFO with other sensors. The last event generated by each on-change sensor must
143 always be saved outside of the shared FIFO so it can never be overwritten by
144 other events. When the SoC wakes up, after all events from the FIFO have been
149 non-wake-up accelerometer (continuous), both sharing the same FIFO </li>
155 accumulating in the FIFO, eventually overwriting every step_count event in the
156 shared FIFO </li>
157 <li> SoC wakes up and all events from the FIFO are sent to the application </li>
161 <p>By saving the last step counter event outside of the FIFO, the HAL can report
175 <h2 id="fifo_allocation_priority">FIFO allocation priority</h2>
176 <p>On platforms in which hardware FIFO size is limited, the system designers may
177 have to choose how much FIFO to reserve for each sensor. To help with this
219 Only to consider if FIFO space is not an issue.</p>
