Linux bluetooth development
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Frédéric Danis" <frederic.danis.oss@gmail.com>,
	"Marcel Holtmann" <marcel@holtmann.org>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	Eric Anholt <eric@anholt.net>
Subject: Re: Problem with re-loading hci_uart.ko on RPi3
Date: Mon, 19 Feb 2018 13:25:38 +0100	[thread overview]
Message-ID: <f94056a0-ece7-c579-6b7d-d6589079d9e6@i2se.com> (raw)
In-Reply-To: <76f76129-dd3e-2d17-635d-18a563d12aa8@gmail.com>

Am 19.02.2018 um 11:10 schrieb Frédéric Danis:
> Hi Marcel,
>
> Le 18/02/2018 à 20:07, Marcel Holtmann a écrit :
>>
>>>> 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.
>> So I am convinced when we run on hardware that has no GPIO resources 
>> exposed (as it is with RPi right now), we should limit the 
>> operational speed to the initialization speed. And then my problem 
>> actually goes away. It also forces people to get the GPIOs exposed or 
>> they have to stick with a slower HCI transport.
>
> We may also reset to initialization speed on module unload.
> This will allow multiple tests on the hardware, even if it does not 
> have GPIOs exposed.

I prefer this solution instead of coding workarounds within the devicetree.

Thanks
Stefan

>
> Regards,
>
> Fred
>

  reply	other threads:[~2018-02-19 12:25 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
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 [this message]
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=f94056a0-ece7-c579-6b7d-d6589079d9e6@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=eric@anholt.net \
    --cc=frederic.danis.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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