Hi Johan, Vinicius, On Tue, May 7, 2013 at 5:06 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Hi Vinicius, > > On Tue, May 07, 2013, Vinicius Gomes wrote: >> > As compared to his original patch, this patchset avoid creating an >> > additional service instance (which should already be created) and >> > instead performs a search within the list of existing services for >> > the given device. >> >> In the AG case when the external profile registers itself with the >> "server" role, the service doesn't get created. > > Hmm? HFP profile instances should be registered without any specific > "Role" property in RegisterProfile since both client and server sides > are required. > >> Nowadays, the service is created when the service is probed (with >> requires profile->device_probe), which doesn't happen for "adapter" >> services. I am still not sure about the right place/time to create the >> service for these cases. > > To my understanding btd_service is only for describing remote services > and not local ones, i.e. those that we can connect to as a client. I may > have misunderstood something about this though (for which Mikel is free > to correct me). The statement above is correct, btd_service is designed to represent remote services only. The confusion here might be caused by the fact that profile.c makes use of struct ext_io to represent both local and remote "services", but I believe this is an unfortunate implementation detail. Cheers, Mikel -- 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
