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: 19 May 2003 13:20:14 -0500 [thread overview]
Message-ID: <1053368413.1995.9.camel@diemos> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0305191235470.655-100000@ida.rowland.org>
On Mon, 2003-05-19 at 11:41, Alan Stern wrote:
> The patch below incorporates your suggested subroutine. That alone wasn't
> enough to prevent the state from bouncing a few times when I powered my
> USB device on or off, so the debounce code is in there too. This patch
> behaves fine on my workstation, which has both ports connected. I'll try
> it later on my laptop, which only has one port.
>
> In the end, I decided it was easiest and safest to follow your "don't
> suspend if any ports are OC" scheme. We can try it the other way too if
> you want. What do you think would happen if you were to try to put your
> machine in an APM/ACPI "suspend" state?
>
> This is a cumulative patch, i.e., it applies to a virgin 2.5.69 source.
> Let me know how it works for you.
Alan,
the patch applied cleanly and worked for me
(prevented global suspension). Having the lengthy
waits outside of the ISR is a definate plus, and
the debounce makes sense.
My machine does not have APM/ACPI facilities so
I can't test the suspend. It is getting pretty
dated, but the economy dictates I live with it for
a while longer :-)
Does you laptop use the PIIX4? If it does and uses only
one port, I would be very interested to see if
one port is continuously reporting OC (hardwired).
Thanks for the patch,
Paul
--
Paul Fulghum, paulkf@microgate.com
Microgate Corporation, http://www.microgate.com
next prev parent reply other threads:[~2003-05-19 18:09 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
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 [this message]
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=1053368413.1995.9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.