summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| | * | | | | qcacld-2.0: Add USB VID and PID for QCA9379Yingying Tang2016-08-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently there is no QCA9379 device id in USB device id table. Add USB VID and PID for QCA9379. Change-Id: I7ae39513ff5fc1f0b36f3c05dc0e783532a8d4a3 CRs-Fixed: 1048598
| | * | | | | qcacld-2.0: Fix compile errors when disable below featureskaliu2016-08-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix compilation errors when disable features that controlled by following MACRO. WLAN_FEATURE_11W CONFIG_QCACLD_WLAN_LFR3 WMI_INTERFACE_EVENT_LOGGING Change-Id: Ibdeac0d600028c016ec88f37442d5f1e694b1ecb CRs-Fixed: 1045659
| | * | | | | qcacld-2.0: Clear scan cache in kernel cfg80211 when leaving IBSSSiva Mullati2016-08-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In current code, during IBSS join host updates the bss in cfg80211 for that BSSID. But during IBSS leave host is not unlinking the bss from the kernl cache. So the bss reamains exist in the cfg80211 even after leaving IBSS. Fix is to delete scan cache in kerenl cfg80211 and remove BSSID from SME scan list during leave IBSS. Change-Id: Id4dd08d72ba3fb6ed1b4037b038d888379bb9d6f CRs-Fixed: 1049076
| | * | | | | qcacld-2.0: Clear hostap key storage when BSS is stoppedWu Gao2016-08-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Invalidate the keys stored in the hostap context when BSS stop event is received, so that no old key will be wrongly issued to firmware when hostapd restarts the BSS with a different encryption mode. Change-Id: Ied1fa37cfcff32d3ee87ae26490e59ae59211952 CRs-Fixed: 1046965
| | * | | | | Release 4.0.11.130Anjaneedevi Kapparapu2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.130 Change-Id: Ib10500ea4e94f246b171783634597263b24ba3b9 CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Pass valid data to kernel upon processing GET_STAWPAIE IOCTLManjeet Singh2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While processing GET_STAWPAIE, based on interface, driver calls WLANSap_getstationIE_information()/csrRoamGetWpaRsnReqIE() to get WPA-RSN IE data. For suppose WPA-RSN IE length is greter than DOT11F_IE_RSN_MAX_LEN(114), then these functions returns failure by updating only data length. But as calling functions are not checking return value, driver updates kernel buffer with invalid data. Add check to validate WLANSap_getstationIE_information() and csrRoamGetWpaRsnReqIE() return value. Also update DOT11F_IE_RSN_MAX_LEN to 255 from 114 and update IOCTL numbers. Change-Id: If021318e526c1b1a5616f9447be11174aa4c6a34 CRs-Fixed: 1000857
| | * | | | | qcacld-2.0: Add ipv4 and ipv6 packet checksHimanshu Agarwal2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Presently in updating wma_wow_wake_up_stats, icmpv4 and icmpv6 counts are increased just by checking ICMP protocol offset byte and ICMPV6 protocol offset byte without checking for whether it is a IPV4 or IPV6 packet. So it is possible that for ICMPV6 packet, the IPV4 protol offset byte is equal to ICMP protocol or for some ICMP packet, the IPV6 protocol byte is equal to ICMPV6 protocol and thus both the icmpv4 and icmpv6 counts will get increased for that packet. Add ipv4 and ipv6 packet checks as well in addition to the present checks to avoid wrong increment in the counts. Change-Id: I2d6e5d095d2f4b2dd474b9338bfc830b04bfa533 CRs-fixed: 1048651
| | * | | | | qcacld-2.0: Add initializations for target_delta and bus_deltaHimanshu Agarwal2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In htt_tx_function, due to lack of initializations of target_delta and bus_delta, target_tx_credit remains zero even after the first credit update indication from fw due to which HOST driver is not able to send any packet to fw causing connection failure. Add initializations for target_delta and bus_delta in htt_tx_attach func. Change-Id: I87078dce40bf18d5a7d68bfccd43a6af9c088f8e CRs-Fixed: 1048714
| | * | | | | qcacld-2.0: Acquire read lock before accessing the address listSrinivas Girigowda2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WLAN host driver access the inet6_dev address list without acquiring the read lock, if the kernel network stack deletes the address while driver is accessing the list, it can lead to referencing already freed address by the driver. Hence, fix is to take the read lock before accessing the address list. Change-Id: I934e9f2039f3ab8540e439b9e8a87efced98807c CRs-Fixed: 1048897
| | * | | | | qcacld-2.0: Handle disassociate reason code 34 and cleanup logsSrinivas Girigowda2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently code honors disconnect reason code 34 but still log shows up as invalid reason code. 34 is a valid 802.11 reason code. Add eSIR_MAC_XS_UNACKED_FRAMES_REASON and clean up logs. Change-Id: I32fb804792dd67dd31824a5387e4ecb419656420 CRs-Fixed: 1015244
| | * | | | | qcacld-2.0: Avoid null pointer when STAUT connect to specific APc_zding2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When STAUT connected to specific AP, it will received fragment frame with "fragno" equals to 0, and "more_frag" equals to 0, then the skb is chained for RX thread processing. However the skb will be freed at the end of "htt_t2h_lp_msg_process". This will trigger a null pointer reference at "tlshim_data_rx_cb". The change is to clone this single fragment for RX thread processing, with the same logic of handling non-single fragment frames. Change-Id: Ieb16cf28e04443ea13e992d04688355c39a56a52 CRs-Fixed: 1048532
| | * | | | | qcacld-2.0: Optimize the spinlock usage in suspend callbackKomal Seelam2016-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Optimize the spinlock usage in suspend callback by keeping target wakeup sequence outside the spinlock such that spinlock is not held for longer time. 2. Remove duplicate target sleep call as anyway bus suspend callback puts target into sleep before returning. Change-Id: I08c3d1a72e0b6d3aadd590222130e33ee3db02b2 CRs-Fixed: 1048112
| * | | | | | Promotion of wlan-cld2.driver.lnx.1.0-00063.Linux Build Service Account2016-07-29
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CRs Change ID Subject -------------------------------------------------------------------------------------------------------------- 1037713 I3b10bcbedbd52ea99cc8191f0b1c593ed20e768a qcacld-2.0: Add recovery logic when wmi cmd buffer reach 865207 Iad3c57f0b4e10e68c86cef175b8cadcfd9e7fe1e qcacld-2.0: CL 1597848 - update fw common interface file 997430 Ib70b04f4a720123d21ba820dd3c1e86076083dc9 qcacld-2.0: Purge the scan results by age before posting 962367 Ic968e441411033c3eeb9ec39aff4fc308b80bce8 qcacld-2.0: Fix null pointer dereference in wlan_hdd_nan 962367 I0533494acf6ad520c3258e7f32dbd831508817df qcacld-2.0: Fix unexpected log message in transmit path 688141 I9b57cf4ed2c7d55714c3d495963860ca71b5595b Release 4.0.11.121 962367 Iaf012c08e6b5a7a6327b84b12c06ab27963a704c qcacld-2.0: Add support for multicast traffic over NDI 688141 If991eb8f4762124fba929f08d667971658af8ce4 Release 4.0.11.123 1034565 Iae5aa03ccad8eff72935b1a9f895364495f323e0 qcacld-2.0: Track memory allocation requests in driver 1044604 Idf56344121ca533e1dc57e664822e6cb254ed8c7 qcacld-2.0: Add TX_COMPLETION_THREAD & MSM8976_TCP_PERF 1048047 Ia14b84f1039dc4ffec6ad63550fed21e932f8012 qcacld-2.0: Use system time instead of jiffies for BSS r 1043855 I5d14f3a4b33e961c0b66678258b5ed0fc007b47f qcacld-2.0: Configure NSoffload request in case of activ 1034565 I0e9c869b97e963356327caa7ef36f57e8595ade5 qcacld-2.0: Fix incorrect modification of the copyright 1045161 I763a5fa0b9a7951729b75a0d85696547ce04d174 qcacld-2.0: Avoid suspicious pointer dereference 865207 I2aa5983833ba2ed028a4053b292fe4b6ae66858e qcacld-2.0: CL 1596255 - update fw common interface file 688141 Ife6a10fff834184d99f4db8ae0c7132bf4c23ce1 Release 4.0.11.126 1043805 I4706c57e8c1b684bfe164b23fc0902c376d4d80a qcacld-2.0: Adjust buffer size for fw dump 1047257 Ia93289eaf89538818a8e1264dfcf3306d682bd9b qcacld-2.0: Do not probe MC thread when its suspended 1039967 I75694eb8ab54bfb7622061405f5192832ba8be99 qcacld-2.0: Initlialize hif irq index using atomic opera 984851 Ifdf8d6a1d0c7296713fc23d002beed8a6ac29cc7 qcacld-2.0: Fix probe response dropped by sirvalidateand 1046841 Ib0f894d329146d11fe80995248e3b3c343fb7372 qcacld-2.0: Do not start new connection if cfg80211 requ 1035864 Ic2eae19357d9d459c5a8f690fbc432dd34bfd13d qcacld-2.0: optimize data path memory allocation 865207 I26873873d7a355c179babaa7cc56e187e9771c92 qcacld-2.0: CL 1546483 - update fw common interface file 1041359 I57af2f5b067fa4e76f42379afa40a0f547221fac qcacld-2.0: Remove peer id check for per msdu count 1047096 I36ac5d3cf0d8761bbff4ce4c932a9ca0b16489ef qcacld-2.0: Correct log for sta_inactivity_timeout 1039152 I6cfbb5cb6a434a924e988bab50a5a062a2499ccf qcacld-2.0: Fix suspicious dereference of pointer 1045801 Id309d003a9a4ecc56bf609be7f26d2c508dcb1de qcacld-2.0: Refine ol_schedule_ramdump_work in usb inter 1047268 I7b5181ec1c8548ff9e7d4d56a59ac3814040c187 qcacld-2.0: Increment wow wakeup counter wow_ipv6_mcast_ 865207 I0832f646e76d3e883a36ce3d5d6a63ad7bf83a4c qcacld-2.0: CL 1594228 - update fw common interface file 1046433 I69ec02017e6fc08221059266e06af3c17c084549 qcacld-2.0: Flush TX LL queues when throttle level is se 688141 I2ce7ca1165767e023d3f8f468fa005bbc451bb54 Release 4.0.11.127 1043384 Ia7093802c9240c967378de54695a258d80c395de qcacld-2.0: Initialize session id for auth retry timer 688141 Ibed113b0440acaeca6a8d8aa1a0e373dec660e81 Release 4.0.11.120 1037388 I03ed2db558c5a57883c1051501a57f325f40b6cf qcacld-2.0: Fix eSmeCommandDelStaSession stuck in smeCmd 1028623 I96ccda760045ecd54592b649116f3e7fe4a4f31b qcacld-2.0: Add support for sifs burst duration ini 865207 I473e46c1236140c780059d2877e573bbe22b1586 qcacld-2.0: CL 1548852 - update fw common interface file 865207 I4aaccf1d55aa3e173e4ae2e298a8c711e4a01e31 qcacld-2.0: CL 1548360 - update fw common interface file 1039904 I59a8b150cf8383bf265c048c9fa1b26646e68dc0 qcacld-2.0: Ensure the fw parameters are restored 1034734 I712f814b90ecd4c0322355dd9022441019ecd7a4 qcacld-2.0: Avoid return and send join response with fai 688141 I7ddefac3b95dbac3295f86ab58fbf08c86e135fc Release 4.0.11.124 865207 I3940ffaf856fe9697818b6e56df3a49bf4750af0 qcacld-2.0: CL 1594673 - update fw common interface file 1038049 I4391ad5e2446f6cdbe38bbe47c6fdd57f47839a3 qcacld-2.0: Handle MCC during preauth response 1047807 I05f88b7a49c4fc9c531dfe1574f38da2b416c827 qcacld-2.0: Reduce log levels and cleanup 1000624 If1bbe6d4ab9fdb05d0986b955cdefac66d1ee508 qcacld-2.0: Purge scan results only when scan is complet 688141 I76042fc086e24dcfbb9c9e8d996c5a073f75375b Release 4.0.11.129 1039967 I61e42d28a9eb242e13cc73cdab8efb52e1574cb6 qcacld-2.0: fix corruption of irq history buffer index 1037383 I9273c9e737b97207ce0acee131ab6f3c19cd3e0d qcacld-2.0: Diag event for WOW reason code 1045760 Iba2a6d4c04809041489ff8c32aeb17c9dafbc4a5 qcacld-2.0: Vendor attribute for setting TX fail count t 962367 I48a4a30fd9f6369fe398254184d0016a35c0a6b3 qcacld-2.0: Configure multicast filters for nan data int 688141 I620da79090ae1185526d5e706b297a51544b8561 Release 4.0.11.122 1041684 I3b7d51071bc325da519959c321aa661cb342ffeb qcacld-2.0: Add check to avoid adf_dp_trace_cb_table ove 688141 Ibed4210488ecdd4abe868ec6d9f422d4706840cb Release 4.0.11.128 1036471 Id7ac76bedc20aac39199e14b7042cfb58ba255fe qcacld-2.0: Prevent invalid ipa suspend indication to fw 962367 I7316cc3864052eef4c7bbe9bbac01f0333909c59 qcacld-2.0: Delete peer(if needed) in ndp end indication 880416 Ib0207cee6a1812a81354f638e6bf55441d52c6e1 qcacld-2.0: Active mode offload support 1041679 Ief3c6489748f2dfcc68d7ddb8fb0844c116ea7d4 qcacld-2.0: Add NULL Check in rps indication send API 1040610 I1d30d58f4249a29ddad5c1c390c6fbc373ed6cff qcacld-2.0: Indicate teardown to all TDLS peers when dis 1039404 Ia654fe4919deb515a30bab147316ee7e9bbba1df qcacld-2.0: Don't process rmmod once inject crash ioctl 688141 Iada24ab86fd7c4d550903ed5aa153a41904a358f Release 4.0.11.125 1044060 I7a6aa92351e0140b78c9d7b95f2a6cca45f8e387 qcacld-2.0: Add ndp_ctx NULL check in error scenario 1039381 I9b3fea04fa2f6a9cc85dde4fd9eaab8b6b490fd8 qcacld-2.0: WAR for dfs false detection 1043939 I1578aa5322af50f0ae43248c48a2f754ea081970 qcacld-2.0: Dump more WoW wakeup packet info 865207 I8263688aec3895af57555a5db14d4459848c0cc5 qcacld-2.0: CL 1546701 - update fw common interface file 1044603 Ifb135d4ad1691d0e5024aa2ef31880be271cac9e qcacld-2.0: Print qpower enable/disable depending on the Change-Id: I3c6b8f04d40a45feb29931dcec8b0c78ed06fc97 CRs-Fixed: 1044060, 865207, 1034565, 1045801, 984851, 1047807, 1043805, 1039381, 1037713, 1043384, 1040610, 1034734, 1037383, 1039152, 1037388, 1044603, 997430, 1038049, 1048047, 1036471, 1044604, 1000624, 1028623, 1041679, 688141, 1045760, 1041684, 1046433, 962367, 1039967, 1046841, 1043939, 1041359, 1039904, 1043855, 1047096, 1045161, 1035864, 880416, 1047257, 1039404, 1047268
| | * | | | | Release 4.0.11.129Anjaneedevi Kapparapu2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.129 Change-Id: I76042fc086e24dcfbb9c9e8d996c5a073f75375b CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Use system time instead of jiffies for BSS received timeDeepthi Gowri2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation During late suspend jiffies will not be incremented. Because of this scan results are not age out as the delta of current time and the BSS received time is not correct. To address this, use the system time instead of jiffies for the BSS received time and also make sure to use system time in all other functions. CRs-Fixed: 1048047 Change-Id: Ia14b84f1039dc4ffec6ad63550fed21e932f8012
| | * | | | | qcacld-2.0: Purge scan results only when scan is completeDeepthi Gowri2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation Currently the scan results are aged out based on number of scans for each scan response in SME. But lim may send the scan response to SME often, if the allocated length of scan rsp in lim is less than the scan response or the BSS count is less than or equal to 20, due to this aging count would be decremented quickly and thus would age out the scan results soon. To address this, flush the scan results based on the number scans after scan is complete. CRs-Fixed: 1000624 Change-Id: If1bbe6d4ab9fdb05d0986b955cdefac66d1ee508
| | * | | | | qcacld-2.0: Purge the scan results by age before posting to upper layerDeepthi Gowri2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation Currently the age out of scan results is ineffective as the aging timer is started only once the scan results are obtained from the FW, which would expire in 1 sec, so it could be possible that the cached scan entries may still persist and may not be aged out. To address this issue, purge the scan results by age, before the scan results are updated to upper layer. CRs-Fixed: 997430 Change-Id: Ib70b04f4a720123d21ba820dd3c1e86076083dc9
| | * | | | | qcacld-2.0: Reduce log levels and cleanupSrinivas Girigowda2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reduce log levels and cleanup. Change-Id: I05f88b7a49c4fc9c531dfe1574f38da2b416c827 CRs-Fixed: 1047807
| | * | | | | qcacld-2.0: Indicate teardown to all TDLS peers when disconnect from BSSSiva Mullati2016-07-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When one of the TDLS responder(peer) is not implicit and TDLS link is established. In that case when TDLS initiator disconnect from the BSS (say by if down), TDLS initiator does not send any teardown indication to the TDLS peer. Now therefore, for the TDLS peer,the link is still enabled.When the STA(TDLS initiator) comes up again (say by user if up) the frames to peer shall go via AP link since TDLS is down as far as TDLS initiator is concerned. However, the peer shall try to respond over the TDLS link since the peer still maintains the connection/link. This results in failure of frame delivery. Fix is to indicate teardown to peers when disconnect from BSS Change-Id: I1d30d58f4249a29ddad5c1c390c6fbc373ed6cff CRs-Fixed: 1040610
| | * | | | | Release 4.0.11.128Anjaneedevi Kapparapu2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.128 Change-Id: Ibed4210488ecdd4abe868ec6d9f422d4706840cb CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Correct log for sta_inactivity_timeoutAgarawal Ashish2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a station does not send anything in sta_inactivity_timeout, an empty data frame is sent to it in order to verify whether it is still in range. If this frame is not ACKed, the station will be disassociated and then deauthenticated. Added log for failure case and debug log for success case. Change-Id: I36ac5d3cf0d8761bbff4ce4c932a9ca0b16489ef CRs-Fixed: 1047096
| | * | | | | qcacld-2.0: Vendor attribute for setting TX fail count thresholdAgrawal Ashish2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Vendor attribute for setting TX fail count threshold. This attribute is part of QCA_NL80211_VENDOR_SUBCMD_SET_WIFI_CONFIGURATION. Change-Id: Iba2a6d4c04809041489ff8c32aeb17c9dafbc4a5 CRs-Fixed: 1045760
| | * | | | | qcacld-2.0: WAR for dfs false detectionKapil Gupta2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware sometimes get phyerrors in presence of third party devices which may be identified as radar pulses. Add following workaround to skip these pulses on basis of their characteristics: 1. Add new filters for pulses coming on DC position 2. Increased min threshold for filter 5 3. Flush other DC queue once we get pulse belonging to one queue 4. Add extra workaround for FCC filter 31 and 32 to reset the queues based on deviation from mean. 5. Remove rejection of pulses based on max pri(channel load optimization) CRs-Fixed: 1039381 Change-Id: I9b3fea04fa2f6a9cc85dde4fd9eaab8b6b490fd8
| | * | | | | qcacld-2.0: Flush TX LL queues when throttle level is set to 0Govind Singh2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TX LL queues are not flushed immediately when throttle level is set to 0. This is causing latency as TX LL queues are getting flushed on arrival of new packet from network stack. Flush Tx LL queues by rescheduling the throttle phase timer ,when throttle level is set to 0. Change-Id: I69ec02017e6fc08221059266e06af3c17c084549 CRs-Fixed: 1046433
| | * | | | | qcacld-2.0: Delete peer(if needed) in ndp end indicationNaveen Rawat2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Take action to delete peer in NDP_END Indication, rather than NDP_END Response event from firmware. Earlier, device initiating NDP_END will only get NDP_END_Response event from firmware, but that behavior is changed now and both self and peer device will get NDP_END_indication with peer map for ndp end. Change-Id: I7316cc3864052eef4c7bbe9bbac01f0333909c59 CRs-Fixed: 962367
| | * | | | | qcacld-2.0: Increment wow wakeup counter wow_ipv6_mcast_wake_up_countSrinivas Girigowda2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently when the firmware sends WOW_REASON_RA_MATCH event, only wow_ipv6_mcast_ra_stats is incremented. Since it is a ipv6 multicast RA packet which is waking up the APPS, we also need to increment wow_ipv6_mcast_wake_up_count to report the correct statistics. Change-Id: I7b5181ec1c8548ff9e7d4d56a59ac3814040c187 CRs-Fixed: 1047268
| | * | | | | qcacld-2.0: Do not probe MC thread when its suspendedRajeev Kumar2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not probe MC thread when its suspended during cfg80211 suspend and increase thread stuck detection threshold to avoid reporting false alarm. Change-Id: Ia93289eaf89538818a8e1264dfcf3306d682bd9b CRs-Fixed: 1047257
| | * | | | | qcacld-2.0: CL 1597848 - update fw common interface filesNitesh Shah2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding WMI defs for pdev and peer GET_ANTDIV_STATUS_CMD, ANTDIV_INFO_EVENT msgs. Change-Id: Iad3c57f0b4e10e68c86cef175b8cadcfd9e7fe1e CRs-fixed: 865207
| | * | | | | qcacld-2.0: CL 1594673 - update fw common interface filesNitesh Shah2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding new event for NAN Wake up with zero length. Adding WMI_EP definitions. Change-Id: I3940ffaf856fe9697818b6e56df3a49bf4750af0 CRs-fixed: 865207
| | * | | | | qcacld-2.0: CL 1594228 - update fw common interface filesNitesh Shah2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Define mechanism for WMI_SERVICE flags beyond 128. Change-Id: I0832f646e76d3e883a36ce3d5d6a63ad7bf83a4c CRs-fixed: 865207
| | * | | | | qcacld-2.0: CL 1548852 - update fw common interface filesNitesh Shah2016-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding ANT_DIV WMI_PDEV_PARAMs. Change-Id: I473e46c1236140c780059d2877e573bbe22b1586 CRs-fixed: 865207
| | * | | | | Release 4.0.11.127Anjaneedevi Kapparapu2016-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.127 Change-Id: I2ce7ca1165767e023d3f8f468fa005bbc451bb54 CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Avoid return and send join response with failNitesh Shah2016-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function __limProcessSmeJoinReq returns if vos_mem_malloc fails for pMlmJoinReq without giving any join response. Fix is to send the join response with the failure reason. Change-Id: I712f814b90ecd4c0322355dd9022441019ecd7a4 CRs-Fixed: 1034734
| | * | | | | qcacld-2.0: Refine ol_schedule_ramdump_work in usb interface platformkaliu2016-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For usb interface platform, driver won't use ol_schedule_ramdump_work to dump fw, so set this routine to NULL. Change-Id: Id309d003a9a4ecc56bf609be7f26d2c508dcb1de CRs-Fixed: 1045801
| | * | | | | qcacld-2.0: Do not start new connection if cfg80211 request REASSOC failsSelvaraj, Sridhar2016-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | qcacld-3.0 to qcacld-2.0 propagation Change return type of wlan_hdd_reassoc_bssid_hint to indicate REASSOC request rather than success or failure of hdd_reassoc request. If this function returns false, continue with connection else return status code from the function. Change-Id: Ib0f894d329146d11fe80995248e3b3c343fb7372 CRs-Fixed: 1046841
| | * | | | | Release 4.0.11.126Anjaneedevi Kapparapu2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.126 Change-Id: Ife6a10fff834184d99f4db8ae0c7132bf4c23ce1 CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Add support for sifs burst duration inic_manjee2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add code for implementing sifs burst duration ini to be sent to be FW as part of WMI_PDEV_PARAM_BURST_DUR command. Change-Id: I96ccda760045ecd54592b649116f3e7fe4a4f31b CRs-Fixed: 1028623
| | * | | | | qcacld-2.0: Diag event for WOW reason codeNitesh Shah2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add diag event for WOW reason code. The event EVENT_WLAN_POWERSAVE_WOW will be used to inform the WOW reason code. Change-Id: I9273c9e737b97207ce0acee131ab6f3c19cd3e0d CRs-Fixed: 1037383
| | * | | | | qcacld-2.0: CL 1548360 - update fw common interface filesNitesh Shah2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding common changes for enabling ATF per SSID (vdev) strict/fair scheduling. Change-Id: I4aaccf1d55aa3e173e4ae2e298a8c711e4a01e31 CRs-fixed: 865207
| | * | | | | qcacld-2.0: Don't process rmmod once inject crash ioctl receivedMukul Sharma2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During time window where crash ioctl is issued but target failure handler is not called yet, Meanwhile if rmmod comes then host allow it to proceed because logp is not yet set. Simultaneously target failure comes and set logp hence rmmod start wlan shutdown instead wlan exit in ath_hif_sdio_remove. To mitigate this problem, ensure host do not honour rmmod after it receives inject crash ioctl. Change-Id: Ia654fe4919deb515a30bab147316ee7e9bbba1df CRs-Fixed: 1039404
| | * | | | | qcacld-2.0: optimize data path memory allocationHimanshu Agarwal2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When allocate HTT descriptor, instead of allocating large single chunk of memory, allocate small sized multiple chunk of memory. Then not need to allocate order 5 memory. Will have less chance to have memory alloc fail problem. HTT descriptor. Frag descriptor. OL descriptor. TSO descriptor Change-Id: Ic2eae19357d9d459c5a8f690fbc432dd34bfd13d CRs-fixed: 1035864
| | * | | | | qcacld-2.0: Print qpower enable/disable depending on the config valueAbhishek Singh2016-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Driver prints qpower disabled even if command for qpower enabled is sent to firmware. To avoid confusion print qpower enable/disable depending on the cmd sent to firmware. Change-Id: Ifb135d4ad1691d0e5024aa2ef31880be271cac9e CRs-Fixed: 1044603
| | * | | | | Release 4.0.11.125Anjaneedevi Kapparapu2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.125 Change-Id: Iada24ab86fd7c4d550903ed5aa153a41904a358f CRs-Fixed: 688141
| | * | | | | qcacld-2.0: Fix incorrect modification of the copyright yearSaidiReddy Yenuga2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fix copyright year Change-Id: I0e9c869b97e963356327caa7ef36f57e8595ade5 CRs-Fixed: 1034565
| | * | | | | qcacld-2.0: Add ndp_ctx NULL check in error scenarioGovind Singh2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add ndp_ctx NULL check in error scenario before dereferencing it. Change-Id: I7a6aa92351e0140b78c9d7b95f2a6cca45f8e387 CRs-Fixed: 1044060
| | * | | | | qcacld-2.0: Avoid suspicious pointer dereferenceSreelakshmi Konamki2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix add to NULL check before pointer dereference Change-Id: I763a5fa0b9a7951729b75a0d85696547ce04d174 CRs-Fixed: 1045161
| | * | | | | qcacld-2.0: Add TX_COMPLETION_THREAD & MSM8976_TCP_PERF for APQ8009gbian2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: Idf56344121ca533e1dc57e664822e6cb254ed8c7 CRs-Fixed: 1044604
| | * | | | | qcacld-2.0: CL 1596255 - update fw common interface filesNitesh Shah2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Defining new module id for WAL_MODULE_ENQ. Change-Id: I2aa5983833ba2ed028a4053b292fe4b6ae66858e CRs-fixed: 865207
| | * | | | | qcacld-2.0: Adjust buffer size for fw dumpkaliu2016-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In platform using usb interface, when fw assert, buffer alloc for fw dump is smaller than the actual fw dump size, so adjust the buffer size. Change-Id: I4706c57e8c1b684bfe164b23fc0902c376d4d80a CRs-Fixed: 1043805
| | * | | | | Release 4.0.11.124Anjaneedevi Kapparapu2016-07-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.11.124 Change-Id: I7ddefac3b95dbac3295f86ab58fbf08c86e135fc CRs-Fixed: 688141