From: Paul Fulghum <paulkf@microgate.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@digeo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
johannes@erdfelt.com,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: Test Patch: 2.5.69 Interrupt Latency
Date: 15 May 2003 09:12:37 -0500 [thread overview]
Message-ID: <1053007957.2025.23.camel@diemos> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0305141634070.626-100000@ida.rowland.org>
I have a question about the wakeup_hc() code in general:
when waking in response to a resume event,
the current code sets the USBCMD_FGR (force global resume)
and USBCMD_EGSM (enter global suspend mode) bits,
waits 20ms and clears both bits to start sending EOP signal.
According to the datasheet, the controller itself
(not software) sets the FGR bit on detection of
a resume event. 20ms after the USBSTS_RD indication,
software should clear both the FGR and EGSM bits.
My reading of this is that the line:
outw(USBCMD_FGR | USBCMD_EGSM, io_addr + USBCMD);
before the 20ms wait should not be necessary.
Am I reading this correctly?
Thanks,
Paul
--
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, http://www.microgate.com
next prev parent reply other threads:[~2003-05-15 14:01 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 16:12 2.5.69 Interrupt Latency Paul Fulghum
2003-05-07 19:41 ` Paul Fulghum
2003-05-07 22:28 ` Andrew Morton
2003-05-08 0:25 ` Paul Fulghum
2003-05-08 13:56 ` Paul Fulghum
2003-05-08 19:22 ` Andrew Morton
2003-05-08 19:35 ` Paul Fulghum
2003-05-08 23:20 ` Brian Gerst
2003-05-09 18:12 ` Paul Fulghum
2003-05-09 20:30 ` Paul Fulghum
2003-05-09 21:28 ` Andrew Morton
2003-05-12 13:57 ` Paul Fulghum
2003-05-12 14:06 ` Paul Fulghum
2003-05-12 16:24 ` Greg KH
2003-05-12 17:08 ` Paul Fulghum
2003-05-12 17:30 ` Greg KH
2003-05-12 17:49 ` Paul Fulghum
2003-05-12 18:01 ` Greg KH
2003-05-12 18:15 ` Paul Fulghum
2003-05-13 15:26 ` Alan Stern
2003-05-13 15:35 ` Paul Fulghum
2003-05-13 17:30 ` Greg KH
2003-05-13 13:01 ` Paul Fulghum
2003-05-13 18:09 ` Greg KH
2003-05-13 18:11 ` Greg KH
2003-05-13 21:35 ` Alan Stern
2003-05-13 21:48 ` Helge Hafting
2003-05-13 22:09 ` Alan Stern
2003-05-14 21:06 ` Paul Fulghum
2003-05-14 21:15 ` Johannes Erdfelt
2003-05-14 21:30 ` Greg KH
2003-05-14 21:45 ` Paul Fulghum
2003-05-13 20:17 ` Bill Davidsen
2003-05-13 22:39 ` Paul Fulghum
2003-05-14 20:52 ` Test Patch: " Alan Stern
2003-05-15 13:45 ` Paul Fulghum
2003-05-15 14:12 ` Paul Fulghum [this message]
2003-05-15 21:07 ` Alan Stern
2003-05-15 15:26 ` Paul Fulghum
2003-05-15 18:11 ` Alan Stern
2003-05-15 18:40 ` Paul Fulghum
2003-05-15 19:42 ` Paul Fulghum
2003-05-15 19:59 ` Paul Fulghum
2003-05-15 21:13 ` Alan Stern
2003-05-15 21:30 ` Paul Fulghum
2003-05-15 19:17 ` Paul Fulghum
2003-05-16 15:33 ` Alan Stern
2003-05-16 15:58 ` Paul Fulghum
2003-05-16 16:18 ` Paul Fulghum
2003-05-16 17:16 ` Alan Stern
2003-05-16 17:48 ` Paul Fulghum
2003-05-16 18:31 ` Paul Fulghum
2003-05-16 18:40 ` Alan Stern
2003-05-16 19:05 ` Paul Fulghum
2003-05-18 0:57 ` Andrew McGregor
2003-05-16 17:20 ` Alan Stern
2003-05-16 17:51 ` Paul Fulghum
2003-05-19 16:41 ` Alan Stern
2003-05-19 18:20 ` Paul Fulghum
2003-05-19 18:49 ` Alan Stern
2003-05-16 18:10 ` Paul Fulghum
2003-05-14 17:50 ` Paul Fulghum
2003-05-09 21:07 ` Andrew Morton
2003-05-09 21:28 ` Paul Fulghum
2003-05-08 14:47 ` Paul Fulghum
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=1053007957.2025.23.camel@diemos \
--to=paulkf@microgate.com \
--cc=akpm@digeo.com \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).