summaryrefslogtreecommitdiff
path: root/drivers/base/Kconfig
diff options
context:
space:
mode:
authorBjorn Andersson <bjorn.andersson@linaro.org>2016-12-06 17:01:45 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-12-08 21:05:54 +0100
commit5d47ec02c37ea632398cb251c884e3a488dff794 (patch)
tree743813f72d14ed2a4b1981fe0a70f3b0466221b4 /drivers/base/Kconfig
parent64df1148876e35e81e91195e01c8197edc66fcc5 (diff)
firmware: Correct handling of fw_state_wait() return value
When request_firmware() finds an already open firmware object it will wait for that object to become fully loaded and then check the status. As __fw_state_wait_common() succeeds the timeout value returned will be truncated in _request_firmware_prepare() and interpreted as -EPERM. Prior to "firmware: do not use fw_lock for fw_state protection" the code did test if we where in the "done" state before sleeping, causing this particular code path to succeed, in some cases. As the callers are interested in the result of the wait and not the remaining timeout the return value of __fw_state_wait_common() is changed to signal "done" or "error", which simplifies the logic in _request_firmware_load() as well. Fixes: 5b029624948d ("firmware: do not use fw_lock for fw_state protection") Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Reviewed-by: Daniel Wagner <daniel.wagner@bmw-carit.de> Acked-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base/Kconfig')
0 files changed, 0 insertions, 0 deletions