Tricky way to force rtk_btusb driver work.

[NickNamerr]

Kernel version 3.0.35
WiFi part of device is working properly and stable.
actually my 0x8723 bluetooth is working , but tricky.
if just insmod compiled from master repository driver , the device is appearing in hcitool dev, but could not see any device in hcitool scan.

So, I switched branch to 'new' and compiled driver from 'Linux_BT_USB_2.11.20140423_8723BE' folder, then insmod it and received:

[ 885.951900] rtk_btusb: download_data done
[ 885.952264] fsl-ehci fsl-ehci.1: reused qh e45d1600 schedule
[ 885.952291] usb 2-1: link qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.953844] usb 2-1: unlink qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.953882] rtk_btusb: check_fw_version : read_ver_rsp->lmp_subver = 0x9f73
[ 885.953901] rtk_btusb: check_fw_version : patch_entry->lmp_sub = 0x8723
[ 885.953926] rtk_btusb: Rtk patch end 0
[ 885.953989] fsl-ehci fsl-ehci.1: reused qh e45d1600 schedule
[ 885.954012] usb 2-1: link qh1-0001/e45d1600 start 0 [1/0 us]
[ 885.954316] rtk_btusb: btusb_open end pm_usage_cnt(0x0)
[ 886.952479] hci_cmd_timer: hci0 command tx timeout
[ 887.962477] hci_cmd_timer: hci0 command tx timeout
[ 888.972483] hci_cmd_timer: hci0 command tx timeout
[ 889.982478] hci_cmd_timer: hci0 command tx timeout
[ 890.992479] hci_cmd_timer: hci0 command tx timeout
[ 892.002480] hci_cmd_timer: hci0 command tx timeout
[ 893.012478] hci_cmd_timer: hci0 command tx timeout
[ 894.022479] hci_cmd_timer: hci0 command tx timeout
[ 895.032478] hci_cmd_timer: hci0 command tx timeout
[ 895.952509] rtk_btusb: btusb_flush add delay
[ 895.962547] rtk_btusb: btusb_close
[ 895.972851] usb 2-1: unlink qh1-0001/e45d1600 start 0 [1/0 us]
[ 896.042460] hci_cmd_timer: hci0 command tx timeout

after I did rmmod this driver and immediately insmod first one driver. And this is the only way after my device is starting to discover BT devices. Driver from "master" branch is loading '8723a.bin' firmware, and driver form "new" branch is loading "rtl8723b_fw".