Extending the swsusp Hibernation Framework to ARM - The Linux ...

More documents

Recommendations

Info

Hibernation support for ARM• swsusp_arch_suspend– Utilizes cpu_suspend to save current cpu state– Second argument of cpu_suspend is called after state is saved– Calling cpu_resumecauses execution toreturn to cpu_suspendcaller– Utilizing soft_restartdisables MMU ascpu_resume expects
Hibernation support for ARM• swsusp_arch_resume– Uses stack allocated innosave region to preventourselves fromoverwriting our stack– We will overwrite ourcode, but with the samebytes– Uses cpu_resume torestore cpu state andreturn to cpu_suspendcaller
Page 3 and 4: Motivation• Hibernation provides
Page 5 and 6: swsusp
Page 7 and 8: OMAP PM• Clocks- Clock gating•
Page 9 and 10: WKUP Context• Used for:- Power, r
Page 11 and 12: PRCM• Reset state and module stat
Page 13 and 14: PRCM• Clocks- Leverage the clock
Page 15 and 16: pinctrl• Temporary measure, list
Page 17 and 18: pinctrl• Current solution is a bi
Page 19 and 20: SRAM• Internal memory on many OMA
Page 21 and 22: Other Devices• Many devices that
Page 23 and 24: Other Devices• Some device *do* n
Page 25: Hibernation support for ARM• Mini
Page 29 and 30: AM33xx Hibernation Support●●●
Page 31 and 32: Restore from U-Boot31
Page 33 and 34: Kernel Modifications• U-Boot does
Page 35 and 36: swsusp Image Layout●●Each metad
Page 37 and 38: U-Boot Memory Mapping• The U-Boot
Page 39 and 40: Loading swsusp Pages Into Memory•
Page 41 and 42: Copy Remaining Pages• Moved remap
Page 43: Introducing:The Next-Gen BeagleBone

Extending the swsusp Hibernation Framework to ARM - The Linux ...

Create successful ePaper yourself

Delete template?

Save as template?