Messages in this thread | | | Date | Sat, 7 Jun 2003 22:33:11 +0200 | From | Pavel Machek <> | Subject | Re: [RFC] New system device API |
| |
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?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |