kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: jingyun@cpu-os.ac.cn (jingyun at cpu-os.ac.cn)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB keyboard can NOT wakeup from S3( suspend to RAM )
Date: Tue, 5 Sep 2017 09:51:42 +0800	[thread overview]
Message-ID: <2017090509514217657816@cpu-os.ac.cn> (raw)
In-Reply-To: 20170831071615.GA21934@kroah.com

Hi,Greg

Thanks.
Yes, the suspending takes very litte time.
But the time ,which the suspending takes,  has something to do with the hardware.
Especially when you using an old mechanical  hard disk or something like that.


how do you know you are hitting the key "during" the suspend?
And after notice the problem, I do some hack to confirm that it have to be during the suspending process:
Within funcion  kernel/power/suspend.c (4.9 version kernel source)
static int suspend_enter(suspend_state_t state, bool *wakeup),
I added a line code
mdelay(5000); 
just before
error = platform_suspend_prepare_late(state);
to increase the time window.
Then rebuild&install the kernel.
After the new kernel runs up, now much easier (we got about 5 seconds more)  to reproduce the bug.


Thanks for your time.

Jim




 
From: Greg KH
Date: 2017-08-31 15:16
To: jingyun at cpu-os.ac.cn
CC: kernelnewbies
Subject: Re: Re: USB keyboard can NOT wakeup from S3( suspend to RAM )
On Thu, Aug 31, 2017 at 06:38:48AM +0800, jingyun at cpu-os.ac.cn wrote:
> Hi, Greg
> 
> Thanks for your time.
> First of all, if I do NOT hit the keyboard during the suspend.
> Then my keyboard CAN wake the system up from suspend.
> This has rule out that my system does NOT support USB wakeup. Right ?
 
I really do not know, sorry.  Given taht suspend to ram go so fast, how
do you know you are hitting the key "during" the suspend?  It's an
almost instantaneous process.
 
Check your bios settings about this, or, just don't touch the keyboard
until you really do want to wake it up :)
 
good luck!
 
greg k-h
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170905/0133868c/attachment.html 

  reply	other threads:[~2017-09-05  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 10:03 USB keyboard can NOT wakeup from S3( suspend to RAM ) jingyun at cpu-os.ac.cn
2017-08-30  6:09 ` Greg KH
2017-08-30  6:55   ` valdis.kletnieks at vt.edu
2017-08-30 22:38   ` jingyun at cpu-os.ac.cn
2017-08-31  7:16     ` Greg KH
2017-09-05  1:51       ` jingyun at cpu-os.ac.cn [this message]
2017-08-30  7:45 ` Andrey Skvortsov
2017-08-30 23:06   ` jingyun at cpu-os.ac.cn
2017-09-05  6:32     ` Martin Kepplinger
2017-09-05  2:20       ` jingyun at cpu-os.ac.cn

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=2017090509514217657816@cpu-os.ac.cn \
    --to=jingyun@cpu-os.ac.cn \
    --cc=kernelnewbies@lists.kernelnewbies.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).