Hi Amitkumar, > 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 <[email protected]> > Signed-off-by: Amitkumar Karwar <[email protected]> > --- > drivers/bluetooth/btmrvl_drv.h | 1 + > drivers/bluetooth/btmrvl_main.c | 11 +++++++++-- > drivers/bluetooth/btmrvl_sdio.c | 3 ++- > 3 files changed, 12 insertions(+), 3 deletions(-)
patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
