From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
Pavel Machek <pavel@ucw.cz>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>
Subject: Re: [RFC] Fix Device Power Management States
Date: Tue, 10 Aug 2004 10:00:23 +0100 [thread overview]
Message-ID: <20040810100023.A18024@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1092098630.14100.73.camel@gaston>; from benh@kernel.crashing.org on Tue, Aug 10, 2004 at 10:43:50AM +1000
On Tue, Aug 10, 2004 at 10:43:50AM +1000, Benjamin Herrenschmidt wrote:
> > > Aha, so you are saying these do not need to be done in hardware order?
> >
> > AFAICT, no.
>
> As stated in my previous mail, I don't agree here... there are
> dependencies that cannot be dealt otherwise. USB was an example
> (ieee1394 is another), IDE is one, SCSI, i2c, whatever ...
>
> Of course, if we consider those "bus" drivers not to have class
> and thus not to be stopped and only the "leaf" devices to get stopped,
> that may work... I'm not sure we are not missing something there
> though...
Would a PCMCIA bridge be a "leaf" device in that definition, despite
having child devices?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-08-10 9:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 10:43 [RFC] Fix Device Power Management States Patrick Mochel
2004-08-09 11:38 ` Pavel Machek
2004-08-09 16:02 ` Patrick Mochel
2004-08-09 21:29 ` Pavel Machek
2004-08-10 5:03 ` Patrick Mochel
2004-08-10 9:43 ` Nigel Cunningham
2004-08-10 10:20 ` Pavel Machek
2004-08-10 22:33 ` Nigel Cunningham
2004-08-10 13:58 ` Patrick Mochel
2004-08-10 22:29 ` Nigel Cunningham
2004-08-10 22:56 ` Patrick Mochel
2004-08-10 23:09 ` Nigel Cunningham
2004-08-10 23:36 ` suspend2 merge [was Re: [RFC] Fix Device Power Management States] Pavel Machek
2004-08-11 0:04 ` Arkadiusz Miskiewicz
2004-08-11 5:05 ` Nigel Cunningham
2004-08-11 9:13 ` Pavel Machek
2004-08-10 10:13 ` [RFC] Fix Device Power Management States Pavel Machek
2004-08-10 18:36 ` David Brownell
2004-08-10 20:36 ` Pavel Machek
2004-08-10 22:42 ` Patrick Mochel
2004-08-09 22:15 ` Nigel Cunningham
2004-08-10 0:43 ` Benjamin Herrenschmidt
2004-08-10 9:00 ` Russell King [this message]
2004-08-10 10:08 ` Pavel Machek
2004-08-10 0:40 ` Benjamin Herrenschmidt
2004-08-10 4:55 ` Patrick Mochel
2004-08-10 6:52 ` Benjamin Herrenschmidt
2004-08-10 10:07 ` Pavel Machek
2004-08-10 14:28 ` Patrick Mochel
2004-08-10 17:56 ` Pavel Machek
2004-08-10 22:41 ` Patrick Mochel
2004-08-10 23:10 ` Pavel Machek
2004-08-10 23:14 ` [patch] Smaller goal first: fix confusion [was Re: [RFC] Fix Device Power Management States] Pavel Machek
2004-08-11 1:02 ` [RFC] Fix Device Power Management States Benjamin Herrenschmidt
2004-08-10 19:41 ` David Brownell
2004-08-10 22:44 ` Patrick Mochel
2004-08-10 10:33 ` Matthew Garrett
2004-08-10 14:36 ` Patrick Mochel
2004-08-10 19:18 ` David Brownell
2004-08-10 20:50 ` Pavel Machek
2004-08-11 1:47 ` Todd Poynor
2004-08-12 22:03 ` Russell King
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=20040810100023.A18024@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@ucw.cz \
/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.