From c7c998b964f5211f34ab14334d0af8903f2fc35b Mon Sep 17 00:00:00 2001 From: Oliver Neukum Date: Sat, 21 Jul 2007 04:37:43 -0700 Subject: [PATCH] --- yaml --- r: 62327 b: refs/heads/master c: fccdb5ae7e453eb7de5592bc4ed17d10d4d90125 h: refs/heads/master i: 62325: 5e6c499202876e5216209fb9358b9943f6b49f0a 62323: ccb741d7847dfc39b4cfbedb7dc5e2b6bc3de6ab 62319: ea44fe4922615737402dcec5af1063bc7d5a134c v: v3 --- [refs] | 2 +- trunk/Documentation/power/freezing-of-tasks.txt | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index ffb8d48316d5..cd95857e194e 100644 --- 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 index af1a282c71a3..04dc1cf9d215 100644 --- 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.