]>
Commit | Line | Data |
---|---|---|
fd913ef7 RJ |
1 | Generic Bluetooth controller over USB (btusb driver) |
2 | --------------------------------------------------- | |
3 | ||
4 | Required properties: | |
5 | ||
6 | - compatible : should comply with the format "usbVID,PID" specified in | |
7 | Documentation/devicetree/bindings/usb/usb-device.txt | |
8 | At the time of writing, the only OF supported devices | |
9 | (more may be added later) are: | |
10 | ||
11 | "usb1286,204e" (Marvell 8997) | |
7d19261b BN |
12 | "usbcf3,e300" (Qualcomm QCA6174A) |
13 | "usb4ca,301a" (Qualcomm QCA6174A (Lite-On)) | |
14 | ||
fd913ef7 | 15 | |
a4ccc9e3 RJ |
16 | Also, vendors that use btusb may have device additional properties, e.g: |
17 | Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt | |
18 | ||
fd913ef7 RJ |
19 | Optional properties: |
20 | ||
fd913ef7 RJ |
21 | - interrupt-names: (see below) |
22 | - interrupts : The interrupt specified by the name "wakeup" is the interrupt | |
23 | that shall be used for out-of-band wake-on-bt. Driver will | |
24 | request this interrupt for wakeup. During system suspend, the | |
25 | irq will be enabled so that the bluetooth chip can wakeup host | |
26 | platform out of band. During system resume, the irq will be | |
27 | disabled to make sure unnecessary interrupt is not received. | |
28 | ||
29 | Example: | |
30 | ||
31 | Following example uses irq pin number 3 of gpio0 for out of band wake-on-bt: | |
32 | ||
33 | &usb_host1_ehci { | |
fd913ef7 RJ |
34 | #address-cells = <1>; |
35 | #size-cells = <0>; | |
36 | ||
37 | mvl_bt1: bt@1 { | |
38 | compatible = "usb1286,204e"; | |
39 | reg = <1>; | |
40 | interrupt-parent = <&gpio0>; | |
41 | interrupt-name = "wakeup"; | |
42 | interrupts = <3 IRQ_TYPE_LEVEL_LOW>; | |
43 | }; | |
44 | }; |