transport: Delay existence based on delay reporting capability In case when the existence of the delay property is based on its value not being zero it is not possible to read the delay if sink sets it to zero on purpose (or it was not updated by the sink at all). However, client might expect it to be readable, if SEP reports delay reporting as available. Instead of checking the value, we should check the capabilities of the AVDTP stream. Also, by doing that we can allow this property to be writable in the future - the exists() callback is used in the properties_set() function as well.

Diffstat

3 files changed, 25 insertions(+), 7 deletions(-)