diff options
author | Daniel Wagner <daniel.wagner@bmw-carit.de> | 2016-11-17 11:00:50 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-11-29 21:28:54 +0100 |
commit | 5b029624948d6864053166da1263df74c0c443df (patch) | |
tree | 94f4ab936f9919decceb63f7a9a79fc2702371b1 /mm | |
parent | 0430cafcc4fb632beeeab42f8817542dcf6901ce (diff) | |
download | linux-stable-5b029624948d6864053166da1263df74c0c443df.tar.gz linux-stable-5b029624948d6864053166da1263df74c0c443df.tar.bz2 linux-stable-5b029624948d6864053166da1263df74c0c443df.zip |
firmware: do not use fw_lock for fw_state protection
fw_lock is to use to protect 'corner cases' inside firmware_class. It
is not exactly clear what those corner cases are nor what it exactly
protects. fw_state can be used without needing the fw_lock to protect
its state transition and wake ups.
fw_state is holds the state in status and the completion is used to
wake up all waiters (in this case that is the user land helper so only
one). This operation has to be 'atomic' to avoid races. We can do this
by using swait which takes care we don't miss any wake up.
We use also swait instead of wait because don't need all the additional
features wait provides.
Note there some more cleanups possible after with this change. For
example for !CONFIG_FW_LOADER_USER_HELPER we don't check for the state
anymore. Let's to this in the next patch instead mingling to many
changes into this one. And yes you get a gcc warning "‘__fw_state_check’
defined but not used [-Wunused-function] code." for the time beeing.
Cc: Ming Lei <ming.lei@canonical.com>
Signed-off-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 'mm')
0 files changed, 0 insertions, 0 deletions