Hi,
On 30-05-18 15:25, Rob Herring wrote:
On Sun, May 27, 2018 at 2:04 PM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
Init hci_uart->init_ready so that hci_uart_init_ready() works properly.
Why do you need to init in a wq? For serdev devices, probe is async
already. So my thought was this wouldn't be needed.
The H5 protocol needs to exchange a number of messages to
sync the 2 sides before it can accept any HCI commands, so
it uses the delayed-registration feature of the hci_ldisc code by
setting the HCI_UART_INIT_PENDING. When doing serdev based enumeration
we could do something different but that would require significant
changes to the hci_h5.c code.
Regards,
Hans
--
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
