From: Christian Hewitt <christianshewitt@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
khilman@baylibre.com, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/10] arm64: dts: meson-gxm-khadas-vim2: fix Bluetooth support
Date: Mon, 3 Jun 2019 15:57:17 +0400 [thread overview]
Message-ID: <CD983BAA-CC37-455E-B78A-CF8A72ACE7A4@gmail.com> (raw)
In-Reply-To: <bbf3c69f-8695-d665-c7ca-587b7e77eb4f@baylibre.com>
On 3 Jun 2019, at 12:57 pm, Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> On 29/05/2019 20:08, Martin Blumenstingl wrote:
>> On Wed, May 29, 2019 at 12:25 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>>
>>> On 27/05/2019 20:36, Martin Blumenstingl wrote:
>>>> On Mon, May 27, 2019 at 3:22 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>>>>
>>>>> From: Christian Hewitt <christianshewitt@gmail.com>
>>>>>
>>>>> - Remove serial1 alias
>>>>> - Add support for uart_A rts/cts
>>>>> - Add bluetooth uart_A subnode qith shutdown gpio
>>>> I tried this on my own Khadas VIM2:
>>>> Bluetooth: hci0: command 0x1001 tx timeout
>>>> Bluetooth: hci0: BCM: Reading local version info failed (-110)
>>>>
>>>> I'm not sure whether this is specific to my board or what causes this.
>>>
>>> Which kernel version ?
>> 5.2-rc2
>>
>> it's a Khadas VIM2 Basic (thus it has a AP6356S), board revision v1.2
>
> Can you try with :
>
> clocks = <&wifi32k>;
> clock-names = "lpo";
>
> added in the bluetooth node ?
Tested and confirmed working with rev 1.2 ‘basic' and 5.1 kernel with those nodes added.
VIM2:~ # dmesg | grep -i blue
[ 10.793600] Bluetooth: Core ver 2.22
[ 10.793792] Bluetooth: HCI device and connection manager initialized
[ 10.793814] Bluetooth: HCI socket layer initialized
[ 10.793821] Bluetooth: L2CAP socket layer initialized
[ 10.793851] Bluetooth: SCO socket layer initialized
[ 10.801928] Bluetooth: HCI UART driver ver 2.3
[ 10.801944] Bluetooth: HCI UART protocol H4 registered
[ 10.804919] Bluetooth: HCI UART protocol Broadcom registered
[ 10.805025] Bluetooth: HCI UART protocol QCA registered
[ 11.016629] Bluetooth: hci0: BCM: chip id 101
[ 11.018537] Bluetooth: hci0: BCM: features 0x2f
[ 11.043112] Bluetooth: hci0: BCM4354A2
[ 11.043134] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[ 11.075919] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 11.359784] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.359793] Bluetooth: BNEP filters: protocol multicast
[ 11.359811] Bluetooth: BNEP socket layer initialized
[ 17.075509] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266
I use BT remotes to avoid issues with multiple boards responding to IR so it was working before at some point. I assume I dropped a change somewhere in the process of feeding you the batch of patches - apologies!
Christian
next prev parent reply other threads:[~2019-06-03 11:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 13:21 [PATCH 00/10] arm64: meson-gx: misc fixes Neil Armstrong
2019-05-27 13:21 ` [PATCH 01/10] arm64: dts: meson-gxm-khadas-vim2: fix gpio-keys-polled node Neil Armstrong
2019-05-27 18:32 ` Martin Blumenstingl
2019-06-06 20:00 ` Kevin Hilman
2019-06-07 13:01 ` Neil Armstrong
2019-06-07 16:59 ` Kevin Hilman
2019-05-27 13:21 ` [PATCH 02/10] arm64: dts: meson-gxm-khadas-vim2: fix Bluetooth support Neil Armstrong
2019-05-27 18:36 ` Martin Blumenstingl
2019-05-29 10:25 ` Neil Armstrong
2019-05-29 18:08 ` Martin Blumenstingl
2019-06-03 8:57 ` Neil Armstrong
2019-06-03 11:57 ` Christian Hewitt [this message]
2019-06-06 19:52 ` Martin Blumenstingl
2019-05-27 13:21 ` [PATCH 03/10] arm64: dts: meson-gxbb-wetek: enable SARADC Neil Armstrong
2019-05-27 18:15 ` Martin Blumenstingl
2019-05-29 14:17 ` Neil Armstrong
2019-05-27 13:21 ` [PATCH 04/10] arm64: dts: meson-gxbb-wetek: enable bluetooth Neil Armstrong
2019-05-27 18:19 ` Martin Blumenstingl
2019-05-27 13:21 ` [PATCH 05/10] arm64: dts: meson-gxbb-vega-s95: fix regulators Neil Armstrong
2019-05-27 18:21 ` Martin Blumenstingl
2019-05-27 13:21 ` [PATCH 06/10] arm64: dts: meson-gxbb-vega-s95: add HDMI nodes Neil Armstrong
2019-05-27 18:23 ` Martin Blumenstingl
2019-05-27 13:21 ` [PATCH 07/10] arm64: dts: meson-gxbb-vega-s95: enable CEC Neil Armstrong
2019-05-27 18:22 ` Martin Blumenstingl
2019-05-27 13:21 ` [PATCH 08/10] arm64: dts: meson-gxbb-vega-s95: enable SARADC Neil Armstrong
2019-05-27 18:24 ` Martin Blumenstingl
2019-05-29 14:17 ` Neil Armstrong
2019-05-27 13:21 ` [PATCH 09/10] arm64: dts: meson-gxbb-vega-s95: fix WiFi/BT module support Neil Armstrong
2019-05-27 18:27 ` Martin Blumenstingl
2019-05-27 13:22 ` [PATCH 10/10] arm64: dts: meson-gxbb-vega-s95: add ethernet PHY interrupt Neil Armstrong
2019-05-27 18:25 ` Martin Blumenstingl
2019-06-03 22:25 ` [PATCH 00/10] arm64: meson-gx: misc fixes Kevin Hilman
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=CD983BAA-CC37-455E-B78A-CF8A72ACE7A4@gmail.com \
--to=christianshewitt@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
/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;
as well as URLs for NNTP newsgroup(s).