Hi Tomas, ext Tomas Winkler wrote:
From: Gregory Paskar <greogry.paskar@xxxxxxxxx> A bluetooth device experiencing hardware failure may issue a HARDWARE_ERROR hci event. The reaction to this event is device reset flow implemented in following sequence. 1. Notify: HCI_DEV_DOWN 2. Reinitialize internal structures. 3. Call driver flush function 4. Send HCI reset request to the device. 5. Send HCI init sequence reset to the device. 6. Notify HCI_DEV_UP.
Drivers on some embedded platforms can disable whole bt chip with gpio line. Actually hw reset is sometimes needed for the reset. I'm wondering if it would be feasible to add hdev->close() and hdev->open requense to reset code? It would force driver to do hw reset for the chip.
-- Ville -- 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
