On Mon, Aug 7, 2017 at 5:39 AM, Loic Poulain <loic.poulain@xxxxxxxxx> wrote: > Add binding document for serial bluetooth chips using > Broadcom protocol. > > Signed-off-by: Loic Poulain <loic.poulain@xxxxxxxxx> > --- > v2: dt-bindings as separate patch > rebase on upcoming pi3 dts changes > v3: changes in bcm serdev drivers: > name refactoring and additional comments > Add generic host_set_baudrate method > Use agnostic device_property_read > .../devicetree/bindings/net/broadcom-bluetooth.txt | 29 ++++++++++++++++++++++ > 1 file changed, 29 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/broadcom-bluetooth.txt > > diff --git a/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt b/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt > new file mode 100644 > index 0000000..c51ea1b > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt > @@ -0,0 +1,29 @@ > +Broadcom Bluetooth Chips > +--------------------- > + > +This documents the binding structure and common properties for serial > +attached Broadcom devices. > + > +Serial attached Broadcom devices shall be a child node of the host UART > +device the slave device is attached to. > + > +Required properties: > + > + - compatible: should contain one of the following: > + * "brcm,bcm43438-bt" > + > +Optional properties: Most Broadcom devices have a couple of GPIOs needing control. Maybe they are tied off active on RPi3, but you should document them here even if the driver doesn't yet need them. I think they are the same as the Nokia BT IIRC. Same goes for any input clocks. > + > + - max-speed: see Documentation/devicetree/bindings/serial/slave-device.txt > + > +Example: > + > +&uart2 { > + pinctrl-names = "default"; > + pinctrl-0 = <&uart2_pins>; > + > + bluetooth { > + compatible = "brcm,bcm43438-bt"; > + max-speed = <921600>; > + }; > +}; > -- > 1.9.1 > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html