lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAHCN7x+Mq=b6RN-ezU0400W=H=D7DR+Es1FHtT4GyozpVd8ALA@mail.gmail.com> Date: Fri, 5 May 2017 09:51:33 -0500 From: Adam Ford <aford173@...il.com> To: Sebastian Reichel <sre@...nel.org> Cc: Rob Herring <robh@...nel.org>, Marcel Holtmann <marcel@...tmann.org>, linux-bluetooth@...r.kernel.org, Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org, Johan Hedberg <johan.hedberg@...il.com>, Gustavo Padovan <gustavo@...ovan.org>, Satish Patel <satish.patel@...aro.org>, Wei Xu <xuwei5@...ilicon.com>, Eyal Reizer <eyalr@...com>, netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 0/4] TI Bluetooth serdev support On Sun, Apr 30, 2017 at 11:04 AM, Sebastian Reichel <sre@...nel.org> wrote: > Hi, > > On Sun, Apr 30, 2017 at 10:14:20AM -0500, Adam Ford wrote: >> On Wed, Apr 5, 2017 at 1:30 PM, Rob Herring <robh@...nel.org> wrote: >> > This series adds serdev support to the HCI LL protocol used on TI BT >> > modules and enables support on HiKey board with with the WL1835 module. >> > With this the custom TI UIM daemon and btattach are no longer needed. >> >> Without UIM daemon, what instruction do you use to load the BT firmware? >> >> I was thinking 'hciattach' but I was having trouble. I was hoping you >> might have some insight. >> >> hciattach -t 30 -s 115200 /dev/ttymxc1 texas 3000000 flow Just >> returns a timeout. >> >> I modified my i.MX6 device tree per the binding documentation and >> setup the regulators and enable GPIO pins. > > If you configured everything correctly no userspace interaction is > required. The driver should request the firmware automatically once > you power up the bluetooth device. > > Apart from DT changes make sure, that the following options are > enabled and check dmesg for any hints. > > CONFIG_SERIAL_DEV_BUS > CONFIG_SERIAL_DEV_CTRL_TTYPORT > CONFIG_BT_HCIUART > CONFIG_BT_HCIUART_LL > I have enabled those flags, and I have updated my device tree. I am testing this on an OMAP3630 (DM3730) board with a WL1283. I am getting a lot of timeout errors. I tested this against the original implemention I had in pdata-quirks.c using the ti-st driver, uim & and the btwilink driver. I pulled in some of the newer patches to enable the wl1283-st, but I am obviously missing something. I 58.717651] Bluetooth: hci0: Reading TI version information failed (-110) [ 58.724853] Bluetooth: hci0: download firmware failed, retrying... [ 60.957641] Bluetooth: hci0 command 0x1001 tx timeout [ 68.957641] Bluetooth: hci0: Reading TI version information failed (-110) [ 68.964843] Bluetooth: hci0: download firmware failed, retrying... [ 69.132171] Bluetooth: Unknown HCI packet type 06 [ 69.138244] Bluetooth: Unknown HCI packet type 0c [ 69.143249] Bluetooth: Unknown HCI packet type 40 [ 69.148498] Bluetooth: Unknown HCI packet type 20 [ 69.153533] Bluetooth: Data length is too large [ 69.158569] Bluetooth: Unknown HCI packet type a0 [ 69.163574] Bluetooth: Unknown HCI packet type 00 [ 69.168731] Bluetooth: Unknown HCI packet type 00 [ 69.173736] Bluetooth: Unknown HCI packet type 34 [ 69.178924] Bluetooth: Unknown HCI packet type 91 [ 71.197631] Bluetooth: hci0 command 0x1001 tx timeout [ 79.197662] Bluetooth: hci0: Reading TI version information failed (-110) Since the pdata-quirks and original ti-st drivers work together, I know the hardware is fine. The only change to the device tree is the addition of the Bluetooth container: bluetooth { compatible = "ti,wl1283-st"; enable-gpios = <&gpio6 2 GPIO_ACTIVE_HIGH>; }; Any thoughts or suggestions to try? I get similar behavior on an i.MX6 board with a wl1837-st module as well. adam > -- Sebastian
Powered by blists - more mailing lists