* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] [not found] ` <20161018224259.jrwbaal27irzjqyo@earth> @ 2016-10-19 9:25 ` Pavel Machek 2016-12-14 12:21 ` Pali Rohár 0 siblings, 1 reply; 7+ messages in thread From: Pavel Machek @ 2016-10-19 9:25 UTC (permalink / raw) To: linux-arm-kernel Hi! [Ccing lists.] > Can you push the patch, which gets further than negotiation into > some git branch available to me? I tried to apply your patch to > my code, but it did not work for me. Ok, I've pushed the branch to kernel.org: git push git at gitolite.kernel.org:pub/scm/linux/kernel/git/pavel/linux-n900.git bt-2-v4.9:bt-2-v4.9 In retrospect, I did make some changes to dts, they may be neccessary, too. If it still does not work, please try with my .config. I'm using modules here, using this script: pavel at n900:/my/modules$ cat run2 echo removing... sudo killall a.out rmmod nokia_h4p #rmmod omap_serial #rmmod serial_core rmmod hci_uart.ko #rmmod bcm2048.ko echo installing... insmod serial_core.ko insmod omap-serial.ko insmod bcm2048.ko insmod hci_uart.ko ls -al /dev/ttyO1 sleep 1 stty crtscts < /dev/ttyO1 /my/tui/ofone/a.out & For the record, dmesg says: Good luck, Pavel [ 30.694274] g_ether gadget: notify connect true [ 30.714080] g_ether gadget: notify speed 425984000 [ 127.719146] ssi-protocol ssi-protocol: WAKELINES TEST OK [ 218.542694] of_get_named_gpiod_flags: can't parse 'rts-gpio' property of node '/ocp at 68000000/serial at 4806c000[0]' [ 218.546264] 4806c000.serial: ttyO1 at MMIO 0x4806c000 (irq = 89, base_baud = 3000000) is a OMAP UART1 [ 218.574157] of_get_named_gpiod_flags: can't parse 'rts-gpio' property of node '/ocp at 68000000/serial at 49020000[0]' [ 218.574340] 49020000.serial: ttyO2 at MMIO 0x49020000 (irq = 90, base_baud = 3000000) is a OMAP UART2 [ 218.650115] bcm2048: probe [ 218.650177] bcm2048 4806c000.serial:bluetooth: GPIO lookup for consumer reset [ 218.650177] bcm2048 4806c000.serial:bluetooth: using device tree for GPIO lookup [ 218.650360] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/ocp at 68000000/serial at 4806c000/bluetooth[0]' - status (0) [ 218.650390] bcm2048 4806c000.serial:bluetooth: GPIO lookup for consumer host-wakeup [ 218.650421] bcm2048 4806c000.serial:bluetooth: using device tree for GPIO lookup [ 218.650482] of_get_named_gpiod_flags: parsed 'host-wakeup-gpios' property of node '/ocp at 68000000/serial at 4806c000/bluetooth[0]' - status (0) [ 218.650512] bcm2048 4806c000.serial:bluetooth: GPIO lookup for consumer bluetooth-wakeup [ 218.650543] bcm2048 4806c000.serial:bluetooth: using device tree for GPIO lookup [ 218.650604] of_get_named_gpiod_flags: parsed 'bluetooth-wakeup-gpios' property of node '/ocp at 68000000/serial@4806c000/bluetooth[0]' - status (0) [ 218.650817] bcm2048 4806c000.serial:bluetooth: parent uart: ttyO1 [ 218.650817] bcm2048 4806c000.serial:bluetooth: sysclk speed: 38400 kHz [ 218.650848] bcm2048 4806c000.serial:bluetooth: probe: 0 [ 218.774139] Bluetooth: HCI UART driver ver 2.3 [ 218.774169] Bluetooth: HCI UART protocol H4 registered [ 218.774169] Bluetooth: HCI UART protocol H4+ registered [ 218.774169] Bluetooth: HCI UART protocol BCSP registered [ 218.774200] Bluetooth: HCI UART protocol LL registered [ 218.774200] Bluetooth: HCI UART protocol ATH3K registered [ 218.774200] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 219.904876] tty ttyO1: Nokia H4+ protocol initialized with 4806c000.serial:bluetooth! [ 219.921112] tty ttyO1: Nokia H4+ protocol setup... [ 219.921142] h4p_reset: reset [ 219.921142] hci_uart_init_tty [ 219.983520] h4p_reset: flush [ 219.983551] h4p_reset: speed [ 219.983581] tty ttyO1: setting speed to 120000 baud [ 219.983673] h4p_reset: safety [ 219.986480] tty ttyO1: wakeup received: 0 -> 1 [ 220.013488] tty ttyO1: wait for cts... received! [ 220.013519] h4p_reset: flow [ 220.013549] tty ttyO1: Sending negotiation... [ 220.013580] tty ttyO1: gpio state: reset=1 wakehost=1 wakebt=1 [ 220.013610] enqueue: hu c304cc80 skb cd4da000 [ 220.017425] tty ttyO1: H4P negotiation: [ 220.017456] tty ttyO1: baudrate = 416 [ 220.017486] tty ttyO1: system clock = 38400 [ 220.017486] tty ttyO1: manufacturer id = 4 [ 220.017486] tty ttyO1: version id = 11 [ 220.017578] tty ttyO1: setting speed to 921600 baud [ 220.043457] tty ttyO1: wait for cts... received! [ 220.043548] tty ttyO1: Negotiation successful... [ 220.043579] tty ttyO1: Sending alive packet... [ 220.043579] enqueue: hu c304cc80 skb cd4dacc0 [ 220.043853] tty ttyO1: Received alive packet! [ 220.047851] tty ttyO1: FW: Skip negotion packet! [ 220.047882] tty ttyO1: FW: Skip alive packet! [ 220.052185] enqueue: hu c304cc80 skb cd4da480 [ 220.055175] enqueue: hu c304cc80 skb cd4dae40 [ 220.058776] enqueue: hu c304cc80 skb cd4da6c0 [ 220.058898] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.058929] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.064605] enqueue: hu c304cc80 skb cd4daf00 [ 220.068389] enqueue: hu c304cc80 skb cd4da0c0 [ 220.068542] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.068542] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.071960] enqueue: hu c304cc80 skb cd4da840 [ 220.072082] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.072082] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.075592] enqueue: hu c304cc80 skb cd4da180 [ 220.079803] enqueue: hu c304cc80 skb cd479cc0 [ 220.084381] enqueue: hu c304cc80 skb cd479180 [ 220.087982] enqueue: hu c304cc80 skb cd4793c0 [ 220.088104] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.088134] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.091522] enqueue: hu c304cc80 skb cd479e40 [ 220.095336] enqueue: hu c304cc80 skb cd479540 [ 220.098876] enqueue: hu c304cc80 skb cd479000 [ 220.102386] enqueue: hu c304cc80 skb cd479600 [ 220.102478] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.102508] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.105987] enqueue: hu c304cc80 skb cd479780 [ 220.109527] enqueue: hu c304cc80 skb cd450cc0 [ 220.109619] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.109649] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.113098] enqueue: hu c304cc80 skb cd484600 [ 220.113220] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.113250] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.116760] enqueue: hu c304cc80 skb cd4a9b40 [ 220.120300] enqueue: hu c304cc80 skb cd77c840 [ 220.124786] enqueue: hu c304cc80 skb cd4f7900 [ 220.128387] enqueue: hu c304cc80 skb c4fb2180 [ 220.131896] enqueue: hu c304cc80 skb c4fb23c0 [ 220.135498] enqueue: hu c304cc80 skb c4fb2cc0 [ 220.139007] enqueue: hu c304cc80 skb c4fb2000 [ 220.142486] enqueue: hu c304cc80 skb cd44fcc0 [ 220.146118] enqueue: hu c304cc80 skb cd4b60c0 [ 220.149627] enqueue: hu c304cc80 skb cf1986c0 [ 220.153106] enqueue: hu c304cc80 skb cf198480 [ 220.156738] enqueue: hu c304cc80 skb cf1980c0 [ 220.160278] enqueue: hu c304cc80 skb cf198240 [ 220.164733] enqueue: hu c304cc80 skb cd49f780 [ 220.168365] enqueue: hu c304cc80 skb cd4daf00 [ 220.171844] enqueue: hu c304cc80 skb cd4da6c0 [ 220.175445] enqueue: hu c304cc80 skb cd4dab40 [ 220.175567] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.175567] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.178955] enqueue: hu c304cc80 skb cd479780 [ 220.182434] enqueue: hu c304cc80 skb cd479540 [ 220.182525] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.182556] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.186035] enqueue: hu c304cc80 skb cd4793c0 [ 220.188140] enqueue: hu c304cc80 skb cd479b40 [ 220.188537] enqueue: hu c304cc80 skb cd484600 [ 220.236480] enqueue: hu c304cc80 skb cd4a9f00 [ 220.237701] enqueue: hu c304cc80 skb cd4f7900 [ 220.238830] enqueue: hu c304cc80 skb c4fb23c0 [ 220.239959] enqueue: hu c304cc80 skb c4fb2b40 [ 220.241119] enqueue: hu c304cc80 skb c3107000 [ 220.242187] enqueue: hu c304cc80 skb cd724240 [ 220.243286] enqueue: hu c304cc80 skb cf198540 [ 220.244781] enqueue: hu c304cc80 skb cf198540 [ 220.245758] enqueue: hu c304cc80 skb cd49f780 [ 220.246612] enqueue: hu c304cc80 skb cd4daf00 [ 220.247436] enqueue: hu c304cc80 skb cd479540 [ 220.248535] tty ttyO1: Sending radio packet... [ 220.248565] enqueue: hu c304cc80 skb cd479cc0 [ 220.248596] tty ttyO1: Radio packet sent [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 [ 221.283477] tty ttyO1: radio packet timeout! [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout pavel at n900:~$ -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161019/4903439f/attachment-0001.sig> ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-10-19 9:25 ` partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] Pavel Machek @ 2016-12-14 12:21 ` Pali Rohár 2016-12-14 12:53 ` Pavel Machek 0 siblings, 1 reply; 7+ messages in thread From: Pali Rohár @ 2016-12-14 12:21 UTC (permalink / raw) To: linux-arm-kernel On Wednesday 19 October 2016 11:25:06 Pavel Machek wrote: > Hi! > > [Ccing lists.] > > > Can you push the patch, which gets further than negotiation into > > some git branch available to me? I tried to apply your patch to > > my code, but it did not work for me. > > Ok, I've pushed the branch to kernel.org: > > git push > git at gitolite.kernel.org:pub/scm/linux/kernel/git/pavel/linux-n900.gi > t bt-2-v4.9:bt-2-v4.9 > > In retrospect, I did make some changes to dts, they may be > neccessary, too. > > If it still does not work, please try with my .config. I'm using > modules here, using this script: > > pavel at n900:/my/modules$ cat run2 > echo removing... > sudo killall a.out > rmmod nokia_h4p > #rmmod omap_serial > #rmmod serial_core > rmmod hci_uart.ko > #rmmod bcm2048.ko > echo installing... > insmod serial_core.ko > insmod omap-serial.ko > insmod bcm2048.ko > insmod hci_uart.ko > ls -al /dev/ttyO1 > sleep 1 > stty crtscts < /dev/ttyO1 > /my/tui/ofone/a.out & > > For the record, dmesg says: > > Good luck, > Pavel > > [ 30.694274] g_ether gadget: notify connect true > [ 30.714080] g_ether gadget: notify speed 425984000 > [ 127.719146] ssi-protocol ssi-protocol: WAKELINES TEST OK > [ 218.542694] of_get_named_gpiod_flags: can't parse 'rts-gpio' > property of node '/ocp at 68000000/serial at 4806c000[0]' > [ 218.546264] 4806c000.serial: ttyO1 at MMIO 0x4806c000 (irq = 89, > base_baud = 3000000) is a OMAP UART1 > [ 218.574157] of_get_named_gpiod_flags: can't parse 'rts-gpio' > property of node '/ocp at 68000000/serial at 49020000[0]' > [ 218.574340] 49020000.serial: ttyO2 at MMIO 0x49020000 (irq = 90, > base_baud = 3000000) is a OMAP UART2 > [ 218.650115] bcm2048: probe > [ 218.650177] bcm2048 4806c000.serial:bluetooth: GPIO lookup for > consumer reset > [ 218.650177] bcm2048 4806c000.serial:bluetooth: using device tree > for GPIO lookup > [ 218.650360] of_get_named_gpiod_flags: parsed 'reset-gpios' > property of node '/ocp at 68000000/serial at 4806c000/bluetooth[0]' - > status (0) [ 218.650390] bcm2048 4806c000.serial:bluetooth: GPIO > lookup for consumer host-wakeup > [ 218.650421] bcm2048 4806c000.serial:bluetooth: using device tree > for GPIO lookup > [ 218.650482] of_get_named_gpiod_flags: parsed 'host-wakeup-gpios' > property of node '/ocp at 68000000/serial at 4806c000/bluetooth[0]' - > status (0) > [ 218.650512] bcm2048 4806c000.serial:bluetooth: GPIO lookup for > consumer bluetooth-wakeup > [ 218.650543] bcm2048 4806c000.serial:bluetooth: using device tree > for GPIO lookup > [ 218.650604] of_get_named_gpiod_flags: parsed > 'bluetooth-wakeup-gpios' property of node > '/ocp at 68000000/serial at 4806c000/bluetooth[0]' - status (0) > [ 218.650817] bcm2048 4806c000.serial:bluetooth: parent uart: ttyO1 > [ 218.650817] bcm2048 4806c000.serial:bluetooth: sysclk speed: 38400 > kHz > [ 218.650848] bcm2048 4806c000.serial:bluetooth: probe: 0 > [ 218.774139] Bluetooth: HCI UART driver ver 2.3 > [ 218.774169] Bluetooth: HCI UART protocol H4 registered > [ 218.774169] Bluetooth: HCI UART protocol H4+ registered > [ 218.774169] Bluetooth: HCI UART protocol BCSP registered > [ 218.774200] Bluetooth: HCI UART protocol LL registered > [ 218.774200] Bluetooth: HCI UART protocol ATH3K registered > [ 218.774200] Bluetooth: HCI UART protocol Three-wire (H5) > registered [ 219.904876] tty ttyO1: Nokia H4+ protocol initialized > with 4806c000.serial:bluetooth! > [ 219.921112] tty ttyO1: Nokia H4+ protocol setup... > [ 219.921142] h4p_reset: reset > [ 219.921142] hci_uart_init_tty > [ 219.983520] h4p_reset: flush > [ 219.983551] h4p_reset: speed > [ 219.983581] tty ttyO1: setting speed to 120000 baud > [ 219.983673] h4p_reset: safety > [ 219.986480] tty ttyO1: wakeup received: 0 -> 1 > [ 220.013488] tty ttyO1: wait for cts... received! > [ 220.013519] h4p_reset: flow > [ 220.013549] tty ttyO1: Sending negotiation... > [ 220.013580] tty ttyO1: gpio state: reset=1 wakehost=1 wakebt=1 > [ 220.013610] enqueue: hu c304cc80 skb cd4da000 > [ 220.017425] tty ttyO1: H4P negotiation: > [ 220.017456] tty ttyO1: baudrate = 416 > [ 220.017486] tty ttyO1: system clock = 38400 > [ 220.017486] tty ttyO1: manufacturer id = 4 > [ 220.017486] tty ttyO1: version id = 11 > [ 220.017578] tty ttyO1: setting speed to 921600 baud > [ 220.043457] tty ttyO1: wait for cts... received! > [ 220.043548] tty ttyO1: Negotiation successful... > [ 220.043579] tty ttyO1: Sending alive packet... > [ 220.043579] enqueue: hu c304cc80 skb cd4dacc0 > [ 220.043853] tty ttyO1: Received alive packet! > [ 220.047851] tty ttyO1: FW: Skip negotion packet! > [ 220.047882] tty ttyO1: FW: Skip alive packet! > [ 220.052185] enqueue: hu c304cc80 skb cd4da480 > [ 220.055175] enqueue: hu c304cc80 skb cd4dae40 > [ 220.058776] enqueue: hu c304cc80 skb cd4da6c0 > [ 220.058898] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.058929] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.064605] enqueue: hu c304cc80 skb cd4daf00 > [ 220.068389] enqueue: hu c304cc80 skb cd4da0c0 > [ 220.068542] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.068542] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.071960] enqueue: hu c304cc80 skb cd4da840 > [ 220.072082] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.072082] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.075592] enqueue: hu c304cc80 skb cd4da180 > [ 220.079803] enqueue: hu c304cc80 skb cd479cc0 > [ 220.084381] enqueue: hu c304cc80 skb cd479180 > [ 220.087982] enqueue: hu c304cc80 skb cd4793c0 > [ 220.088104] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.088134] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.091522] enqueue: hu c304cc80 skb cd479e40 > [ 220.095336] enqueue: hu c304cc80 skb cd479540 > [ 220.098876] enqueue: hu c304cc80 skb cd479000 > [ 220.102386] enqueue: hu c304cc80 skb cd479600 > [ 220.102478] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.102508] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.105987] enqueue: hu c304cc80 skb cd479780 > [ 220.109527] enqueue: hu c304cc80 skb cd450cc0 > [ 220.109619] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.109649] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.113098] enqueue: hu c304cc80 skb cd484600 > [ 220.113220] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.113250] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.116760] enqueue: hu c304cc80 skb cd4a9b40 > [ 220.120300] enqueue: hu c304cc80 skb cd77c840 > [ 220.124786] enqueue: hu c304cc80 skb cd4f7900 > [ 220.128387] enqueue: hu c304cc80 skb c4fb2180 > [ 220.131896] enqueue: hu c304cc80 skb c4fb23c0 > [ 220.135498] enqueue: hu c304cc80 skb c4fb2cc0 > [ 220.139007] enqueue: hu c304cc80 skb c4fb2000 > [ 220.142486] enqueue: hu c304cc80 skb cd44fcc0 > [ 220.146118] enqueue: hu c304cc80 skb cd4b60c0 > [ 220.149627] enqueue: hu c304cc80 skb cf1986c0 > [ 220.153106] enqueue: hu c304cc80 skb cf198480 > [ 220.156738] enqueue: hu c304cc80 skb cf1980c0 > [ 220.160278] enqueue: hu c304cc80 skb cf198240 > [ 220.164733] enqueue: hu c304cc80 skb cd49f780 > [ 220.168365] enqueue: hu c304cc80 skb cd4daf00 > [ 220.171844] enqueue: hu c304cc80 skb cd4da6c0 > [ 220.175445] enqueue: hu c304cc80 skb cd4dab40 > [ 220.175567] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.175567] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.178955] enqueue: hu c304cc80 skb cd479780 > [ 220.182434] enqueue: hu c304cc80 skb cd479540 > [ 220.182525] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.182556] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.186035] enqueue: hu c304cc80 skb cd4793c0 > [ 220.188140] enqueue: hu c304cc80 skb cd479b40 > [ 220.188537] enqueue: hu c304cc80 skb cd484600 > [ 220.236480] enqueue: hu c304cc80 skb cd4a9f00 > [ 220.237701] enqueue: hu c304cc80 skb cd4f7900 > [ 220.238830] enqueue: hu c304cc80 skb c4fb23c0 > [ 220.239959] enqueue: hu c304cc80 skb c4fb2b40 > [ 220.241119] enqueue: hu c304cc80 skb c3107000 > [ 220.242187] enqueue: hu c304cc80 skb cd724240 > [ 220.243286] enqueue: hu c304cc80 skb cf198540 > [ 220.244781] enqueue: hu c304cc80 skb cf198540 > [ 220.245758] enqueue: hu c304cc80 skb cd49f780 > [ 220.246612] enqueue: hu c304cc80 skb cd4daf00 > [ 220.247436] enqueue: hu c304cc80 skb cd479540 > [ 220.248535] tty ttyO1: Sending radio packet... > [ 220.248565] enqueue: hu c304cc80 skb cd479cc0 > [ 220.248596] tty ttyO1: Radio packet sent > [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) > [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 > [ 221.283477] tty ttyO1: radio packet timeout! > [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 > [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout > pavel at n900:~$ In log are still some failures, but ... is bluetooth working now? I see that you applied this patch: https://git.kernel.org/cgit/linux/kernel/git/pavel/linux-n900.git/commit/?id=051aa3fbf03ac770d8344690f5a936a7f04c6884 Looks like that pinmux is in DTS file incorrect. Can somebody verify it? Maybe Tony? -- Pali Roh?r pali.rohar at gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161214/d223c86e/attachment.sig> ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-12-14 12:21 ` Pali Rohár @ 2016-12-14 12:53 ` Pavel Machek 2016-12-14 13:31 ` Sebastian Reichel 0 siblings, 1 reply; 7+ messages in thread From: Pavel Machek @ 2016-12-14 12:53 UTC (permalink / raw) To: linux-arm-kernel Hi! > > [ 220.248596] tty ttyO1: Radio packet sent > > [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) > > [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 > > [ 221.283477] tty ttyO1: radio packet timeout! > > [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 > > [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout > > pavel at n900:~$ > > In log are still some failures, but ... is bluetooth working now? It is... for Sebastian. I'm playing with camera now. > I see that you applied this patch: > https://git.kernel.org/cgit/linux/kernel/git/pavel/linux-n900.git/commit/?id=051aa3fbf03ac770d8344690f5a936a7f04c6884 > > Looks like that pinmux is in DTS file incorrect. Can somebody verify it? > Maybe Tony? Yes, it is. Sebastian was pretty certain about that. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161214/615b77da/attachment-0001.sig> ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-12-14 12:53 ` Pavel Machek @ 2016-12-14 13:31 ` Sebastian Reichel 2016-12-14 15:10 ` Tony Lindgren 0 siblings, 1 reply; 7+ messages in thread From: Sebastian Reichel @ 2016-12-14 13:31 UTC (permalink / raw) To: linux-arm-kernel Hi Pali & Pavel, On Wed, Dec 14, 2016 at 01:53:23PM +0100, Pavel Machek wrote: > > > [ 220.248596] tty ttyO1: Radio packet sent > > > [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) > > > [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 > > > [ 221.283477] tty ttyO1: radio packet timeout! > > > [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 > > > [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout > > > pavel at n900:~$ > > > > In log are still some failures, but ... is bluetooth working now? I could scan for devices. The code is still racy, though. It's most likely related to the newly introduced idle code. (Without sending the BT module to correctly idle the bcm2048 does not work correctly at all) I was quite busy the last few weeks and did not manage to find much time for kernel work. Now I will first have to catch up with my power-supply tree. > It is... for Sebastian. I'm playing with camera now. > > > I see that you applied this patch: > > https://git.kernel.org/cgit/linux/kernel/git/pavel/linux-n900.git/commit/?id=051aa3fbf03ac770d8344690f5a936a7f04c6884 > > > > Looks like that pinmux is in DTS file incorrect. Can somebody verify it? > > Maybe Tony? > > Yes, it is. Sebastian was pretty certain about that. Yes, I'm certain. The bootloader enables the pullup resistors. Note, that the wrong DTS entry is not in mainline. My bluetooth branch has a fixed DTS patch instead of a fixup patch on top of the broken one: https://git.kernel.org/cgit/linux/kernel/git/sre/linux-n900.git/commit/?h=nokia-bluetooth-dev&id=6b63c111a979d100cfbdd76cb4a6bbadace35216 -- Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161214/28d87fe2/attachment.sig> ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-12-14 13:31 ` Sebastian Reichel @ 2016-12-14 15:10 ` Tony Lindgren 2016-12-14 15:52 ` Sebastian Reichel 0 siblings, 1 reply; 7+ messages in thread From: Tony Lindgren @ 2016-12-14 15:10 UTC (permalink / raw) To: linux-arm-kernel * Sebastian Reichel <sre@kernel.org> [161214 05:32]: > Hi Pali & Pavel, > > On Wed, Dec 14, 2016 at 01:53:23PM +0100, Pavel Machek wrote: > > > > [ 220.248596] tty ttyO1: Radio packet sent > > > > [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) > > > > [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 > > > > [ 221.283477] tty ttyO1: radio packet timeout! > > > > [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 > > > > [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout > > > > pavel at n900:~$ > > > > > > In log are still some failures, but ... is bluetooth working now? > > I could scan for devices. The code is still racy, though. It's > most likely related to the newly introduced idle code. (Without > sending the BT module to correctly idle the bcm2048 does not > work correctly at all) > > I was quite busy the last few weeks and did not manage to find > much time for kernel work. Now I will first have to catch up > with my power-supply tree. > > > It is... for Sebastian. I'm playing with camera now. > > > > > I see that you applied this patch: > > > https://git.kernel.org/cgit/linux/kernel/git/pavel/linux-n900.git/commit/?id=051aa3fbf03ac770d8344690f5a936a7f04c6884 > > > > > > Looks like that pinmux is in DTS file incorrect. Can somebody verify it? > > > Maybe Tony? > > > > Yes, it is. Sebastian was pretty certain about that. > > Yes, I'm certain. The bootloader enables the pullup resistors. > Note, that the wrong DTS entry is not in mainline. My bluetooth > branch has a fixed DTS patch instead of a fixup patch on top of > the broken one: > > https://git.kernel.org/cgit/linux/kernel/git/sre/linux-n900.git/commit/?h=nokia-bluetooth-dev&id=6b63c111a979d100cfbdd76cb4a6bbadace35216 Maybe send it so we can merge it as a fix during the early -rc cycle? Regards, Tony ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-12-14 15:10 ` Tony Lindgren @ 2016-12-14 15:52 ` Sebastian Reichel 2016-12-14 16:02 ` Tony Lindgren 0 siblings, 1 reply; 7+ messages in thread From: Sebastian Reichel @ 2016-12-14 15:52 UTC (permalink / raw) To: linux-arm-kernel Hi Tony, On Wed, Dec 14, 2016 at 07:10:56AM -0800, Tony Lindgren wrote: > * Sebastian Reichel <sre@kernel.org> [161214 05:32]: > > Hi Pali & Pavel, > > > > On Wed, Dec 14, 2016 at 01:53:23PM +0100, Pavel Machek wrote: > > > > > [ 220.248596] tty ttyO1: Radio packet sent > > > > > [ 220.249328] Bluetooth: hci0: Frame reassembly failed (-84) > > > > > [ 220.272949] tty ttyO1: wakeup received: 1 -> 0 > > > > > [ 221.283477] tty ttyO1: radio packet timeout! > > > > > [ 221.283630] enqueue: hu c304cc80 skb cd4a9b40 > > > > > [ 223.363372] Bluetooth: hci0 command 0xfc18 tx timeout > > > > > pavel at n900:~$ > > > > > > > > In log are still some failures, but ... is bluetooth working now? > > > > I could scan for devices. The code is still racy, though. It's > > most likely related to the newly introduced idle code. (Without > > sending the BT module to correctly idle the bcm2048 does not > > work correctly at all) > > > > I was quite busy the last few weeks and did not manage to find > > much time for kernel work. Now I will first have to catch up > > with my power-supply tree. > > > > > It is... for Sebastian. I'm playing with camera now. > > > > > > > I see that you applied this patch: > > > > https://git.kernel.org/cgit/linux/kernel/git/pavel/linux-n900.git/commit/?id=051aa3fbf03ac770d8344690f5a936a7f04c6884 > > > > > > > > Looks like that pinmux is in DTS file incorrect. Can somebody verify it? > > > > Maybe Tony? > > > > > > Yes, it is. Sebastian was pretty certain about that. > > > > Yes, I'm certain. The bootloader enables the pullup resistors. > > Note, that the wrong DTS entry is not in mainline. My bluetooth > > branch has a fixed DTS patch instead of a fixup patch on top of > > the broken one: > > > > https://git.kernel.org/cgit/linux/kernel/git/sre/linux-n900.git/commit/?h=nokia-bluetooth-dev&id=6b63c111a979d100cfbdd76cb4a6bbadace35216 > > Maybe send it so we can merge it as a fix during the early -rc > cycle? Sorry if I was not clear enough: mainline does *not* contain incorrect DT information. My bluetooth RFC patches did. So this can go into the kernel once the driver is there and the binding got accepted. Alternatively I can prepare a patch, which just adds the cts/rts pinmux for the bluetooth UART, but it's not very useful on its own. -- Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161214/5d0c089d/attachment.sig> ^ permalink raw reply [flat|nested] 7+ messages in thread
* partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] 2016-12-14 15:52 ` Sebastian Reichel @ 2016-12-14 16:02 ` Tony Lindgren 0 siblings, 0 replies; 7+ messages in thread From: Tony Lindgren @ 2016-12-14 16:02 UTC (permalink / raw) To: linux-arm-kernel * Sebastian Reichel <sre@kernel.org> [161214 07:52]: > On Wed, Dec 14, 2016 at 07:10:56AM -0800, Tony Lindgren wrote: > > Maybe send it so we can merge it as a fix during the early -rc > > cycle? > > Sorry if I was not clear enough: mainline does *not* contain > incorrect DT information. My bluetooth RFC patches did. So > this can go into the kernel once the driver is there and > the binding got accepted. Oh OK good to hear. > Alternatively I can prepare a patch, which just adds the > cts/rts pinmux for the bluetooth UART, but it's not very > useful on its own. OK sounds like no rush until other pieces are ready. Regards, Tony ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-12-14 16:02 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20161016002454.ul5rdqwubvkct4pf@earth>
[not found] ` <20161016090959.GA377@amd>
[not found] ` <20161016173911.arxynrja6vely3d5@earth>
[not found] ` <20161017085137.GA6628@amd>
[not found] ` <20161018224259.jrwbaal27irzjqyo@earth>
2016-10-19 9:25 ` partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] Pavel Machek
2016-12-14 12:21 ` Pali Rohár
2016-12-14 12:53 ` Pavel Machek
2016-12-14 13:31 ` Sebastian Reichel
2016-12-14 15:10 ` Tony Lindgren
2016-12-14 15:52 ` Sebastian Reichel
2016-12-14 16:02 ` Tony Lindgren
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).