xref: /linux/Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt (revision bfd5bb6f90af092aa345b15cd78143956a13c2a8)
1Marvell 8897/8997 (sd8897/sd8997) bluetooth devices (SDIO or USB based)
2------
3The 8997 devices supports multiple interfaces. When used on SDIO interfaces,
4the btmrvl driver is used and when used on USB interface, the btusb driver is
5used.
6
7Required properties:
8
9  - compatible : should be one of the following:
10	* "marvell,sd8897-bt" (for SDIO)
11	* "marvell,sd8997-bt" (for SDIO)
12	* "usb1286,204e"      (for USB)
13
14Optional properties:
15
16  - marvell,cal-data: Calibration data downloaded to the device during
17		      initialization. This is an array of 28 values(u8).
18		      This is only applicable to SDIO devices.
19
20  - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
21		        firmware will use the pin to wakeup host system (u16).
22  - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
23		      platform. The value will be configured to firmware. This
24		      is needed to work chip's sleep feature as expected (u16).
25  - interrupt-parent: phandle of the parent interrupt controller
26  - interrupt-names: Used only for USB based devices (See below)
27  - interrupts : specifies the interrupt pin number to the cpu. For SDIO, the
28		 driver will use the first interrupt specified in the interrupt
29		 array. For USB based devices, the driver will use the interrupt
30		 named "wakeup" from the interrupt-names and interrupt arrays.
31		 The driver will request an irq based on this interrupt number.
32		 During system suspend, the irq will be enabled so that the
33		 bluetooth chip can wakeup host platform under certain
34		 conditions. During system resume, the irq will be disabled
35		 to make sure unnecessary interrupt is not received.
36
37Example:
38
39IRQ pin 119 is used as system wakeup source interrupt.
40wakeup pin 13 and gap 100ms are configured so that firmware can wakeup host
41using this device side pin and wakeup latency.
42
43Example for SDIO device follows (calibration data is also available in
44below example).
45
46&mmc3 {
47	vmmc-supply = <&wlan_en_reg>;
48	bus-width = <4>;
49	cap-power-off-card;
50	keep-power-in-suspend;
51
52	#address-cells = <1>;
53	#size-cells = <0>;
54	btmrvl: bluetooth@2 {
55		compatible = "marvell,sd8897-bt";
56		reg = <2>;
57		interrupt-parent = <&pio>;
58		interrupts = <119 IRQ_TYPE_LEVEL_LOW>;
59
60		marvell,cal-data = /bits/ 8 <
61			0x37 0x01 0x1c 0x00 0xff 0xff 0xff 0xff 0x01 0x7f 0x04 0x02
62			0x00 0x00 0xba 0xce 0xc0 0xc6 0x2d 0x00 0x00 0x00 0x00 0x00
63			0x00 0x00 0xf0 0x00>;
64		marvell,wakeup-pin = /bits/ 16 <0x0d>;
65		marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
66	};
67};
68
69Example for USB device:
70
71&usb_host1_ohci {
72    #address-cells = <1>;
73    #size-cells = <0>;
74
75    mvl_bt1: bt@1 {
76	compatible = "usb1286,204e";
77	reg = <1>;
78	interrupt-parent = <&gpio0>;
79	interrupt-names = "wakeup";
80	interrupts = <119 IRQ_TYPE_LEVEL_LOW>;
81	marvell,wakeup-pin = /bits/ 16 <0x0d>;
82	marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
83    };
84};
85