diff options
author | Richard Russon <ntfs@flatcap.org> | 2004-11-06 04:09:22 +0000 |
---|---|---|
committer | Richard Russon <ntfs@flatcap.org> | 2004-11-06 04:09:22 +0000 |
commit | ae3d2a189aaae2a83194d4af276c0eb73aca40d2 (patch) | |
tree | cd56ab71c46a0d91333c58411a37e472f9fe995b /Documentation | |
parent | c47d83003c229bb6f71e4a6bb6b89869e9d20918 (diff) | |
parent | df886b2210ac2e732554d020a7d0ea5120338bde (diff) | |
download | history-ae3d2a189aaae2a83194d4af276c0eb73aca40d2.tar.gz |
Merge flatcap.org:/home/flatcap/backup/bk/ntfs-2.6
into flatcap.org:/home/flatcap/backup/bk/ntfs-2.6-devel
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/arm/Samsung-S3C24XX/Suspend.txt | 24 |
1 files changed, 21 insertions, 3 deletions
diff --git a/Documentation/arm/Samsung-S3C24XX/Suspend.txt b/Documentation/arm/Samsung-S3C24XX/Suspend.txt index 59d4bad5b43ecc..9966156c2d5005 100644 --- a/Documentation/arm/Samsung-S3C24XX/Suspend.txt +++ b/Documentation/arm/Samsung-S3C24XX/Suspend.txt @@ -33,7 +33,8 @@ Resuming code to resume Linux operation. GSTATUS4 is currently left alone by the sleep code, and is free to - use for any other purposes. + use for any other purposes (for example, the EB2410ITX uses this to + save memory configuration in). Machine Support @@ -41,9 +42,9 @@ Machine Support The machine specific functions must call the s3c2410_pm_init() function to say that it's bootloader is capable of resuming. This can be as - simple as adding the following to the file: + simple as adding the following to the machine's definition: - late_initcall(s3c2410_pm_init); + INITMACHINE(s3c2410_pm_init) A board can do its own setup before calling s3c2410_pm_init, if it needs to setup anything else for power management support. @@ -52,6 +53,23 @@ Machine Support saving the resume address, if your board requires it, then contact the maintainer and discuss what is required. + Note, the origianal method of adding an late_initcall() is wrong, + and will end up initialising all compiled machine's pm init! + + +Debugging +--------- + + There are several important things to rember when using PM suspend: + + 1) The uart drivers will disable the clocks to the UART blocks when + suspending, which means that use of printascii() or similar direct + access to the UARTs will cause the debug to stop. + + 2) Whilst the pm code itself will attempt to re-enabled the UART clocks, + care should be taken that any external clock sources that the UARTs + rely on are still enabled at that point + Configuration ------------- |