AVRCP 1.3/1.4 current implementation

["David Stockwell" <dstockwell@frequency-one.com>]

Hello to all,

In my earlier work, I noticed that in audio/manager.c, function 
handle_uuids, when the UUID was found for an AVRCP target or controller, it 
would only launch avrcp_connect IF a Sink was enabled and present.

I suspect this was done to make sure that if a headset or similar was 
connecting, it would make sure the audio side of the connection was up and 
running before enabling the control side of the interface.

However, my device has no audio side, it is a pure AVRCP CT, so there is no 
audio-side connection.  In previous testing, I just unconditionally started 
avrcp_connect and it all worked fine for my purposes.  I am wondering if 
there is any other impact.

I could submit the patch in which avrcp_connect is unconditionally called. 
Or, I could just wait until all of the uuids are processed (after the 
g_slist_foreach in audio_probe), then launch avrcp_connect if either (a) a 
sink is connected and enabled as at present, or (b) if no sink is called for 
or provided by the CT/TG (as expressed in SDP), just launch avrcp_connect 
without the sink.  Are there any other impacts that this might cause?

To Joao, I would like to test my device against the GSOC work you did; can 
you send me the URL?  If you are farther along, no sense re-inventing the 
wheel. Thanks/obrigado.

David Stockwell