From: Alan Stern <stern@rowland.harvard.edu>
To: "Lu, Baolu" <baolu.lu@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] usb: notify hcd when USB device suspend or resume
Date: Wed, 13 May 2015 10:14:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1505131013380.1674-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <5552B8AD.9020200@linux.intel.com>
On Wed, 13 May 2015, Lu, Baolu wrote:
> From software point of view, the extra time it takes to ask for cache
> operation can be measured in xhci_device_suspend(). I can measure
> the data later when I complete my tasks in hand. If that data is ignorable
> comparing to the suspend time, we can simply do it always.
Or do it whenever the hardware doesn't support FSC. That seems
reasonable.
Alan Stern
next prev parent reply other threads:[~2015-05-13 14:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 7:39 [PATCH v2 0/3] usb: notify hcd when USB device suspend or resume Lu Baolu
2015-05-06 7:40 ` [PATCH v2 1/3] " Lu Baolu
2015-05-06 14:35 ` Alan Stern
2015-05-07 0:27 ` Lu, Baolu
2015-05-07 14:34 ` Alan Stern
2015-05-08 1:14 ` Lu, Baolu
2015-05-08 14:21 ` Alan Stern
2015-05-09 0:42 ` Lu, Baolu
2015-05-11 14:25 ` Alan Stern
2015-05-12 2:05 ` Lu, Baolu
2015-05-12 15:54 ` Alan Stern
2015-05-13 2:36 ` Lu, Baolu
2015-05-13 14:14 ` Alan Stern [this message]
2015-05-08 7:55 ` Lu, Baolu
2015-05-06 7:40 ` [PATCH v2 2/3] usb: xhci: implement device_suspend/device_resume entries Lu Baolu
2015-05-06 14:30 ` Alan Stern
2015-05-07 0:30 ` Lu, Baolu
2015-05-06 7:40 ` [PATCH v2 3/3] usb: xhci: remove stop device and ring doorbell in hub control and bus suspend Lu Baolu
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=Pine.LNX.4.44L0.1505131013380.1674-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=baolu.lu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
/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).