From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200
Date: Thu, 24 Jun 2010 18:40:32 +0300 [thread overview]
Message-ID: <4C237C70.70409@pardus.org.tr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1006241004430.1654-100000@iolanthe.rowland.org>
Alan Stern wrote:
>
> The content of the power/wakeup file depends on two values: the
> can_wakeup flag and the should_wakeup flag. If can_wakeup is false
> then the file will be empty; otherwise it will contain "disabled" or
> "enabled" according to the value of should_wakeup.
>
> Now, device_init_wakeup() sets both flags whereas
> device_set_wakeup_capable() affects only the can_wakeup flag. After
> this change is made there should be nothing in the kernel that turns on
> the should_wakeup flag, and consequently remote wakeup should remain
> disabled.
>
> You can check this by grepping for occurrences of "should_wakeup" or
> "dev_set_wakeup_enable" (which affects the should_wakeup flag).
>
> Alan Stern
>
Okay the patch fixed the issue for the users. Thanks again for all your
helps,
Regards,
Ozan Caglayan
prev parent reply other threads:[~2010-06-24 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 7:22 [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200 Ozan Çağlayan
2010-06-21 10:31 ` Ozan Çağlayan
2010-06-21 16:25 ` Alan Stern
2010-06-22 9:09 ` Ozan Çağlayan
2010-06-22 14:49 ` Alan Stern
2010-06-22 16:53 ` Ozan Çağlayan
2010-06-22 17:47 ` Alan Stern
2010-06-24 7:01 ` Ozan Çağlayan
2010-06-24 14:10 ` Alan Stern
2010-06-24 15:40 ` Ozan Çağlayan [this message]
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=4C237C70.70409@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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