Hi Luiz, Tanu, <div class="gmail_quote">On Wed, Jan 25, 2012 at 5:42 PM, Luiz Augusto von Dentz <<a href="mailto:luiz.dentz@gmail.com" target="_blank">luiz.dentz@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi Frederic, <div> On Tue, Jan 24, 2012 at 3:31 PM, Dalleau, Frederic <<a href="mailto:frederic.dalleau@intel.com" target="_blank">frederic.dalleau@intel.com</a>> wrote: > This is good question. > > Current patch include a configuration, so either the user is fine with the > default sink or he do not use the feature at all :D > > However, the following possibilities can be written : > 1) statically configure another sink in configuration file. > 2) Use the intended role : "music", or "voice" > 3) Other audio policy? > > All these scenario can be resumed into a call to function that returns the > desired sink. > > Number 1) is too restrictive. > We could imagine the loopback is an application, so number 2) make sense. > Number 3) would for sure require an external module to avoid > module-bluetooth-device depending on a policy module. </div>I got the impression that we are going forward with the idea of a policy module for PA, no idea if in the end it would load a policy or make a decision based on intent role, but anyways IMO the routing decisions should not be in module-bluetooth-discover. </blockquote><div> ok I'm updating the patches and will repost soon Frédéric </div></div>