[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200610081016.46677.dtor@insightbb.com>
Date: Sun, 8 Oct 2006 10:16:45 -0400
From: Dmitry Torokhov <dtor@...ightbb.com>
To: Oliver Neukum <oliver@...kum.org>
Cc: David Brownell <david-b@...bell.net>, Pavel Machek <pavel@....cz>,
USB development list <linux-usb-devel@...ts.sourceforge.net>,
Kernel development list <linux-kernel@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>
Subject: Re: [linux-usb-devel] error to be returned while suspended
On Sunday 08 October 2006 04:39, Oliver Neukum wrote:
> Am Sonntag, 8. Oktober 2006 09:20 schrieb David Brownell:
> > > If a device is always opened, as mice are, it will not be suspended.
> > > Yet they can be without any data to deliver forever.
> >
> > In 2.6.19-rc1 read Documentation/power/devices.txt about runtime
> > suspend states. Then think about how why mouse in a runtime suspend
> > state, with remote wakeup enabled, looks externally ** EXACTLY ** like
> > a mouse that's fully active ....
>
> I've done so. And I've read the HID spec. It just says that a mouse
> may support remote wakeup, not what should wake it up. A device
> that wakes only if a button is clicked is within spec.
>
And that's what some devices do. Apologies for a non-USB example, but
since we are talking about input devices and it would be nice to have
the rules consistent across all hardware interfaces I think it's OK...
Synaptics PS/2 touchpad can be put into a sleep mode where it only
reacts on button presses. While this behavior is reasonable for system-
wide suspend it would hardly work for autosuspend.
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists