Hi Hui, >>>>>>> The problem is: >>>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset, >>>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset, >>>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well. >>>>>>> >>>>>>> u@u-Lenovo-B4400:~$ lsusb -t >>>>>>> 1-7:1.0: No such file or directory >>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M >>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M >>>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M >>>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M >>>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>>>> >>>>>>> But if the bt module is connected to the EHCI, it always fails to play sound. >>>>>>> >>>>>>> u@u-Lenovo-B4400:~$ lsusb -t >>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M >>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M >>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M >>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M >>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M >>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M >>>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M >>>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M >>>>>> can you paste /sys/kernel/debug/usb/devices here. >>>>>> >>>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other. >>>>>> >>>>>> Try to unload the uvcvideo driver and try it again. >>>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this, >>>>> u@u-Lenovo-B4400:~$ lsusb -t >>>>> 1-1.3:1.0: No such file or directory >>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M >>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M >>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M >>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M >>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M >>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M >>>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M >>>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M >>>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M >>>>> u@u-Lenovo-B4400:~$ uname -a >>>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux >>>>> >>>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset. >>>>> And hciconfig output shows still no SCO packets received by BT driver. >>>>> u@u-Lenovo-B4400:~$ hciconfig >>>>> hci0: Type: BR/EDR Bus: USB >>>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5 >>>>> UP RUNNING PSCAN >>>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0 >>>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0 >>>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here. >>> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded. >>> >>> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq >>> [ 8.653635] kvm: disabled by bios >>> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00 >>> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13 >>> [ 8.717725] Registered led device: phy0-led >>> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' >>> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated >>> >>>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI. >>> Do you mean the hcidump file i just sent in my previous email. >> I do not get this. I specifically asked to run “btmon -w <file>” before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace. > > The attachment is the logfile generated by "btmon -w <file>". And the logfile was generated by below steps, > > 1) boot up the system into the ubuntu desktop > 2) open a terminal and run "sudo btmon -w ~/lenovo-m4400s-btmon.log" > 3) open bluetooth applet and click adding a new device, the bluetooth begin to scan devices > 4) power up the bt headset > 5) laptop bt module find the headset and connect it successfully > 6) open the sound applet, choose bt headset as output device, play sound, but no sound can be heard from bt headset > 7) Ctrl+C to terminate the "btmon -w <file>" > > In case you can't receive the attachment, i decode the logfile and paste the content here. what I need is to see the 7260 controller init. So you need to start btmon -w <file> before the 7260 gets attached to the USB bus or before btusb.ko driver gets loaded. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
