---

yaml --- r: 62327 b: refs/heads/master c: fccdb5a h: refs/heads/master i: 62325: 5e6c499 62323: ccb741d 62319: ea44fe4 v: v3
git-mirror · Jul 22, 2007 · c7c998b · c7c998b
1 parent 19d91b6
commit c7c998b
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: d6269543ef24aa012aa228c27af3adb074f7b36b
+refs/heads/master: fccdb5ae7e453eb7de5592bc4ed17d10d4d90125
diff --git a/trunk/Documentation/power/freezing-of-tasks.txt b/trunk/Documentation/power/freezing-of-tasks.txt
@@ -155,6 +155,8 @@ Suppose, however, that the firmware file is located on a filesystem accessible
 only through another device that hasn't been resumed yet.  In that case,
 request_firmware() will fail regardless of whether or not the freezing of tasks
 is used.  Consequently, the problem is not really related to the freezing of
-tasks, since it generally exists anyway.  [The solution to this particular
-problem is to keep the firmware in memory after it's loaded for the first time
-and upload if from memory to the device whenever necessary.]
+tasks, since it generally exists anyway.
+
+A driver must have all firmwares it may need in RAM before suspend() is called.
+If keeping them is not practical, for example due to their size, they must be
+requested early enough using the suspend notifier API described in notifiers.txt.