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,
	linux-usb-devel@lists.sourceforge.net,
	debian-powerpc@lists.debian.org
Subject: Re: [linux-usb-devel] USB glitches after suspend on ppc
Date: Wed, 6 Apr 2005 13:11:53 -0700	[thread overview]
Message-ID: <200504061311.53720.david-b@pacbell.net> (raw)
In-Reply-To: <20050406192007.7f71c61d@jack.colino.net>

On Wednesday 06 April 2005 10:20 am, Colin Leroy wrote:
> On 05 Apr 2005 at 13h04, David Brownell wrote:
> > > 
> > > 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.
> > ...
> > How's that sound?
> 
> Nice :)
> 
> Ok, here are the results of my tests with 2.6.12-rc2 and the patches
> you sent me applied:
> 
> - plug USB device, sleep, unplug USB device, resume: no more oops
> - sleep, plug in USB device: no oops, but it wakes the laptop up for a
> few seconds; then, it goes back to sleep. No oops on second resume. I
> can live with that :)

Interesting.  Looks like pci_enable_wake(dev, state, 0) isn't actually
disabling wakeup on your hardware.  (Assuming CONFIG_USB_SUSPEND=n; if
not, then it's odd that the system went back to sleep!)  Do you think
that might be related to those calls manipulating the Apple ASICs being
in the OHCI layer rather than up nearer the generic PCI glue?  (I still
think they don't belong in USB code -- ohci or usbcore -- at all.  If
the platform-specific PCI hooks don't suffice, they need fixing.)

Thanks for the testing update.  I'm glad to know that there seems to
be only one (minor) glitch that's PPC-specific!
 

> - once out of two resumes, resume leaves the ports unpowered; so I still
> need my usb-ehci-power.patch that re-powers ports unconditionnaly.

OK, I just posted the patch cleaning up EHCI port power switching;
that should remove the need for that separate patch.  (As well as
fixing some minor annoyances.)

- Dave

  reply	other threads:[~2005-04-06 20:12 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 ` [linux-usb-devel] " David Brownell
2005-04-06 17:20   ` Colin Leroy
2005-04-06 20:11     ` David Brownell [this message]
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=200504061311.53720.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®