Hello! Can anybody help me to understand the process of handling avdtp SET_CONFIGURATION command in scenario when a2dp headset initializes connection to linux machine? I see that the headset sends SET_CONFIGURATION avdtp command (with appropriate SBC params), but i cant find out how this ultimately translates to actual configuration of a player (totem in my case). What layers are involved in general? I see that handling of the command follows the following path (approx.): avdtp.c::sbc_setconf_ind() a2dp.c::auto_config() avdtp.c::avdtp_sep_set_state() a2dp.c::stream_state_changed() sink.c::stream_state_changed() At no stage I am able to spot the actual configuration of the sbc... (there should be probably some sort of d-bus messages, but, again, I don’t see that neither SelectConfiguration nor SetConfiguration from the media-api are used). In addition, there is BT_SET_CONFIGURATION command that is handled in unix.c (after SET_CONFIGURATION is handled); how does it fits in the configuration picture? Any info (or reference where it can be found) will be much appreciated. Thanks and regards. Ilia Kolominsky iliak@xxxxxx Direct: +972(9)7906231 Mobile: +972(54)909009 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
