From: Pavel Machek <pavel@suse.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] New system device API
Date: Sat, 7 Jun 2003 22:33:11 +0200 [thread overview]
Message-ID: <20030607203304.GB667@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0306061749200.11379-100000@cherise>
Hi!
> For things like CPUs, generic code will register the class, but other
> architecture-specific or otherwise configurable drivers may register
> auxillary drivers, that look like:
>
> struct sysdev_driver {
> struct list_head entry;
> int (*add)(struct sys_device *);
> int (*remove)(struct sys_device *);
> int (*shutdown)(struct sys_device *);
> int (*suspend)(struct sys_device *, u32 state);
> int (*resume)(struct sys_device *);
> };
System devices may be special, but they should not be so special not
to require u32 level. All current system devices need to be
suspended last, but that's pure coincidence, I believe.
As mikpe noted, hierarchy is still needed between "system" devices:
nmi watchdog depends on lapic...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-06-07 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 1:18 Patrick Mochel
2003-06-07 20:33 ` Pavel Machek [this message]
2003-06-09 16:19 ` Patrick Mochel
2003-06-09 18:42 ` Pavel Machek
2003-06-09 20:30 ` Patrick Mochel
2003-06-09 21:07 ` Pavel Machek
2003-06-09 21:15 ` Patrick Mochel
2003-06-09 21:23 ` Pavel Machek
2003-06-09 21:40 ` Patrick Mochel
2003-06-09 22:04 ` Pavel Machek
2003-06-09 23:09 ` Nigel Cunningham
2003-06-09 23:16 ` Pavel Machek
2003-06-09 23:24 ` Nigel Cunningham
2003-06-09 23:25 ` Patrick Mochel
2003-06-09 23:26 ` Pavel Machek
2003-06-09 21:32 ` Pavel Machek
2003-06-09 21:41 ` Patrick Mochel
2003-06-10 18:27 ` Jesse Pollard
2003-06-07 10:34 mikpe
2003-06-09 16:18 ` Patrick Mochel
2003-06-09 17:39 mikpe
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=20030607203304.GB667@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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
all inboxes | Powered by JetHome®