On Mon, Sep 26, 2011 at 08:20:11PM +0300, Ujfalusi, Peter wrote:
For the ramp code execution we should avoid any delay at all costs, since it can have audible side effects.
If you're that sensitive to latency does a workqueue offer sufficient guarantees?
In my past experience the system wq can cause latency, since we usually have slow devices on it (GPS, proximity sensor, magnetometer, etc). Reading from those usually takes considerable amount of time, and we can end up with delayed execution of our ramp code.
How long are these work items taking? I'm wondering if the other work items are taking sufficiently long to be actively disruptive if they should be isolated from other things rather than the other way around. Of course it could also be a large buildup of work...