firmware: add sanity check on shutdown/suspend
The firmware API should not be used after we go to suspend and after we reboot/halt. The suspend/resume case is a bit complex, so this documents that so things are clearer. We want to know about users of the API in incorrect places so that their callers are corrected, so this also adds a warn for those cases. Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
a669f04ab4
commit
81f9507628
@@ -44,6 +44,17 @@ request_firmware_nowait
|
||||
.. kernel-doc:: drivers/base/firmware_class.c
|
||||
:functions: request_firmware_nowait
|
||||
|
||||
Considerations for suspend and resume
|
||||
=====================================
|
||||
|
||||
During suspend and resume only the built-in firmware and the firmware cache
|
||||
elements of the firmware API can be used. This is managed by fw_pm_notify().
|
||||
|
||||
fw_pm_notify
|
||||
------------
|
||||
.. kernel-doc:: drivers/base/firmware_class.c
|
||||
:functions: fw_pm_notify
|
||||
|
||||
request firmware API expected driver use
|
||||
========================================
|
||||
|
||||
|
||||
Reference in New Issue
Block a user