Hi Marcel, On Wed, Apr 08, 2015, Marcel Holtmann wrote: > When establishing a Bluetooth LE connection, read the remote used > features mask to determine which features are supported. This was > not really needed with Bluetooth 4.0, but since Bluetooth 4.1 and > also 4.2 have introduced new optional features, this becomes more > important. > > This works the same as with BR/EDR where the connection enters the > BT_CONFIG stage and hci_connect_cfm call is delayed until the remote > features have been retrieved. Only after successfully receiving the > remote features, the connection enters the BT_CONNECTED state. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > include/net/bluetooth/hci.h | 13 ++++++ > net/bluetooth/hci_event.c | 107 +++++++++++++++++++++++++++++++++++++++++++- > 2 files changed, 118 insertions(+), 2 deletions(-) Applied to bluetooth-next. Thanks. Johan -- 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
