1. 18 Jan, 2016 8 commits
    • Kang Xu's avatar
      Release · 74adbc06
      Kang Xu authored
      Change-Id: I21de8ea5f847b7212564faefd71d6f0c5a76a4dd
      CRs-Fixed: 710831
    • Yingying Tang's avatar
      qcacld-2.0: Add verbosity level to a kernel log. · a22bb276
      Yingying Tang authored
      When a STA is connected to the SoftAP, the kernel log gets a
      non-stop message "ol_txrx_peer_link_status_handler: peer_num...".
      Change the always-printing message to a highest verbosity level.
      Change-Id: I0c308795aaa64f20f7a4c52d59c4be50186ffd52
      CRs-Fixed: 947904
    • Yingying Tang's avatar
      qcacld-2.0: Fix a issue of slow QRF WoW reconnection · 120b29cb
      Yingying Tang authored
      This change add a process in apfind_evt handler to trigger host to
      reconnect to remote AP when firmware notifies host about finding this
      missing AP during QRF scan.
      Without this fix, host driver may take longer time to realize that
      the remote AP's connection was dropped and need reconnection, since
      it just wakes up from suspend and does not aware of the connection
      status change.
      Change-Id: I543c29cfa7e9ba138b975c8d06b455b0c9da59e1
      CRs-Fixed: 936929
    • Kang Xu's avatar
      Release · 66c581c6
      Kang Xu authored
      Change-Id: I78e09d9cfef0dbd959461c8bb3f08edcccbb96aa
      CRs-Fixed: 710831
    • Yue Ma's avatar
      qcacld: Add support to do FW initiated recovery · cf2c4189
      Yue Ma authored
      Host driver initiated recovery will cause issues if FW is still
      trying to access host buffers. Hence add the support that recovery
      can be initiated by FW to make sure FW activity has stopped.
      Change-Id: I5f00fe9b969a7d2ce39e31df3dafa30d35078de5
      CRs-fixed: 851449
    • Kiran Kumar Lokere's avatar
      qcacld: Add support to self recover when SME command stuck. · 12309b6b
      Kiran Kumar Lokere authored
      Add support for self recovery when SME command stuck happens.
      Add knob to control the self recovery support and dump the
      recovery stats with ioctl command.
      Change-Id: I2f60d7ede88df939b9cb48d52f0d7e8c0bf79fcf
      CRs-Fixed: 700189
    • Kang Xu's avatar
      Release · 654dd3e2
      Kang Xu authored
      Change-Id: Id7961511751cf0cdef6630f69dc19c838b687d8a
      CRs-Fixed: 710831
    • Yingying Tang's avatar
      Qcacld: Add some log to debug a memory corruption problem · f3d5cd10
      Yingying Tang authored
      Add some debug log between 2 Roam sub state change process.
      Check why the normal Roam sub state change process is not
      Change-Id: Iac0f9f86e7dccfccda97291810e32205f705d34c
      CRs-Fixed: 935062
  2. 09 Nov, 2015 28 commits
  3. 25 Sep, 2015 4 commits
    • Kang Xu's avatar
      Release · 4b141611
      Kang Xu authored
      Change-Id: Ie42923cd476f6f4ea49b13e42b200dfc69273812
      CRs-Fixed: 710831
    • Abhishek Singh's avatar
      qcacld: Set the hdd state to not connected if disconnect timeout. · bbc45ec8
      Abhishek Singh authored
      If disconnect command is queued in SME and same time the connect
      is in progress which failed eventualy, driver will not call the
      disconnect handler leading to the wait for disconnect handler
      timeout. This timeout will leave the hdd state as disconneting
      and thus the next connect commands will always try to disconnect
      thinking that disconnect is still in progress leading to connect
      return with failure.
      With this fix hdd will set the hdd state from disconnecting to
      not connected even if disconnect timeout.
      Change-Id: I349bfe129d476894bc60615477818245cb131a9b
      CRs-Fixed: 832623
    • Srinivas Girigowda's avatar
      qcacld: Set connState to not connected, if disconnect cmd is not queued · d9ed7945
      Srinivas Girigowda authored
      The analysis of this issue is, if the function sme_RoamDisconnect returns
      eHAL_STATUS_CMD_NOT_QUEUED (which means command not queued because there
      is no connection). At this point state m/c is set to Disconnecting and
      we are starting the disconnect timer which timesout and returns -EETIMEDOUT
      and hence connState is not set to eConnectionState_NotConnected.
      When the connection state "Connecting", it can move to either "Connected"
      or "Disconnected". Here since there is a connection failure, we should be
      moving to "Disconnected". Upon connection failure and hdd disconnect in
      progress, we don't move to "Not connected" state and state is stuck at
      "Connection in progress". Hence scan failure.
      To fix this issue, if sme_RoamDisconnect returns eHAL_STATUS_CMD_NOT_QUEUED
      move the state to "Not connected"
      Change-Id: I174eda7eec679f5861946d04c78ad1e76a17975e
      CRs-Fixed: 728064
    • Chandrasekaran, Manishekar's avatar
      qcacld: Abort scan for SSID if deauth is received from supplicant. · 007ee031
      Chandrasekaran, Manishekar authored
      During connection if AP is not found in scan list, driver tries
      to scan for the ssid (eCsrScanForSsid) and if AP is found,
      the connect cmd is started.
      During this scan if Disconnect comes from supplicant, as there is
      no ongoing connect command and sme is not in connected state, the
      disconnect command is dropped in SME and hdd is indicated success.
      This leads to HDD waiting on the event disconnect_comp_var and
      connState to eConnectionState_Disconnecting.
      After this if supplicant send connect and as HDD is in
      disconnecting state it will again wait for disconnect_comp_var
      and return failure after timeout and this will continue and user
      will not able to connect.
      If disconnect is received during eCsrScanForSsid abort/dequeue
      the eCsrScanForSsid in SME and in HDD set the connState to
      eConnectionState_NotConnected and set disconnect_comp_var
      Change-Id: I1da89065e1e59bcf08806179f85e3d9d00d5828e
      CRs-Fixed: 689890