From: Adam Ford <aford173@gmail.com>
To: Linux-OMAP <linux-omap@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Philipp Puschmann <philipp.puschmann@emlix.com>
Subject: [PATCH] Bluetooth: hci_ll: set operational frequency earlier
Date: Mon, 30 Sep 2019 15:10:18 -0500 [thread overview]
Message-ID: <CAHCN7xLOCC00UC4PB3vHa6Q7yyhXVEaWgx2X9D9L2dDubd_5fA@mail.gmail.com> (raw)
Is anyone else having issues with the hci_ll after a2e02f38eff8
("Bluetooth: hci_ll: set operational frequency earlier") was applied?
I have an i.MX6Q with a WL1837MOD attached to UART2. After this patch
I git a bunch of timeouts when initializing the device using the 5.3
and 5.3.1 kernel. I know a bunch of omap and imx users have done
some various tests over the years, so I thought I'd ask.
[ 195.911836] Bluetooth: hci0: command 0xff36 tx timeout
[ 206.071837] Bluetooth: hci0: command 0x1001 tx timeout
[ 214.231862] Bluetooth: hci0: Reading TI version information failed (-110)
[ 214.238712] Bluetooth: hci0: download firmware failed, retrying...
[ 216.391834] Bluetooth: hci0: command 0xff36 tx timeout
[ 226.551843] Bluetooth: hci0: command 0x1001 tx timeout
[ 234.711856] Bluetooth: hci0: Reading TI version information failed (-110)
[ 234.718705] Bluetooth: hci0: download firmware failed, retrying...
[ 236.871832] Bluetooth: hci0: command 0xff36 tx timeout
[ 247.031837] Bluetooth: hci0: command 0x1001 tx timeout
[ 255.191852] Bluetooth: hci0: Reading TI version information failed (-110)
[ 255.198706] Bluetooth: hci0: download firmware failed, retrying...
Can't init device hci0: Connection timed out (110)
Revering this patch fixes the issue, and subsequent patch proposals
form Philipp haven't seemed to fix the issues for me on 5.3
adam
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-09-30 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 20:10 Adam Ford [this message]
2019-09-30 22:33 ` [PATCH] Bluetooth: hci_ll: set operational frequency earlier Sebastian Reichel
2019-10-01 7:04 ` Philipp Puschmann
2019-10-01 12:37 ` Adam Ford
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=CAHCN7xLOCC00UC4PB3vHa6Q7yyhXVEaWgx2X9D9L2dDubd_5fA@mail.gmail.com \
--to=aford173@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=philipp.puschmann@emlix.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).