Messages in this thread | | | Subject | Re: [PATCH 2/8] introduce the device async action mechanism | From | Zhang Rui <> | Date | Mon, 20 Jul 2009 11:09:36 +0800 |
| |
On Mon, 2009-07-20 at 06:16 +0800, Pavel Machek wrote: > Hi! > > > > > that's not enough. > > ???For examples, > > ACPI battery and EC are independent devices, but EC must be resumed > > before battery because battery driver may access some EC address space > > during resume time. > > Yes, but those dependencies should be pulled from driver tree, not > adding separate dependencies infrastructure. > Sorry, the problem I described above is wrong. We just disable the EC interrupt mode in S3, but it still works. Battery can access EC address space before EC resumed, in low speed.
> > > > In particular, we have to make sure that parent devices will not be suspended > > > until all of their children have been suspended and children devices will not > > > be resumed before the parents. > > this is right.
thanks, rui
-- 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/
| |