Hi Marcel, On Tue, Feb 26, 2019 at 11:53 PM Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > > We may need to specify a GPIO wake pin for this device, so add a > > compatible property for it. > > > > There are at least to USB PID/VID variations of this chip: one with a > > Lite-On ID and one with an Atheros ID. > > > > Signed-off-by: Brian Norris <briannorris@xxxxxxxxxxxx> > > Reviewed-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx> > > --- > > v2: > > * drop leading zeroes from VID, per documented binding > > --- > > drivers/bluetooth/btusb.c | 2 ++ > > 1 file changed, 2 insertions(+) > > all 3 patches have been applied to bluetooth-next tree. Thanks! I failed to repeat my comment from v1: """ This patch is also required to make this stable, but since it's not really tied to the device tree, and it's an existing bug, I sent it separately: https://lore.kernel.org/patchwork/patch/1044896/ Subject: Bluetooth: btusb: request wake pin with NOAUTOEN """ Can you take this one too? Otherwise Scarlet will be less stable (possible interrupt storm at boot). Regards, Brian
