From: Colin Leroy <colin@colino.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Brownell <david-b@pacbell.net>,
Linux-USB <linux-usb-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: [linux-usb-devel] USB glitches after suspend on ppc
Date: Thu, 7 Apr 2005 08:41:09 +0200 [thread overview]
Message-ID: <20050407084109.19cfd858@colin.toulouse> (raw)
In-Reply-To: <1112828577.9568.199.camel@gaston>
On Thu, 07 Apr 2005 09:02:57 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > 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.)
>
> There are no platform hooks in the right place for now afaik.
Nope, not in upstream, but I used the ohci patch from Paul Mackerras
previously.
> Anyway, I think Colin's controller is an OHCI/EHCI NEC chip, so not
> an Apple ASIC, it's not doing anything in those calls.
--
Colin
next prev parent reply other threads:[~2005-04-07 6:41 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
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 [this message]
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=20050407084109.19cfd858@colin.toulouse \
--to=colin@colino.net \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.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®