Hi Marcel, On Wed, Jan 28, 2015, Marcel Holtmann wrote: > When receiving a HCI Hardware Error event, the controller should be > assumed to be non-functional until issuing a HCI Reset command. > > The Bluetooth hardware errors are vendor specific and so add a > new hdev->hw_error callback that drivers can provide to run extra > code to handle the hardware error. > > After completing the vendor specific error handling perform a full > reset of the Bluetooth stack by closing and re-opening the transport. > > Based-on-patch-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > include/net/bluetooth/hci_core.h | 3 +++ > net/bluetooth/hci_core.c | 21 +++++++++++++++++++++ > net/bluetooth/hci_event.c | 4 +++- > 3 files changed, 27 insertions(+), 1 deletion(-) Both of these patches have been 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
