> > Device objects exists for each paired device. If the pairing is > removed the object is also removed and a new pairing is needed before > connecting to it (as imposed by the whole bluetooth stack logic > anyway). AFAIK the HDP source and sink must be paired before any session can be established, so the relevant device objects will always be there, so the path can be (re)used. > Re-using the device path and adding sessions as sub-paths seems > reasonable, but I would wait on comments from Johan / Luiz / Marcel if > this is desirable or might have any side-implication before defining > this topic as closed. -- 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
