Return-Path: Date: Sun, 25 Feb 2018 22:16:13 +0100 (CET) From: Stefan Wahren To: Marcel Holtmann Cc: Rob Herring , Lukas Wunner , Eric Anholt , Johan Hedberg , devicetree@vger.kernel.org, Loic Poulain , Florian Fainelli , linux-rpi-kernel@lists.infradead.org, Mark Rutland , Phil Elwell , =?UTF-8?Q?Fr=C3=A9d=C3=A9ric_Danis?= , linux-bluetooth@vger.kernel.org, linux-arm-kernel@lists.infradead.org Message-ID: <648118289.71086.1519593373795@email.1und1.de> In-Reply-To: <84F7E645-59B4-4618-8C91-A5CD654E16A6@holtmann.org> References: <1519567855-26105-1-git-send-email-stefan.wahren@i2se.com> <1519567855-26105-4-git-send-email-stefan.wahren@i2se.com> <84F7E645-59B4-4618-8C91-A5CD654E16A6@holtmann.org> Subject: Re: [PATCH 3/4] ARM: dts: bcm2835-rpi-zero-w: Add bcm43438 serial slave MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 List-ID: Hi Marcel, > Marcel Holtmann hat am 25. Februar 2018 um 21:17 geschrieben: > > > Hi Stefan, > > > Add BCM43438 (bluetooth) as a serdev slave device of uart0 (pl011/ttyAMA0). > > This allows to automatically insert the bcm43438 to the bluetooth > > subsystem instead of relying on patched userspace helpers (hciattach). > > > > In order to keep a debug UART we need to switch to uart1. > > > > Signed-off-by: Stefan Wahren > > --- > > arch/arm/boot/dts/bcm2835-rpi-zero-w.dts | 14 +++++++++++++- > > 1 file changed, 13 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm/boot/dts/bcm2835-rpi-zero-w.dts b/arch/arm/boot/dts/bcm2835-rpi-zero-w.dts > > index cf53436..b7f79f1 100644 > > --- a/arch/arm/boot/dts/bcm2835-rpi-zero-w.dts > > +++ b/arch/arm/boot/dts/bcm2835-rpi-zero-w.dts > > @@ -131,6 +131,18 @@ > > > > &uart0 { > > pinctrl-names = "default"; > > - pinctrl-0 = <&uart0_gpio14>; > > + pinctrl-0 = <&uart0_gpio32 &uart0_ctsrts_gpio30>; > > + status = "okay"; > > + > > + bluetooth { > > + compatible = "brcm,bcm43438-bt"; > > + max-speed = <2000000>; > > + shutdown-gpios = <&gpio 45 GPIO_ACTIVE_HIGH>; > > + }; > > +}; > > is the shutdown GPIO working as expected with this hardware. So even module unload and reload works fine? Yes, unload and reload works fine. > Meaning we are getting back to the 115200 default baud rate on the UART? I assume that, because reload works as expected. > Or is this actually the device-wakeup GPIO? The line is called BT_ON, so i don't expect this to be the device-wakeup. I don't have any schematics for the bluetooth part. Regards Stefan > > Regards > > Marcel >