Bluetooth: btmrvl: don't consume all vendor specific events
authorAmitkumar Karwar <akarwar@marvell.com>
Fri, 21 Mar 2014 03:05:44 +0000 (20:05 -0700)
committerMarcel Holtmann <marcel@holtmann.org>
Fri, 21 Mar 2014 03:29:48 +0000 (20:29 -0700)
commitd986b4a6480bdd55c073635ef883c754e46ac0eb
treea3d8af7d195ba3d9252b3ecc196ea5ea6fde7620
parent61b1a7fbda6f761ebe16a62124578ca0779d9365
Bluetooth: btmrvl: don't consume all vendor specific events

If vendor specific HCI commands are received from application,
we should send corresponding events to stack.
These events should be consumed in driver, only if they are for
the internal HCI commands generated by driver.

This patch fixes the vendor command 0x3f stuck problem with
above mentioned change. For example,

hcitool cmd 3f 22 fe 06 22 21 20 43 50 00

Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Signed-off-by: Bing Zhao <bzhao@marvell.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
drivers/bluetooth/btmrvl_main.c