[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190222225345.69084-2-briannorris@chromium.org>
Date: Fri, 22 Feb 2019 14:53:44 -0800
From: Brian Norris <briannorris@...omium.org>
To: Heiko Stuebner <heiko@...ech.de>,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Douglas Anderson <dianders@...omium.org>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-bluetooth@...r.kernel.org, <linux-kernel@...r.kernel.org>,
Matthias Kaehlcke <mka@...omium.org>,
Rajat Jain <rajatja@...gle.com>,
Robin Murphy <robin.murphy@....com>,
Brian Norris <briannorris@...omium.org>
Subject: [PATCH v2 2/3] dt-bindings: net: btusb: add QCA6174A IDs
There are two USB PID/VID variations I've seen for this chip, and I want
to utilize the 'interrupts' property defined here already.
Signed-off-by: Brian Norris <briannorris@...omium.org>
Reviewed-by: Matthias Kaehlcke <mka@...omium.org>
---
v2:
* drop leading zeroes from VID
---
Documentation/devicetree/bindings/net/btusb.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/btusb.txt b/Documentation/devicetree/bindings/net/btusb.txt
index 37d67926dd6d..b1ad6ee68e90 100644
--- a/Documentation/devicetree/bindings/net/btusb.txt
+++ b/Documentation/devicetree/bindings/net/btusb.txt
@@ -9,6 +9,9 @@ Required properties:
(more may be added later) are:
"usb1286,204e" (Marvell 8997)
+ "usbcf3,e300" (Qualcomm QCA6174A)
+ "usb4ca,301a" (Qualcomm QCA6174A (Lite-On))
+
Also, vendors that use btusb may have device additional properties, e.g:
Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt
--
2.21.0.rc0.258.g878e2cd30e-goog
Powered by blists - more mailing lists