From: Oliver Neukum <oliver@neukum.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: full usbhid autosuspend
Date: Fri, 4 Apr 2008 16:45:39 +0200 [thread overview]
Message-ID: <200804041645.40301.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804041637150.32130@jikos.suse.cz>
Am Freitag, 4. April 2008 16:38:18 schrieb Jiri Kosina:
> > > triggered it on my test system trivially by just attaching one PS2 and one
> > > USB keyboard to the system, fiddling a bit with leds on PS2 keyboard and
> > > then tried to perform remote-wakeup on the suspended USB keyboard.
> > That is you hit a key on the USB keyboard?
>
> Yes. Just letting the USB keyboard go auto-suspend, then fiddling with
> LEDs on PS2 keyboard and then hitting key on USB keyboard triggers it for
> me quite reliably (not 100% though, so you may have to retry).
I mean did you hit e.g. CAPS LOCK or any key that should have switched an
LED or just any other key?
Regards
Oliver
next prev parent reply other threads:[~2008-04-04 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 14:03 full usbhid autosuspend Oliver Neukum
[not found] ` <200804011603.05998.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-04-04 14:24 ` Jiri Kosina
[not found] ` <Pine.LNX.4.64.0804041437430.32130-YCXOAqNspd+N3ZZ/Hiejyg@public.gmane.org>
2008-04-04 14:28 ` Oliver Neukum
[not found] ` <200804041628.14793.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-04-04 14:38 ` Jiri Kosina
2008-04-04 14:45 ` Oliver Neukum [this message]
2008-04-04 15:11 ` Jiri Kosina
[not found] ` <Pine.LNX.4.64.0804041708100.32130-YCXOAqNspd+N3ZZ/Hiejyg@public.gmane.org>
2008-04-04 15:08 ` Oliver Neukum
[not found] ` <200804041708.48296.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-04-22 0:07 ` Jiri Kosina
2008-04-22 8:16 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804041645.40301.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).