diff options
| -rw-r--r-- | Documentation/power/freezing-of-tasks.txt | 8 |
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 | |||
| 155 | only through another device that hasn't been resumed yet. In that case, | 155 | only through another device that hasn't been resumed yet. In that case, |
| 156 | request_firmware() will fail regardless of whether or not the freezing of tasks | 156 | request_firmware() will fail regardless of whether or not the freezing of tasks |
| 157 | is used. Consequently, the problem is not really related to the freezing of | 157 | is used. Consequently, the problem is not really related to the freezing of |
| 158 | tasks, since it generally exists anyway. [The solution to this particular | 158 | tasks, since it generally exists anyway. |
| 159 | problem is to keep the firmware in memory after it's loaded for the first time | 159 | |
| 160 | and upload if from memory to the device whenever necessary.] | 160 | A driver must have all firmwares it may need in RAM before suspend() is called. |
| 161 | If keeping them is not practical, for example due to their size, they must be | ||
| 162 | requested early enough using the suspend notifier API described in notifiers.txt. | ||