greybus: rework synchronous operation completion
The only time we need a completion signaled on a request is when the
request provided no callback function. In that case, we wait for
a completion on behalf of the caller.
If an interrupt occurs, we attempt to cancel the message that's
been sent, but we don't actually complete the operation as required.
Instead of simply waiting for the completion, put in place a
special callback function for the synchronous operation. The
only job the callback has is to signal completion, allowing the
waiter to know it's done.
This means gb_operation_complete() will always have a non-null
callback pointer, so it becomes a simple wrapper, and we can get rid
of it and invoke the callback directly, in gb_operation_work().
Be defensive by checking for a null callback pointer, and reset
it to NULL once it's been called.
Signed-off-by: Alex Elder <elder@linaro.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
1 file changed
tree: 976cdfda3115f49bbbf60fb849d0ff75b86c50a4
- drivers/