Re: [PATCH] Bluetooth: hci_core: fix init with HCI_QUIRK_NON_PERSISTENT_SETUP

2019-10-16 Thread Mattijs Korpershoek
Hi Marcel, Marcel Holtmann writes: Hi Mattijs, Some HCI devices which have the HCI_QUIRK_NON_PERSISTENT_SETUP [1] require a call to setup() to be ran after every open(). During the setup() stage, these devices expect the chip to acknowledge its setup() completion via vendor specific

Re: [PATCH] Bluetooth: hci_core: fix init with HCI_QUIRK_NON_PERSISTENT_SETUP

2019-10-16 Thread Marcel Holtmann
Hi Mattijs, > Some HCI devices which have the HCI_QUIRK_NON_PERSISTENT_SETUP [1] > require a call to setup() to be ran after every open(). > > During the setup() stage, these devices expect the chip to acknowledge > its setup() completion via vendor specific frames. > > If userspace opens()

[PATCH] Bluetooth: hci_core: fix init with HCI_QUIRK_NON_PERSISTENT_SETUP

2019-10-03 Thread Mattijs Korpershoek
Some HCI devices which have the HCI_QUIRK_NON_PERSISTENT_SETUP [1] require a call to setup() to be ran after every open(). During the setup() stage, these devices expect the chip to acknowledge its setup() completion via vendor specific frames. If userspace opens() such HCI device in