Hi Hans, >>>>> Make the serdev driver use struct bcm_device as its driver data and share >>>>> all the pm / GPIO / IRQ related code paths with the platform driver. >>>>> >>>>> After this commit the 2 drivers are in essence the same and the serdev >>>>> driver interface can be used for all ACPI enumerated HCI UARTs. >>>>> >>>>> Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> >>>>> --- >>>>> drivers/bluetooth/hci_bcm.c | 118 +++++++++++++++++++++++++------------------- >>>>> 1 file changed, 68 insertions(+), 50 deletions(-) >>>> all 9 patches have been applied to bluetooth-next tree. >>> >>> Excellent, thank you! >>> >>> So I guess this means we can also move forward with getting >>> the 2 patches from Frédéric Danis merged ? There is a bit >>> of a bisect-ability problem there, if the acpi pull-req >>> gets merged first then uart attached bcm bt will stop >>> working until the bluetooth subsys is also merged. >>> >>> But I don't think this will impact a lot of users >>> (also given the need for a manual btattach so far), >>> so I don't think this is a big problem... ? >> I wonder if we should just do this as all-in-one change for 4.15 kernel. We surely can get the ACPI changes into 4.15 and the Bluetooth changes as well. Then it should just work. >> So I am leaning to just adding the revert patch into the bluetooth-next tree and then just add the ACPI PnP ID for the GPD device in the same pull request. And if the ACPI changes make it then nobody will know the difference that we switched from USB to UART. > > Yes that should work fine. I think that is what I am going for. Mainly since the GPD USB hack already seems to be in 4.13 and thus a little to late to fix anyway. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
