Hi Ilya, > Device Tree bindings to configure the Bluetooth UART device. > > Signed-off-by: Ilya Faenson <ifaenson@xxxxxxxxxxxx> > --- > .../devicetree/bindings/net/bluetooth/btbcm.txt | 54 ++++++++++++++++++++++ > 1 file changed, 54 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/btbcm.txt > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/btbcm.txt b/Documentation/devicetree/bindings/net/bluetooth/btbcm.txt > new file mode 100644 > index 0000000..cc9f225 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/bluetooth/btbcm.txt > @@ -0,0 +1,54 @@ > +btbcm > +------ > + > +Required properties: > + > + - compatible : must be "brcm,brcm-bt-uart". > + - tty : tty device connected to this Bluetooth device. > + > +Optional properties: > + > + - bt-host-wake-gpios : bt-host-wake input GPIO to be used as an interrupt. > + > + - bt-wake-gpios : bt-wake output GPIO to be used to suspend / resume device. > + > + - reg-on-gpios : reg-on output GPIO to be used to power device on/off. > + > + - baud-rate-before-config-download : initial Bluetooth device baud rate. > + Default: 3000000. > + > + - manual-fc : flow control UART in suspend / resume scenarios. > + Default: 0. > + > + - configure-sleep : configure suspend / resume flag. > + Default: 0. > + > + - configure-audio : configure platform PCM SCO flag. > + Default: 0. > + > + - PCM* : SCO PCM platform parameters. Work with Broadcom on setting. > + Defaults: see the example below. I think at some point this needs to be reviewed by the DT guys as well. They surely want to have some say in the naming and how to deal with the Bluetooth devices behind UART controllers. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
