aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/power/freezing-of-tasks.txt
diff options
context:
space:
mode:
authorOliver Neukum <oliver@neukum.org>2007-07-21 07:37:43 -0400
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-21 20:49:16 -0400
commitfccdb5ae7e453eb7de5592bc4ed17d10d4d90125 (patch)
treec85dd84f8e7db1629d20ebc468ba42249d970e4c /Documentation/power/freezing-of-tasks.txt
parentd6269543ef24aa012aa228c27af3adb074f7b36b (diff)
Documentation:reference notifiers.txt in freezing-of-tasks.txt
freezing-of-tasks.txt mentions firmware issues without mentioning the use of the new notifier API to overcome them. Here's an update. Signed-off-by: Oliver Neukum <oneukum@suse.de> Acked-by: Rafael J. Wysocki <rjw@sisk.pl> Acked-by: Nigel Cunningham <nigel@nigel.suspend2.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/power/freezing-of-tasks.txt')
-rw-r--r--Documentation/power/freezing-of-tasks.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/power/freezing-of-tasks.txt b/Documentation/power/freezing-of-tasks.txt
index af1a282c71a3..04dc1cf9d215 100644
--- a/Documentation/power/freezing-of-tasks.txt
+++ b/Documentation/power/freezing-of-tasks.txt
@@ -155,6 +155,8 @@ Suppose, however, that the firmware file is located on a filesystem accessible
155only through another device that hasn't been resumed yet. In that case, 155only through another device that hasn't been resumed yet. In that case,
156request_firmware() will fail regardless of whether or not the freezing of tasks 156request_firmware() will fail regardless of whether or not the freezing of tasks
157is used. Consequently, the problem is not really related to the freezing of 157is used. Consequently, the problem is not really related to the freezing of
158tasks, since it generally exists anyway. [The solution to this particular 158tasks, since it generally exists anyway.
159problem is to keep the firmware in memory after it's loaded for the first time 159
160and upload if from memory to the device whenever necessary.] 160A driver must have all firmwares it may need in RAM before suspend() is called.
161If keeping them is not practical, for example due to their size, they must be
162requested early enough using the suspend notifier API described in notifiers.txt.