Chin-Ran Lo 8cf60cf238 Bluetooth: btmrvl: don't send data to firmware while processing suspend ... Usually when driver sends data to firmware it receives TX_DONE (DN_LD_HOST_INT_STATUS) interrupt from firmware right away. It's also observed that some times the fireware could delay sending DN_LD_HOST_INT_STATUS interrupt. If driver sends data to firmware during suspend processing and the TX_DONE interrupt is delayed, it may come back at wrong time when SDIO host driver is in the middle of suspending. Block any data from stack while suspending. Also skip sending data that are already in driver tx_queue. Don't purge the skb queue on suspend to avoid intermittent music after system resumes from S3. Signed-off-by: Chin-Ran Lo <crlo@marvell.com> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>		2016-01-06 16:37:14 +01:00
..
ath3k.c
bcm203x.c
bfusb.c
bluecard_cs.c
bpa10x.c
bt3c_cs.c
btbcm.c
btbcm.h
btintel.c
btintel.h
btmrvl_debugfs.c
btmrvl_drv.h
btmrvl_main.c
btmrvl_sdio.c
btmrvl_sdio.h
btqca.c
btqca.h
btrtl.c
btrtl.h
btsdio.c
btuart_cs.c
btusb.c
btwilink.c
dtl1_cs.c
hci_ath.c
hci_bcm.c
hci_bcsp.c
hci_h4.c
hci_h5.c
hci_intel.c
hci_ldisc.c
hci_ll.c
hci_qca.c
hci_uart.h
hci_vhci.c
Kconfig
Makefile