On 20/07/17 19:23, Marcel Holtmann wrote: > > However I would prefer if we stop using hciattach and focus on hci_bcm.c support with btattach and serdev. I can resubmit my serdev driver if you like? It needs a little cleanup but its been solid here over the last week or two. Mostly its missing some runtime PM support (I cant test that as my device is crippled and has no host-wakeup or device-suspend lines). I cant see a nice way to integrate it with the existing driver due to the fact that it differs markedly in the routines that need pointers to the serio structures. The non-serio version uses a linked list that it traverses during startup to reconcile the port with the tty. Its a much uglier way to do it, but kinda by necessity. Is there any particular issue with having both drivers in-tree? A lot of legacy hardware will *never* use the serio method as it doesn't have the information available from firmware as to which serio device it should attach to. I guess some of the ACPI versions might be adaptable, but that would require some kind of ACPI->serio mapping that I'm not sure exists at present? ICBW though? -Ian -- 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
