On Wed, Aug 15, 2012 at 11:02:37AM +0200, Jiri Kosina wrote:
> On Tue, 14 Aug 2012, Russell King wrote:
>
> > > Actually, Henrik (added to CC) has been doing some latency improvements
> > > both for input core in general, and for HID devices as well lately. I
> > > still have his patchset in my
On Tue, 14 Aug 2012, Russell King wrote:
> > Actually, Henrik (added to CC) has been doing some latency improvements
> > both for input core in general, and for HID devices as well lately. I
> > still have his patchset in my to-review queue, as I have just came back
> > from offline vacation, b
Hi Russell,
> On Tue, Aug 14, 2012 at 12:54:00PM +0200, Jiri Kosina wrote:
> > Actually, Henrik (added to CC) has been doing some latency improvements
> > both for input core in general, and for HID devices as well lately. I
> > still have his patchset in my to-review queue, as I have just came
On Tuesday 14 August 2012 12:54:00 Jiri Kosina wrote:
> Offloading the processing to workqueue might actually work and make sense,
> but I will have to think a little bit more about all the consequences it'd
> have throughout the rest of the code.
How would alt-sysrq be handled?
Reagrds
On Tue, Aug 14, 2012 at 12:54:00PM +0200, Jiri Kosina wrote:
> Actually, Henrik (added to CC) has been doing some latency improvements
> both for input core in general, and for HID devices as well lately. I
> still have his patchset in my to-review queue, as I have just came back
> from offline
On Tue, 14 Aug 2012, Russell King wrote:
> I've been trying to track down where all the CPU time goes while
> processing USB interrupts for HID devices. At the moment, out of
> everything on the cubox, moving the mouse or even pressing a key
> on the keyboard just once is far more expensive than
I've been trying to track down where all the CPU time goes while
processing USB interrupts for HID devices. At the moment, out of
everything on the cubox, moving the mouse or even pressing a key
on the keyboard just once is far more expensive than processing an
interrupt for the network interface