[PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties · Brian Norris <briannorris@chromium.org> · 2019-02-22
[PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs · Brian Norris <briannorris@chromium.org> · 2019-02-22
Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs · Matthias Kaehlcke <mka@chromium.org> · 2019-02-22
Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs · Robin Murphy <robin.murphy@arm.com> · 2019-02-22
Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs · Brian Norris <briannorris@chromium.org> · 2019-02-22
[PATCH 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node · Brian Norris <briannorris@chromium.org> · 2019-02-22
Re: [PATCH 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node · Matthias Kaehlcke <mka@chromium.org> · 2019-02-22
Re: [PATCH 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node · Rajat Jain <hidden> · 2019-02-22
Re: [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties · Matthias Kaehlcke <mka@chromium.org> · 2019-02-22

Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs

From: Brian Norris <briannorris@chromium.org>
Date: 2019-02-22 22:11:17
Also in: linux-arm-kernel, linux-bluetooth, linux-rockchip, lkml

On Fri, Feb 22, 2019 at 1:57 PM Robin Murphy [off-list ref] wrote:

On 2019-02-22 12:34 am, Brian Norris wrote:

quoted

+               "usb0cf3,e300" (Qualcomm QCA6174A)
+               "usb04ca,301a" (Qualcomm QCA6174A (Lite-On))

Nit: the USB device binding states that those leading zeroes in the VIDs
should be suppressed.

Ah, thanks. Didn't notice that part. I'll remove the zeroes and resend.

Brian