Книга: Microsoft Windows Embedded CE 6.0 Exam Preparation Kit
Entering the Suspend State
Entering the Suspend State
When entering the Suspend state, Windows Embedded CE performs the following sequence of steps:
1. GWES notifies the Taskbar about the power down event.
2. The system aborts calibration if in the calibration screen.
3. The system stops the Windows message queues. After step 3, the system enters single-thread mode, which prevents function calls that rely on blocking operations.
4. The system checks if the startup user interface (UI) must appear on resume.
5. The system saves video memory to RAM.
6. The system calls SetSystemPowerState (NULL, POWER_STATE_SUSPEND, POWER_FORCE).
7. Power Manager:
a. Calls the FileSystemPowerFunction to power off the drivers related to the file system.
b. Calls PowerOffSystem to inform the kernel to do the final power down.
c. Calls Sleep(0) to invoke the scheduler.
NOTE
FileSystemPowerFunction and PowerOffSystem
If the OS design does not include Power Manager or GWES, then the OEM must explicitly call FileSystemPowerFunction and PowerOffSystem.
8. Kernel:
a. Unloads GWES process.
b. Unloads Filesys.exe.
c. Calls OEMPowerOff.
9. OEMPowerOff configures the interrupts and puts the CPU in Suspend state.
- 4.4.4 The Dispatcher
- About the author
- Chapter 7. The state machine
- Appendix E. Other resources and links
- Example NAT machine in theory
- The final stage of our NAT machine
- Compiling the user-land applications
- The conntrack entries
- User-land states
- Untracked connections and the raw table
- Basics of the iptables command
- State match