From: Russell King <rmk@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: Fix up power managment in 2.6
Date: Mon, 1 Sep 2003 23:48:40 +0100 [thread overview]
Message-ID: <20030901234840.H22682@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030901224018.GA470@elf.ucw.cz>; from pavel@ucw.cz on Tue, Sep 02, 2003 at 12:40:18AM +0200
On Tue, Sep 02, 2003 at 12:40:18AM +0200, Pavel Machek wrote:
> > The main advantage from a driver writers point of view is the disposal
> > of the "level" argument. (Doesn't really affect x86, PCI drivers never
> > had visibility of this.)
>
> Yes, "level" is gone, instead we have very ugly
> -EAGAIN-means-call-me-with-interrupts-disabled hack.
>From a driver writers point of view, that's something I won't be using.
If I'm told to suspend, I better suspend. If the driver model is calling
me out of sequence (because there are other children depending on me)
then it hasn't taken notice of my ordering requirements.
(Note - this bit isn't complete, but then the new model is no worse off
than the old model at present with respect to that issue. The new model
does provide the interfaces to allow drivers to specify these dependencies
though.)
> > However, I'll let the PPC people justify the real reason for the driver
> > model change, since it was /their/ requirement that caused it, and I'm
> > not going to fight their battles for them. (although I seem to be doing
> > exactly that while wasting my time here.)
>
> I noticed something going on, but it seem to me one more "struct bus"
> would have solved that...
I've no idea what the PPC problem exactly was. It's up to the PPC guys
to speak up *now*.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-09-01 22:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 23:28 Fix up power managment in 2.6 Pavel Machek
2003-09-01 6:57 ` Russell King
2003-09-01 8:11 ` Pavel Machek
2003-09-01 8:26 ` Russell King
2003-09-01 9:33 ` Pavel Machek
2003-09-01 16:28 ` Linus Torvalds
2003-09-01 21:12 ` Pavel Machek
2003-09-01 21:52 ` Russell King
2003-09-01 22:19 ` Pavel Machek
2003-09-01 22:30 ` Russell King
2003-09-01 22:40 ` Pavel Machek
2003-09-01 22:48 ` Russell King [this message]
2003-09-02 17:17 ` Greg KH
2003-09-03 15:13 ` Pavel Machek
2003-09-02 10:21 ` Benjamin Herrenschmidt
2003-09-03 13:02 ` Alan Cox
2003-09-03 13:31 ` Benjamin Herrenschmidt
2003-09-03 17:08 ` Pavel Machek
2003-09-05 20:42 ` Pavel Machek
2003-09-01 22:55 ` Patrick Mochel
2003-09-01 23:38 ` Pavel Machek
2003-09-02 0:52 ` Patrick Mochel
2003-09-02 9:02 ` Pavel Machek
2003-09-02 9:47 ` Pavel Machek
2003-09-02 16:11 ` Patrick Mochel
2003-09-03 16:21 ` Pavel Machek
2003-09-03 23:17 ` Patrick Mochel
2003-09-03 17:49 ` Pavel Machek
2003-09-03 17:59 ` bill davidsen
2003-09-03 23:20 ` Patrick Mochel
2003-09-05 9:33 ` Pavel Machek
2003-09-03 20:03 ` Bill Davidsen
2003-09-03 22:14 ` Pavel Machek
2003-09-04 4:06 ` Bill Davidsen
2003-09-04 14:52 ` Patrick Mochel
2003-09-02 10:29 ` Jan Rychter
2003-09-05 5:58 ` Rob Landley
2003-09-05 10:26 ` Pavel Machek
2003-09-05 10:56 ` Michael Frank
2003-09-05 11:08 ` Pavel Machek
2003-09-05 11:51 ` Michael Frank
2003-09-05 12:01 ` Pavel Machek
2003-09-05 17:47 ` Patrick Mochel
2003-09-05 18:02 ` Jeff Garzik
2003-09-05 18:13 ` Patrick Mochel
2003-09-05 21:46 ` Jeff Garzik
2003-09-05 18:57 ` Rob Landley
2003-09-05 19:06 ` Pavel Machek
2003-09-05 20:09 ` Keyboard stuff (was Re: Fix up power managment in 2.6) Rob Landley
2003-09-05 20:31 ` Pavel Machek
2003-09-05 20:01 ` Fix up power managment in 2.6 Richard A Nelson
2003-09-05 21:45 ` Jeff Garzik
2003-09-05 18:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:13 Nicolas Mailhot
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=20030901234840.H22682@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.org \
/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