From: Paul Fulghum <paulkf@microgate.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
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 14:42:22 -0500 [thread overview]
Message-ID: <1053027740.2095.44.camel@diemos> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0305151355290.1139-100000@ida.rowland.org>
On Thu, 2003-05-15 at 13:11, Alan Stern wrote:
> Maybe they are an Intel-specific addition? Or perhaps a more
> recent version of the spec has more information -- the one I've got is 1.1
> (March 1996).
I can't find any later documents.
> Can you suggest a good way of detecting whether or not a controller is
> part of a PIIX4 chipset, to indicate whether or not the OC bits are valid?
I don't see a generic way to determine the validity of these bits.
I think the PCI ID is the only way:
Vendor ID 8086
Device ID 7112
The erratum is only for the PIIX4, and it is
triggered only when the OC inputs are active,
so limiting the check to that device should
be OK.
Probably the least intrusive thing to do
is to disable suspending the uhci controller
if it is a PIIX4 *and* either port has an
over current condition. This will catch the case
of a functional USB controller that has one
or more real over current conditions and the
case of a deliberately disabled (by hardwiring
the OC inputs) controller. The erratum will
pop up in both cases causing suspend<->wake
thrashing.
--
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, http://www.microgate.com
next prev parent reply other threads:[~2003-05-15 19:31 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
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 [this message]
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=1053027740.2095.44.camel@diemos \
--to=paulkf@microgate.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