Re: [PATCH] input: Fix USB autosuspend on bcm5974

["Henrik Rydberg" <rydberg@euromail.se>]

On Fri, Oct 07, 2011 at 05:27:56PM +0100, Matthew Garrett wrote:
> On Fri, Oct 07, 2011 at 09:20:27AM -0700, Dmitry Torokhov wrote:
> > On Fri, Oct 07, 2011 at 01:36:53PM +0100, Matthew Garrett wrote:
> > > On Fri, Oct 07, 2011 at 08:37:46AM +0200, Oliver Neukum wrote:
> > > 
> > > > Please also note that for a device to generate wakeup events the kernel has to
> > > > enable them which drivers have to request, like the usbhid driver does.
> > > > If you do this you better have a test device, because I found that most
> > > > generic mice generate wakeup events only if you press a button, not move
> > > > the mouse. We are simply not equipped in our API to use that capability.
> > > 
> > > This hardware generates wakeups events on touch.
> > 
> > Is it true for all generations that the driver supports?
> 
> As far as I can tell.

And yet, there is a complication, since the keyboard and mouse
interfaces are both present on the same device. I just ran a small
test, on an MBA3,1. While it is true that the trackpad generates
wakeup events on touch, it enters a loop of suspend/resume, presumably
due to the keyboard. Moreover, the trackpad emits some strange packets
which leave a (large) message trail.

Henrik