roadrunner2

@omnibrain Apologies for the broken links - fixed now.

@Maximus- for completeness sake: do you have the all of the following kernel config enabled: `CONFIG_SERIAL_8250_LPSS`, `CONFIG_BT_HCIUART_BCM`, `CONFIG_BT_HCIUART_SERDEV`, `CONFIG_SERIAL_DEV_BUS`, `CONFIG_SERIAL_DEV_CTRL_TTYPORT`, and `CONFIG_SERIAL_8250_DW`? There may well be something missing for 8,1...

@l1k I rebased your `hci_bcm_v1` branch on v4.15.0-rc5 and verified it works fine on MBP13,3. LGTM. Thanks! @Maximus- regarding lag: make sure the gnome bluetooth settings window is not open...

Oh, I did just notice an interesting stack trace in dmesg (but haven't investigated if this is serious or not): ``` ============================= WARNING: suspicious RCU usage 4.15.0-rc5+ #13 Tainted: G...

Hmm, so now in the v2 version, on powering down we call BTPD followed by BTLP(1) - is that kosher?

@l1k So I cherry-picked your v2 commits onto v4.15-rc5 (commits 43fff7683468 and b8841a08ed93-e982998851a3). It's failing `bcm_serdev_probe()` because in `bcm_get_resources()` the `devm_gpiod_get_optional(..., "device-wakeup", ...)` was changed to `devm_gpiod_get(..., "device-wakeup", ...)` (which...

@l1k This is working for me (MBP13,3): patches were cherry-picked onto v4.15-rc6.

@peterychuang Does removing and re-loading the `hci_uart` kernel module help?

@peterychuang I'll try build the original `hci_bcm_v2` tomorrow; but if you want, you can try my [hci_bcm_v4.15_v2](/roadrunner2/linux/tree/hci_bcm_4.15_v2) branch which is @l1k's patches cherry-picked onto v4.15-rc6 and which is working for...

@l1k Both your original `hci_bcm_v3` branch, as well as cherry-picking the relevant commits onto v4.15-rc6 work fine for me. Suspend and resume didn't show any issues either (nothing logged, Bluetooth...