Comment 18 for bug 962082

For the record I also have an identical issue with a much older D-Link DBT-122 dongle

tim@atom:~% lsusb | grep DBT
Bus 001 Device 009: ID 07d1:f101 D-Link System DBT-122 Bluetooth

http://www.dlink.com/uk/en/support/product/dbt-122-wireless-usb-bluetooth-adapter

This apparently is also a broadcom chip.

Snippet from kernel

tim@atom:~% udevadm monitor --property
...
UDEV [1757.217749] add /devices/pci0000:00/0000:00:12.2/usb1/1-5/1-5.1 (usb)
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/009
DEVNUM=009
DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-5/1-5.1
DEVTYPE=usb_device
ID_BUS=usb
ID_MODEL=D-Link_DBT-122
ID_MODEL_ENC=D-Link\x20DBT-122
ID_MODEL_FROM_DATABASE=DBT-122 Bluetooth
ID_MODEL_ID=f101
ID_REVISION=0100
ID_SERIAL=Broadcom_Corp_D-Link_DBT-122
ID_USB_INTERFACES=:e00101:ffffff:fe0100:
ID_VENDOR=Broadcom_Corp
ID_VENDOR_ENC=Broadcom\x20Corp
ID_VENDOR_FROM_DATABASE=D-Link System
ID_VENDOR_ID=07d1
MAJOR=189
MINOR=8
PRODUCT=7d1/f101/100
SEQNUM=2367
SUBSYSTEM=usb
TYPE=224/1/1
USEC_INITIALIZED=196931