mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Colin Leroy <colin@colino.net>,
	linux-kernel@vger.kernel.org, debian-powerpc@lists.debian.org
Subject: Re: [linux-usb-devel] USB glitches after suspend on ppc
Date: Tue, 5 Apr 2005 13:53:36 -0700	[thread overview]
Message-ID: <200504051353.36788.david-b@pacbell.net> (raw)
In-Reply-To: <20050405204449.5ab0cdea@jack.colino.net>

On Tuesday 05 April 2005 11:44 am, Colin Leroy wrote:
> Hi,
> 
> There are known issues with USB after suspend/resume (D3 hot) on
> powerpc.

Also known fixes to some of them, which haven't yet been merged.
I'll repost these as followups to this message, to linux-usb-devel
and CC Colin.  They're in the 2.6.12-rc2-mm1 patchset.

To my understanding, such issues have been around for some time
now, although recent kernels have tossed monkey wrenches into
several other cases that previously worked just fine.  (Ergo those
nyet-merged patches...)


> For example, plugging or unplugging devices during sleep 
> results in oopses at resume; and one time out of two, the USB ports are
> unpowered on resume (because the registers think they are, and
> linux doesn't repower them. but they're not).
> 
> Both of these issues have patches available, patches that can be found
> there for example:
> 
> http://colino.net/ibookg4/usb-ohci-fixes.patch
> http://colino.net/ibookg4/usb-ehci-power.patch
> 
> What kind of work on these is needed so that they get in?

Briefly, given 2.6.12-rc2 plus the patches mentioned above,
find out what else is needed.

 * The first of them is Paul's patch, and I never got a
   response to the questions I asked him about it.

     - 2.6.12-rc2 does have the fix to check for HC_STATE_QUIESCING,
       which should supplant the need for a new "suspending" quirk.

     - And the first of those patches waiting merge does update the
       handling of IRQs in the PCI-to-USB glue.

     - So the main change from that patch which is unresolved is
       moving the PMAC-specific stuff up from the OHCI code into
       into the the usb/core/hcd-pci code.  Presumably you could
       do that?  I assume that it really is needed at that layer,
       though it'll only relate to OHCI cells on Apple ASICs.

 * As for the second, that looks to be a hardware-specfic issue
   that just wouldn't reproduce with the controllers I was using
   for PM testing.  What I'll do is wrap up an equivalent fix with
   some related EHCI updates for power switching, post that, and
   ask you to verify that it works (probably simplest to do that
   with OHCI non-modular and not loaded).

How's that sound?

- Dave

  reply	other threads:[~2005-04-05 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 18:44 Colin Leroy
2005-04-05 20:53 ` David Brownell [this message]
2005-04-06 17:20   ` [linux-usb-devel] " Colin Leroy
2005-04-06 20:11     ` David Brownell
2005-04-06 23:02       ` Benjamin Herrenschmidt
2005-04-06 23:28         ` David Brownell
2005-04-06 23:50           ` Benjamin Herrenschmidt
2005-04-07  1:15             ` David Brownell
2005-04-07  6:41         ` Colin Leroy
2005-04-07  6:40       ` Colin Leroy

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=200504051353.36788.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=colin@colino.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®