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 <stefan.wahren@xxxxxxxx>
>>> ---
>>> 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.
awesome. That is good news.
Since you said that the GPIO expander driver for the RPi 3 has been accepted, did you test it there as well? If so, then it would be good to get a patch that also provides shutdown-gpios for RPi 3.
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
