From: Hayes Wang <hayeswang@realtek.com>
To: Oliver Neukum <oneukum@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"peter@lekensteyn.nl" <peter@lekensteyn.nl>
Subject: RE: [PATCH v2] r8152: fix lockup when runtime PM is enabled
Date: Wed, 23 Dec 2015 09:20:25 +0000 [thread overview]
Message-ID: <0835B3720019904CB8F7AA43166CEEB2F9547E@RTITMBSV03.realtek.com.tw> (raw)
In-Reply-To: <1450858813.6437.2.camel@suse.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 944 bytes --]
Oliver Neukum [mailto:oneukum@suse.de]
> Sent: Wednesday, December 23, 2015 4:20 PM
[...]
> No, step (2) does not exist. Calls to suspend() and [reset_]resume()
> always balance. Usually a driver shouldn't care about system suspend.
> The way the driver is currently coded will also fail for Port-Power Off.
It is different with Windows. The Windows would resume the device before
system suspend, if the system suspend follows the autosuspend.
Would this be a problem? After system suspend, the device may wake up
the system when receiving any packet, not only magic packet. The wake
events are different for system suspend and autosuspend. However, I
couldn't change the wake event, because the autosuspend occurs first,
and the suspend() is only called once.
Best Regards,
Hayes
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-12-23 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 11:17 [PATCH v2] r8152: fix lockup when runtime PM is enabled Peter Wu
2015-12-08 12:39 ` Hayes Wang
2015-12-08 14:33 ` Peter Wu
2015-12-15 11:32 ` Oliver Neukum
2015-12-22 9:48 ` Hayes Wang
2015-12-22 11:01 ` Oliver Neukum
2015-12-23 3:31 ` Hayes Wang
2015-12-23 8:20 ` Oliver Neukum
2015-12-23 9:20 ` Hayes Wang [this message]
2015-12-23 10:45 ` Oliver Neukum
2015-12-23 11:15 ` Hayes Wang
2015-12-24 1:32 ` Alan Stern
2015-12-24 7:14 ` Oliver Neukum
2015-12-24 15:14 ` Alan Stern
2015-12-24 15:47 ` Oliver Neukum
2015-12-24 16:08 ` Alan Stern
2015-12-09 3:48 ` David Miller
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=0835B3720019904CB8F7AA43166CEEB2F9547E@RTITMBSV03.realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=peter@lekensteyn.nl \
/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).