shared/vcp: have only one volume change in flight at a time If bt_vcp_set_volume() is called again before the previous operation has completed, the requests get the same change counter, and all except the first one fail. Fix by waiting until the current request completes, and if volume was set again during waiting, send a new request with the latest pending volume value. In this definition, bt_vcp_set_volume() will skip over intermediate volume updates if they are done too rapidly. Send only volume requests that change the value to a different one than last notification we have seen: in this case the request either fails, or succeeds and generates a new notification. In theory this guarantees we always exit waiting, but safeguard it with a timeout.

Diffstat

1 files changed, 82 insertions(+), 4 deletions(-)