Linux bluetooth development
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>
Cc: Eric Anholt <eric@anholt.net>, mzoran@crowfest.net
Subject: Re: Problem with re-loading hci_uart.ko on RPi3
Date: Sun, 18 Feb 2018 14:54:28 +0100 (CET)	[thread overview]
Message-ID: <1941091231.91372.1518962068876@email.1und1.de> (raw)
In-Reply-To: <E4785C91-043A-4FF5-BFCA-5FADAFF81EE5@holtmann.org>

Hi Marcel,

> Marcel Holtmann <marcel@holtmann.org> hat am 17. Februar 2018 um 22:09 geschrieben:
> 
> 
> Hi,
> 
> so with a 4.15 kernel, the Bluetooth chip on the RPi3 is fully supported via DT and serdev. The only problem still present is that when you rmmod hci_uart and then modprobe hci_uart again it will be stuck.
> 
> = New Index: 00:00:00:00:00:00 (Primary,UART,hci0)
> = Open Index: 00:00:00:00:00:00
> = Index Info: 00:00:00:00:00:00 (Broadcom Corporation)
> < HCI Command: Broadcom Update UART Baud Rate (0x3f|0x0018) plen 6
>         Encoded baud rate: Not used (0x0000)
>         Explicit baud rate: 2000000 Mbps
> < HCI Command: Reset (0x03|0x0003) plen 0
> = Close Index: 00:00:00:00:00:00
> = Delete Index: 00:00:00:00:00:00
> 
> Seems like something with the initial baud rate is wrong. When booting the hardware it is suppose to be set to 115200 Mbps, but it seems to be never reset after unloading the module. It stays at 2000000 Mbps. So when sending the Update UART Baud Rate initial command, it gets send at 115200 Mbps, but in reality the Bluetooth chip is still at 2000000 Mbps. So do we have to pull some reset GPIO to get this back into the original setting? Maybe this is just because the GPIOs are not yet exposed on the RPi3 as of now.

The datasheet says the default baudrate is at 115.200 Kbaud, but it also support automatic baudrate detection. So a reset via GPIO should enforce this baudrate.

> 
> Is there any update to get the GPIO expander work upstream?

The latest version of the GPIO expander patch series is here [1]. Unfortunately not merged yet.

I plan to provide bluetooth support for RPi Zero W. Is there anything missing from driver side?

Stefan

[1] - http://lists.infradead.org/pipermail/linux-rpi-kernel/2018-January/007397.html

> 
> One option is of course to keep the max-speed in the DT at 115200 Mbps. It would work, but seriously slow down the transport. Maybe this should be done until we get access to the GPIOs.
> 
> Regards
> 
> Marcel
>

  reply	other threads:[~2018-02-18 13:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 21:09 Problem with re-loading hci_uart.ko on RPi3 Marcel Holtmann
2018-02-18 13:54 ` Stefan Wahren [this message]
2018-02-18 17:55   ` Stefan Wahren
2018-02-18 19:07   ` Marcel Holtmann
2018-02-19 10:10     ` Frédéric Danis
2018-02-19 12:25       ` Stefan Wahren
2018-02-19 13:16         ` Marcel Holtmann
2018-02-19 18:28           ` Stefan Wahren
2018-02-19 18:38             ` Marcel Holtmann
2018-02-19 18:53               ` Stefan Wahren
2018-02-19 18:58                 ` Marcel Holtmann
2018-02-22 14:26                   ` Stefan Wahren
2018-02-22 15:43                     ` Marcel Holtmann
2018-02-22 18:05                       ` Stefan Wahren
2018-02-22 18:50                         ` Marcel Holtmann
2018-02-23 13:40                           ` Stefan Wahren
2018-02-26  8:13                             ` Marcel Holtmann
2018-02-26  9:36                               ` Stefan Wahren
2018-02-26 13:59                                 ` Marcel Holtmann
2018-02-19 13:12       ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1941091231.91372.1518962068876@email.1und1.de \
    --to=stefan.wahren@i2se.com \
    --cc=eric@anholt.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mzoran@crowfest.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox