From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices
Date: Wed, 18 Jan 2017 14:02:06 -0800 [thread overview]
Message-ID: <m2fukgyqld.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCC0RADEKnkYEF6_DkBTftdjmPMku+N3bdvZMCoqs96xGA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 18 Jan 2017 12:25:43 +0100")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> Kevin,
>
> On Sun, Jan 15, 2017 at 11:32 PM, Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
>> This adds the missing kernel bits for Bluetooth support on the
>> Tronsmart Vega S95 (GXBB based) boards as well as for the GXL
>> P230/P231 and GXM Q200/Q201 reference boards.
>>
>> The Bluetooth functionality on these boards is provided by the
>> SDIO wifi/Bluetooth combo-chip (Broadcom bcm43xx based). The
>> Bluetooth module on that combo-chip has to be taken out of reset,
>> which is taken care of the GPIO in the sdio_pwrseq.
>>
>> Once the module is taken out of reset it can be set up from userspace
>> using the "hciattach" tool from bluez, which talks to the Bluetooth
>> module which is connected to one of the serial ports (in our case
>> uart_A). To get the Bluetooth module initialized within the timeout
>> defined by "hciattach" (and to achieve usable speeds for Bluetooth
>> transfers) the communication uses a speed of 2000000 baud, which was
>> not supported by meson_uart before.
>>
>> NOTE: The .dts-changes from this series depends on my previous series
>> "add support for uart_AO_B" - see [0]
>>
>>
>> [0] http://lists.infradead.org/pipermail/linux-amlogic/2017-January/001982.html
>>
>>
>> Martin Blumenstingl (4):
>> tty: serial: meson: allow baud-rates higher than 115200
>> ARM64: dts: meson-gx: add the serial CTS and RTS pin groups
>
> Neil just informed me that Rob Herring is working on defining the UART
> Bluetooth device properly using devicetree (preparation for this is
> named "[PATCH v2 0/9] Serial slave device bus", see [0] for the
> mailing-list conversation and [1] for a WiP git repo).
Ah, good news. I knew Rob had been talking about that for awhile, so
I'm glad to see it coming into existence. Thanks for the pointers.
> This means that there will be a better solution than the one proposed
> in the meson-gx-p23x-q20x and meson-gxbb-vega-s95 patches (patches #1
> and #2 are not affected by this),> namely:
> - I'm currently (ab)using sdio-pwrseq node to power on the UART
> Bluetooth module, this can solved by specifying a bluetooth { } node
> inside the &uart_A node in the future and providing the corresponding
> GPIOs there
Good. I didn't like the (ab)use of sdio_pwrseq GPIO resets for the
bluetooth either.
> - all the userspace commands will not be necessary once
> drivers/bluetooth/hci_bcm.c is changed to the serio framework and gets
> devicetree support
Cool. Maybe you can setup a WIP branch based on Rob's work for broader
testing on Amlogic boards until this gets merged?
In the mean time, I've applied patch 2/4 and hopefully the drivers/tty
patch will go through the serial tree.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
catalin.marinas@arm.com, gregkh@linuxfoundation.org,
will.deacon@arm.com, robh+dt@kernel.org,
linux-serial@vger.kernel.org, jslaby@suse.com, carlo@caione.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices
Date: Wed, 18 Jan 2017 14:02:06 -0800 [thread overview]
Message-ID: <m2fukgyqld.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCC0RADEKnkYEF6_DkBTftdjmPMku+N3bdvZMCoqs96xGA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 18 Jan 2017 12:25:43 +0100")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> Kevin,
>
> On Sun, Jan 15, 2017 at 11:32 PM, Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
>> This adds the missing kernel bits for Bluetooth support on the
>> Tronsmart Vega S95 (GXBB based) boards as well as for the GXL
>> P230/P231 and GXM Q200/Q201 reference boards.
>>
>> The Bluetooth functionality on these boards is provided by the
>> SDIO wifi/Bluetooth combo-chip (Broadcom bcm43xx based). The
>> Bluetooth module on that combo-chip has to be taken out of reset,
>> which is taken care of the GPIO in the sdio_pwrseq.
>>
>> Once the module is taken out of reset it can be set up from userspace
>> using the "hciattach" tool from bluez, which talks to the Bluetooth
>> module which is connected to one of the serial ports (in our case
>> uart_A). To get the Bluetooth module initialized within the timeout
>> defined by "hciattach" (and to achieve usable speeds for Bluetooth
>> transfers) the communication uses a speed of 2000000 baud, which was
>> not supported by meson_uart before.
>>
>> NOTE: The .dts-changes from this series depends on my previous series
>> "add support for uart_AO_B" - see [0]
>>
>>
>> [0] http://lists.infradead.org/pipermail/linux-amlogic/2017-January/001982.html
>>
>>
>> Martin Blumenstingl (4):
>> tty: serial: meson: allow baud-rates higher than 115200
>> ARM64: dts: meson-gx: add the serial CTS and RTS pin groups
>
> Neil just informed me that Rob Herring is working on defining the UART
> Bluetooth device properly using devicetree (preparation for this is
> named "[PATCH v2 0/9] Serial slave device bus", see [0] for the
> mailing-list conversation and [1] for a WiP git repo).
Ah, good news. I knew Rob had been talking about that for awhile, so
I'm glad to see it coming into existence. Thanks for the pointers.
> This means that there will be a better solution than the one proposed
> in the meson-gx-p23x-q20x and meson-gxbb-vega-s95 patches (patches #1
> and #2 are not affected by this),> namely:
> - I'm currently (ab)using sdio-pwrseq node to power on the UART
> Bluetooth module, this can solved by specifying a bluetooth { } node
> inside the &uart_A node in the future and providing the corresponding
> GPIOs there
Good. I didn't like the (ab)use of sdio_pwrseq GPIO resets for the
bluetooth either.
> - all the userspace commands will not be necessary once
> drivers/bluetooth/hci_bcm.c is changed to the serio framework and gets
> devicetree support
Cool. Maybe you can setup a WIP branch based on Rob's work for broader
testing on Amlogic boards until this gets merged?
In the mean time, I've applied patch 2/4 and hopefully the drivers/tty
patch will go through the serial tree.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices
Date: Wed, 18 Jan 2017 14:02:06 -0800 [thread overview]
Message-ID: <m2fukgyqld.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCC0RADEKnkYEF6_DkBTftdjmPMku+N3bdvZMCoqs96xGA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 18 Jan 2017 12:25:43 +0100")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> Kevin,
>
> On Sun, Jan 15, 2017 at 11:32 PM, Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
>> This adds the missing kernel bits for Bluetooth support on the
>> Tronsmart Vega S95 (GXBB based) boards as well as for the GXL
>> P230/P231 and GXM Q200/Q201 reference boards.
>>
>> The Bluetooth functionality on these boards is provided by the
>> SDIO wifi/Bluetooth combo-chip (Broadcom bcm43xx based). The
>> Bluetooth module on that combo-chip has to be taken out of reset,
>> which is taken care of the GPIO in the sdio_pwrseq.
>>
>> Once the module is taken out of reset it can be set up from userspace
>> using the "hciattach" tool from bluez, which talks to the Bluetooth
>> module which is connected to one of the serial ports (in our case
>> uart_A). To get the Bluetooth module initialized within the timeout
>> defined by "hciattach" (and to achieve usable speeds for Bluetooth
>> transfers) the communication uses a speed of 2000000 baud, which was
>> not supported by meson_uart before.
>>
>> NOTE: The .dts-changes from this series depends on my previous series
>> "add support for uart_AO_B" - see [0]
>>
>>
>> [0] http://lists.infradead.org/pipermail/linux-amlogic/2017-January/001982.html
>>
>>
>> Martin Blumenstingl (4):
>> tty: serial: meson: allow baud-rates higher than 115200
>> ARM64: dts: meson-gx: add the serial CTS and RTS pin groups
>
> Neil just informed me that Rob Herring is working on defining the UART
> Bluetooth device properly using devicetree (preparation for this is
> named "[PATCH v2 0/9] Serial slave device bus", see [0] for the
> mailing-list conversation and [1] for a WiP git repo).
Ah, good news. I knew Rob had been talking about that for awhile, so
I'm glad to see it coming into existence. Thanks for the pointers.
> This means that there will be a better solution than the one proposed
> in the meson-gx-p23x-q20x and meson-gxbb-vega-s95 patches (patches #1
> and #2 are not affected by this),> namely:
> - I'm currently (ab)using sdio-pwrseq node to power on the UART
> Bluetooth module, this can solved by specifying a bluetooth { } node
> inside the &uart_A node in the future and providing the corresponding
> GPIOs there
Good. I didn't like the (ab)use of sdio_pwrseq GPIO resets for the
bluetooth either.
> - all the userspace commands will not be necessary once
> drivers/bluetooth/hci_bcm.c is changed to the serio framework and gets
> devicetree support
Cool. Maybe you can setup a WIP branch based on Rob's work for broader
testing on Amlogic boards until this gets merged?
In the mean time, I've applied patch 2/4 and hopefully the drivers/tty
patch will go through the serial tree.
Kevin
next prev parent reply other threads:[~2017-01-18 22:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 22:32 [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` [PATCH 1/4] tty: serial: meson: allow baud-rates higher than 115200 Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:48 ` Andreas Färber
2017-01-15 22:48 ` Andreas Färber
2017-01-15 22:48 ` Andreas Färber
2017-01-18 21:44 ` Kevin Hilman
2017-01-18 21:44 ` Kevin Hilman
2017-01-18 21:44 ` Kevin Hilman
2017-01-15 22:32 ` [PATCH 2/4] ARM64: dts: meson-gx: add the serial CTS and RTS pin groups Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:50 ` Andreas Färber
2017-01-15 22:50 ` Andreas Färber
2017-01-15 22:50 ` Andreas Färber
2017-01-18 21:52 ` Kevin Hilman
2017-01-18 21:52 ` Kevin Hilman
2017-01-18 21:52 ` Kevin Hilman
2017-01-15 22:32 ` [PATCH 3/4] ARM64: dts: meson-gx-p23x-q20x: enable the Bluetooth module Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-16 0:47 ` Andreas Färber
2017-01-16 0:47 ` Andreas Färber
2017-01-16 0:47 ` Andreas Färber
2017-01-16 9:44 ` Martin Blumenstingl
2017-01-16 9:44 ` Martin Blumenstingl
2017-01-16 9:44 ` Martin Blumenstingl
2017-01-15 22:32 ` [PATCH 4/4] ARM64: dts: meson-gxbb-vega-s95: " Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:32 ` Martin Blumenstingl
2017-01-15 22:55 ` Andreas Färber
2017-01-15 22:55 ` Andreas Färber
2017-01-15 22:55 ` Andreas Färber
2017-01-18 11:25 ` [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices Martin Blumenstingl
2017-01-18 11:25 ` Martin Blumenstingl
2017-01-18 11:25 ` Martin Blumenstingl
2017-01-18 22:02 ` Kevin Hilman [this message]
2017-01-18 22:02 ` Kevin Hilman
2017-01-18 22:02 ` Kevin Hilman
2017-01-19 13:39 ` Greg KH
2017-01-19 13:39 ` Greg KH
2017-01-19 13:39 ` Greg KH
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=m2fukgyqld.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.