Hi Marcel, On Wed, Jul 02, 2014, Marcel Holtmann wrote: > With the new unconfigured controller state it is possible to provide a > fully functional HCI transport, but disable the higher level operations > that would normally happen. This way userspace can try to configure the > controller before releases the unconfigured state. > > The internal state is represented by HCI_UNCONFIGURED. This replaces the > HCI_QUIRK_RAW_DEVICE quirk as internal state representation. This is now > a real state and drivers can use the quirk to actually trigger this > state. In the future this will allow a more fine grained switching from > unconfigured state to configured state for controller inititialization. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > include/net/bluetooth/hci.h | 1 + > net/bluetooth/hci_core.c | 43 ++++++++++++++++++++++++++----------------- > net/bluetooth/hci_sock.c | 8 ++++---- > net/bluetooth/mgmt.c | 6 +++--- > 4 files changed, 34 insertions(+), 24 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
