Hi,
On Mon, Sep 30, 2019 at 03:10:18PM -0500, Adam Ford wrote:
> 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)
I can see the same messages on OMAP4+WL1285 based Motorola Droid 4
(with the same commands resulting in a timeout).
> Revering this patch fixes the issue,
Ack.
> and subsequent patch proposals form Philipp haven't seemed
> to fix the issues for me on 5.3.
I did not do any further tests, just noticed this while working
on another patchset.
-- Sebastian
Attachment:
signature.asc
Description: PGP signature
