|| ||Ming Lei <email@example.com> |
|| ||Linus Torvalds <firstname.lastname@example.org>,
Greg Kroah-Hartman <email@example.com> |
|| ||[RFC PATCH 00/13] firmware loader: introduce cache/uncache firmware |
|| ||Wed, 25 Jul 2012 01:00:00 +0800|
|| ||"Rafael J. Wysocki" <firstname.lastname@example.org>,
Borislav Petkov <email@example.com>,
|| ||Article, Thread
In , the problem below has been discussed for some time:
device's firmware may be lost during suspend/resume
cycle because device is unplugged and plugged again
or device experiences system power loss in the period.
but during resume path, system is still not ready(process
frozen, rootfs not usable, ...) to complete loading firmware
from user space for the device
The conclusion is that caching firmware during suspend/resume cycle
is capable of solving the problem.
This patchset implements cache/uncache firmware mechanism,
and apply the mechnism to cache device's firmware in kernel memory
space automatically during suspend/resume cyclye, so device can
load its firmware easily during resume path. When resume is completed
and system is ready, the cached firmwares will be removed from
kernel memory later.
Even there are some corener cases which can't be solved this cache
approach, but as Linus pointed, the driver should use some specific
way to fix it, for example, the isight camera problem can easily be
solved with deferral probe by driver explicitly, see , and some
patches will be posted later to do it.