Bug#677472: [3.1->3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
- To: Alan Stern <stern@rowland.harvard.edu>
- Cc: Frank Schäfer <fschaefer.oss@googlemail.com>, Lan Tianyu <lantianyu1986@gmail.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Octavio Alvarez <alvarezp@alvarezp.com>, 677472@bugs.debian.org, Ben Hutchings <ben@decadent.org.uk>, linux-usb@vger.kernel.org, Frank Schäfer <schaefer.frank@gmx.net>
- Subject: Bug#677472: [3.1->3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
- From: Lan Tianyu <tianyu.lan@intel.com>
- Date: Thu, 13 Dec 2012 09:38:23 +0800
- Message-id: <[🔎] 50C9318F.5010105@intel.com>
- Reply-to: Lan Tianyu <tianyu.lan@intel.com>, 677472@bugs.debian.org
- In-reply-to: <[🔎] Pine.LNX.4.44L0.1212121047020.1488-100000@iolanthe.rowland.org>
- References: <[🔎] Pine.LNX.4.44L0.1212121047020.1488-100000@iolanthe.rowland.org>
On 2012年12月12日 23:50, Alan Stern wrote:
> On Wed, 12 Dec 2012, Lan Tianyu wrote:
>
>> Hi Alan:
>> About your question of "Does the device send a remote wakeup request
>> even when it is disabled for remote wakeup?", I am not very clear.
>> Default, device remote wakeup is disabled and if we disable device's
>> remote wakeup via sysfs, the device's remote wakeup feature will not be
>> set during being suspended. So normally, it should not send out remote
>> wakeup signal but if it still sent out, this means it's a buggy device,
>> right?
>
> Right.
>
>> Moreover, this test is hard to do during s3 since system suspend, we
>> can't see any log. So this should be done in the runtime. I think it's
>> easy to do this test on mouse or keyboard device.
>
> Yes, that should work. But Frank says that the same mouse and keyboard
> do not cause other machines to wake up, so the devices are probably
> working correctly.
>
Yeah.
> Do you have one of these machines to test?
>
Unfortunately, I don't have such machine.
> Alan Stern
>
--
Best regards
Tianyu Lan
Reply to: