The following list shows the characteristics of the power model for Windows Mobile 6 Standard:
1. Windows Mobile 6 Standard never suspends.
2. You can turn off the backlight and the screen.
3. You can run threads.
4. Power handling in the OEMIdle function is more important than it is in the power model for Windows Mobile 6 Classic and Windows Mobile 6 Professional.
5. Low overhead and fast wake-ups from low power states.
Windows Mobile 6 Classic and Windows Mobile 6 Professional: The Suspend Path
1. Power Manager disables all Power Manager-aware non-block drivers.
2. Power Manager calls the IOCTL_HAL_PRESUSPEND input/output control code.
3. Power Manager notifies file systems.
4. Power Manager disables all Power Manager-aware block drivers.
5. The operating system transitions to single threaded mode.
6. Power Manager calls all legacy XXX_PowerDown (Device Manager)callback functions. There can be no system calls in the xxx_PowerDown callback function, because they will make the driver non-pageable.
7. Power Manager calls the OEMPowerOff function, which is the OEM code that suspends the CPU.
Windows Mobile 6 Classic and Windows Mobile 6 Professional: Behavior While Suspended
1. The CPU is suspended, so no threads are running. Only a hardware interrupt can wake the CPU, and multiple interrupts are multiplexed to the CPU pin. Typical hardware interrupt wake sources are the keyboard, the power button, a real-time clock (RTC) alarm, or a ring from the cell radio.
Windows Mobile 6 Classic and Windows Mobile 6 Professional: The Resume Path
The resume path for Windows Mobile 6 Classic and Windows Mobile 6 Professional is the reverse of the suspend path for Windows Mobile 6 Classic and Windows Mobile 6 Professional.
1. CPU wakes up and continues executing where left off in the OEMPowerOff function.
2. The OEMPowerOff function returns.
3. Power Manager calls all legacy XXX_PowerUp (Device Manager) callback functions.
4. The operating system transitions into multi-threaded mode.
5. Power Manager enables Power Manager-aware drivers, Power Manager-aware block drivers, and Power Manager-aware file systems.
No comments:
Post a Comment