On Wed, Jul 18, 2007 at 05:20:16PM +0200, Rafael J. Wysocki wrote: > Now, on the s3c24xx platforms one sysdev seems to be used for many > platform-related operations. In particular, two or more different sysdev > drivers having .suspend() and/or .resume() callbacks defined, related to > different parts of the platform, seem to bind to the same sysdev, which is > kind of ugly. It seems to be more correct to have a separate platform > device defined for each thing that requires to be suspended late or resumed > early and a dedicated platform driver handling these operations. A suggestion. The information's all there. All it takes is to look it up. ARM/S3C2410 ARM ARCHITECTURE P: Ben Dooks M: ben-linux@xxxxxxxxx L: linux-arm-kernel@xxxxxxxxxxxxxxxxxxxxxx (subscribers-only) W: http://www.fluff.org/ben/linux/ S: Maintained -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
