1. 28 Jun, 2012 1 commit
    • Amitkumar Karwar's avatar
      mwifiex: wakeup main thread to handle command queued · 1a1fb970
      Amitkumar Karwar authored
      
      
      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: default avatarAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: default avatarAvinash Patil <patila@marvell.com>
      Signed-off-by: default avatarBing Zhao <bzhao@marvell.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      1a1fb970
  2. 22 Jun, 2012 3 commits
  3. 20 Jun, 2012 4 commits
  4. 12 Jun, 2012 1 commit
  5. 11 Jun, 2012 3 commits
  6. 05 Jun, 2012 2 commits
  7. 04 Jun, 2012 2 commits
  8. 16 May, 2012 19 commits
  9. 15 May, 2012 1 commit
  10. 08 May, 2012 2 commits
  11. 23 Apr, 2012 1 commit
  12. 17 Apr, 2012 1 commit
    • Amitkumar Karwar's avatar
      mwifiex: corrections in timestamp related code · b5abcf02
      Amitkumar Karwar authored
      
      
      We get two timing related fields for each bss from firmware in scan
      results.
      1) timestamp - Actual timestamp information in probe response/beacon
      2) network_tsf - firmware's TSF value at the time the beacon or probe
      response was received.
      Both are needed while associating by firmware.
      
      The patch takes care of following things.
      1) We should pass "timestamp" to cfg80211_inform_bss(), but currently
      "network_tsf" is being provided. This error is corrected here.
      2) Rename "network_tsf" to "fw_tsf"
      3) Make use of u64 variable instead of an array of u8/u32 to save
      parsed "timestamp" information.
      4) Use timestamp provided to stack in scan results using
      cfg80211_inform_bss() while associating. (bss->tsf)
      5) Allocate space to save fw_tsf in "priv" of cfg80211_bss
      and retrieve it while associating.
      Signed-off-by: default avatarAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: default avatarBing Zhao <bzhao@marvell.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      b5abcf02