Hi Andrzej, > Following patches add possibility to specify custom parameters for > outgoing (e)SCO link. This is implemented as SCO socket options. > > This change allows to use reference parameters as defined in HFP 1.5 > specification as well as support for future enchancements as wideband > speech as defined in HFP 1.6 draft (uses different air coding format). > > Additional socket option (patch 3) allows to disable automatic retry > in case of failure which fallbacks from eSCO to SCO connection in > current implementation. Such fallback should not happen when using > wideband speech which mandates using of eSCO transport. I am not a big fan of just stupidly exposing all possible HCI value to userspace and let userspace set them. Especially since in the end there are no real variation here anyway. There are just a 2-3 use cases for your SCO socket. I would rather have simple mode to hand to the kernel and let it do the right thing (including negotiation and downgrading to SCO) than having userspace opening sockets over sockets again. So what are the actual modes for HFP that need to be supported and what is the range of possible SCO and eSCO options? Regards Marcel -- 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
