On Thursday 14 April 2005 7:46 pm, Adam Belay wrote: > The new API uses a power container/domain model. I like that as a basic organizing principle, and I don't think anyone has problems with the notion that the power relationships can't always map directly to the physical device tree. Could you describe a bit about how the containers behave? For example, when a device drops its power consumption, how does it notify its container? And when sets of devices -- e.g. all USB devices, all PCI devices -- support the same power states, how will that code be shared? Would "struct power_device" be the driver model replacement for "struct power"? Also, I'd rather see "struct system_power_state *" everywhere you're now passing "int system_state" in the API. - Dave