summaryrefslogtreecommitdiffstats
path: root/drivers/target
diff options
context:
space:
mode:
authorAmitkumar Karwar <akarwar@marvell.com>2012-06-27 19:57:56 -0700
committerJohn W. Linville <linville@tuxdriver.com>2012-06-28 14:37:48 -0400
commit1a1fb970472d66d1668ff66bc46c2cd977f9a4fc (patch)
treed164ac3c4c2808fcc218bc798615254852fd31b7 /drivers/target
parent469979173ecda9c472c495608d6d540ec33ab85d (diff)
downloadblackbird-obmc-linux-1a1fb970472d66d1668ff66bc46c2cd977f9a4fc.tar.gz
blackbird-obmc-linux-1a1fb970472d66d1668ff66bc46c2cd977f9a4fc.zip
mwifiex: wakeup main thread to handle command queued
We miss to wakeup main thread after adding command to cmd pending queue at follwing places. These commands are handled later when main thread is woken up for handling an interrupt for sleep event from firmware. This adds worst case delay of 50msec. 1) We don't wakeup main thread when asynchronous command is added to cmd pending queue. Move queue_work() call from mwifiex_wait_queue_complete() to mwifiex_send_cmd_async() to wakeup main thread for sync as well as async commands. 2) Scan operation is triggered due to following reasons a) request from user (ex. "iw scan" command) b) Scan performed by driver internally. In first case main thread is woken up when first scan command is queued in cmd pending queue (we don't need to wakeup main thread for subsequent scan commands, because they are queued in scan command response handler), but it is not done for second case. queue_work() is moved inside mwifiex_scan_networks() to handle both the cases. Signed-off-by: Amitkumar Karwar <akarwar@marvell.com> Signed-off-by: Avinash Patil <patila@marvell.com> Signed-off-by: Bing Zhao <bzhao@marvell.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/target')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud