summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | | qcacld-2.0: disable D0-WOW for SDIO based interfaceSarada Prasanna Garnayak2015-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | D0-WOW feature is specific to PCIe based interface and this feature is not required for SDIO based interface. Update kbuild to disable D0-WOW feature for SDIO based interface. CRs-Fixed: 929346 Change-Id: Ia56314b73f8a7e0d8aac8637721467423e3cb284
| * | | | qcacld-2.0: CL 1404920 - update fw common interface filesNirav Shah2015-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New TDLS mode and STA kickout threshold for TDLS peer Change-Id: Ibfba28323bc45481b29f361ac3827a70d4a5bc2f CRs-Fixed: 929922
| * | | | qcacld-2.0: CL 1404155 - update fw common interface filesNirav Shah2015-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WMI interface change for 11w Offload. CRs-Fixed: 929921 Change-Id: I8292398dcad078e9bc9c650690c7b9ebea956cff
| * | | | qcacld-2.0: clean up of ERROR logsGovind Singh2015-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Misleading error logs are removed as part of this fix CRs-Fixed: 929840 Change-Id: Ifdc10b79359863a4f3c2009403ee5f6c7ab18110
| * | | | qcacld-2.0: Allow Runtime PM after Scan CompletionKomal Seelam2015-10-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Runtime PM is tied with wakelocks. Driver held 1sec wakelock after scan completion which is preventing runtime suspend. The wakelock is held to prevent APPS suspend while supplicant initiates the connection. This results in drawing higher current. This has signifcant impact on power as in static display case framework issues scan for every 15sec. The code is in place to prevent runtime pm when connection is in progress. Thus preventing runtime pm after scan can be avoided. Hence the fix. Change-Id: Id45fe56c314c4511305d58dc8d50fb439f55e0a2 CRs-Fixed: 924797
| * | | | Release 4.0.10.204AnjaneeDevi Kapparapu2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.10.204 Change-Id: I2f16a2f59cb47fbca3623e4fe73b0788a461f104 CRs-Fixed: 688141
| * | | | qcacld-2.0: Do not release the lock within list_for_each_entry_safe contextManjunathappa Prakash2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Race condition between vos_free_tlshim_pkt_freeq() and vos_alloc_tlshim_pkt() results in double remove of already removed list node. So do not release lock within list_for_each_entry_safe context. Change-Id: I3462927f7baea578d31847c5542591415c4f0f39 CRs-Fixed: 924423
| * | | | qcacld-2.0: CL 1400127 – update fw common interface filesSanjay Devnani2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | define WMI_ROAM_SUBNET_CHANGE_STATUS flags Change-Id: I665e290086e6f7575f394a3bb4e59d33da0afc9c CRs-Fixed: 865207
| * | | | qcacld-2.0: CL 1399840 – update fw common interface filesSanjay Devnani2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | add WMI_WOW_FLAG_IGNORE_PCIE_RESET WMI Command & Event definition for E-GAP Change-Id: Icdedd06a5b935c34d67880330481a4b36dc8484e CRs-Fixed: 865207
| * | | | qcacld-2.0: CL 1398795 – update fw common interface filesSanjay Devnani2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | add WMI cmd WMI_WOW_HOSTWAKEUP_PIN_PATTERN_CONFIG_CMDID Change-Id: If9d15429b8171b402374fa999db91affe83be753 CRs-Fixed: 865207
| * | | | qcacld-2.0: CL 1395312 – update fw common interface filesSanjay Devnani2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | add WMI_PEER_ASSOC_CONF_EVENT msg Change-Id: Ie182af029e480a91810bcd333c72466dab79074d CRs-Fixed: 865207
| * | | | Qcacld: Fix a problem that can't get the RSSI of connected-staYingying Tang2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Correct the return value to iwpriv, make sure that iwpriv can display the expected result. Change-Id: Iaad6595dd81f2095a5b2d0d60a27b0566751a3a3 CRs-Fixed: 927105
| * | | | qcacld: Fix to avoid acquiring mutex in atomic contextRakesh Sunki2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a radar is indicated from WMA to HDD, it happens in a soft irq context and the dfs_radar_found flag is set by acquiring a mutex which leads to apps crash. The crash happens if the mutex for dfs_radar_found flag is being held by the main thread and as a result the soft irq thread seeking the same mutex will be put in the kernel sleep queue leading to apps crash as sleeping is not allowed in soft irq context. Fix the issue by using spinlock instead of mutexes. An exception has been made to use the spinlock in the main thread context to work around the complications involving for radar indication callback to happen in worker thread context instead of soft irq context. Change-Id: I4bc01ac8991c593ffcaf6ee532f4594cb8beba16 CRs-Fixed: 928394
| * | | | qcacld-2.0: Avoid rx_wake_lock during load/unloadGovind Singh2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Crash is observed due to excessive logging as rx path is acquiring rx_wakelock for rx packet chain, vos_wake_lock_timeout_acquire calls runtime suspend timeout API where we check for load/unload in progress and it results in excessive logging. CRs-Fixed: 920089 Change-Id: I64cffc231c20083e0a7bc4c0966980a6d0abddcf
| * | | | qcacld-2.0: Remove DSRC channels in scan channel listSandeep Puligilla2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Scan need not to be performed on DSRC channels but still host is sending DSRC channels as part of WMI_SCAN_CHAN_LIST_CMDID to firmware. Removed DSRC channel information from the valid scan channel list sent to firmware. Change-Id: I288e8b2d4a528357c33bef5ebaab1b2bfbd66293 CRs-Fixed: 915407
| * | | | qcacld-2.0: Remove Radio measurement related cfg entriesKrishna Kumaar Natarajan2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove cfg entries related to radio measurement(RM). We have support to enable/disable RM capability through INI config. We also had entry in cfg static table(cfg.dat). This change set will remove entries related to RM. Change-Id: Ic56cc34628cd1c0fb10512069ef6dc5f0eebb887 CRs-Fixed: 924420
| * | | | qcacld-2.0: Set RM capability independent of AP's capabilityKrishna Kumaar Natarajan2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove check for AP's capability information to set station's radio measurement(RM) capability in Capability Information element. Change-Id: I6047d4dec19e7cd32d6733e4da773875bbbb31aa CRs-Fixed: 924420
| * | | | qcacld: Do not update WLAN status to LPASS when disconnect during unloadYue Ma2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Host driver updates WLAN status to LPASS with connected false and WLAN on when disconnection happens. Host driver also updates WLAN status right after driver unload is triggered with connected false and WLAN off. There is a scenario that disconnection callback comes during driver unloading which causes LPASS misbehavior. Fix this by only updating disconnection status to LAPSS when driver is not unloading. Change-Id: Ie72ba094283a64c06e8c74523314d6de92a0f08b CRs-fixed: 928365
| * | | | qcacld-2.0: Fix UL TPUT issue when connected to 160MHz APKiran Kumar Lokere2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When STA is connected to 160MHz AP, channel width is updated to 20MHz since the 160MHz channel width is not handled. Add support to handle the 160MHz BW in beacon IEs. Change-Id: Id13164762d6da142093f049121440ce976cecfc1 CRs-Fixed: 924219
| * | | | qcacld-2.0: Indicate proper reason code to userspace on link teardownEdhar, Mahesh Kumar2015-10-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In station mode while teardowning AP link due to inactivity indicate reason code to userspace as eSIR_MAC_DISASSOC_DUE_TO_INACTIVITY_REASON instead of eSIR_MAC_PEER_STA_REQ_LEAVING_BSS_REASON. Change-Id: I83c826a15331e912e2358923471e8a111c44349e CRs-Fixed: 923014
| * | | | Release 4.0.10.203AnjaneeDevi Kapparapu2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.10.203 Change-Id: I3ee8e9bf102e93b031ef8ecbbc2351b4de5ce199 CRs-Fixed: 688141
| * | | | qcacld-2.0: allow rps cpu map to be read from iniMohit Khanna2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Currently wlan driver only sends WLAN_SVC_RPS_ENABLE_IND message along with the interface name to cnss-daemon. This change allows wlan driver to send rps cpu mask from the ini file (for each rx queue) to be sent along with this message. - Enable RPS mask as "e e e e" by default in WLAN ini file. Change-Id: I869d4dd70533eefbff03ed97976700d4e0e75c1d CRs-Fixed: 919192
| * | | | qcacld 2.0: Fix deadlock condition inside tlshim_mgmt_rx_processHimanshu Agarwal2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to spinlock taken over the whole tlshim_mgmt_rx_process function, the deadlock condition is occuring as there are parts of the code inside this function where we are allocating memory without taking atomic flag causing the function to go to sleep occasionally while in spinlock protection. This fix takes spinlock only on those parts of the code where it is required and no memory allocation is happening without setting the atomic flag. Change-Id: I4bbaeb2a87bbc2216e7d5fe4c1492cdc863816db CRs-Fixed: 923496
| * | | | qcacld2.0: Increase default tx_queue_len for WLAN netdeviceMohit Khanna2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An increase in tx_queue_len of netdev to 3000 is giving us better TCP TX performance. Hence, increasing its value from its default (1000). This gives us about 30 - 40 Mbps of boost. Change-Id: I68f26ac0f4a040b0bbf10dd571dae8e5316f16b3 CRs-Fixed: 927673
| * | | | qcacld: Adjust the dfs phyerror rssi thresholdRakesh Sunki2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When radar is injected at edge frequency the rssi values reported in radar summary report are above the rssi thresholds in the radar filters leading to reduced radar detection at the edge frequencies. Fix the issue by adjusting the rssi value to accomadate the rssi reported at the edge frequencies, resulting in increased radar detection rates. Change-Id: I2102d27667b7f8e3a532a81c0a2fc0fd97984c96 CRs-Fixed: 925189
| * | | | qcacld: Add channel 144 in safe channels for LTE CoexManikandan Mohan2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add channel 144 in list of LTE coex safe channel list used for ACS processing Change-Id: I67fa2eb69f30f91e91069743130188d4b5fb2213 CRs-fixed: 926821
| * | | | qcacld-2.0: replace semaphore to completionLeo Chang2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HTC RX event wait semaphore waiting event infinte. Infinte waiting will hang device and cannot getting out from system hang. To collect FW RAM dump and make correct panic, semaphore should be replaced with time limitted compeletion. Add completion re-init. Change-Id: I075a0ee8d0e3e35f6f8ac5244ce384ab873bd9b4 CRs-fixed: 924387
| * | | | qcacld: Increase SSR timeout to 30 secondsYue Ma2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Increase SSR timeout from 15 seconds to 30 seconds in order to handle some corner cases which may cause SSR to take longer time. E.g. CPU is busy/stuck with other tasks. Also increase the timeout to 40 seconds for SLUB DEBUG build. Change-Id: I6837f2d5e87090ede15e514d1c4f978d34931f32 CRs-fixed: 927722
| * | | | qcacld: Fix WDI pipe enable failure due to double invokeYun Park2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix an issue which enables WDI pipes even when RM resource request failed, which will cause to invoke WDI pipe enable twice when RM_ RESOURCE_GRANTED notification arrives later. Also fixed a possible discrapancy between connected client stat count and actual number of connected clients. Change-Id: Ibb86ef6ada398fcc669e3a894daadc09e6096b0f CRs-fixed: 927581
| * | | | qcacld-2.0: Fix iwpriv ipaucstat causes unexpected behaviorYun Park2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | iwpriv ipaucstat with parameter 1 or 3 will also execute QCASAP_SET_ PHYMODE, since the code will not return. This will cause unexpected behavior based on the current device status , and This change fixes this issue. Change-Id: I5ef3044639ad4f32db8c24d917b7b7f2c54d3d51 CRs-Fixed: 927586
| * | | | qcacld-2.0: Properly update specturum channel listEdhar, Mahesh Kumar2015-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently for ACS,one to one correspondence between channel number and index of Sap specturum structure is desired. But the correspondence is broken in case of channel in NOL list or if the DFS channels are not allowed. In case of channel in NOL list or if DFS channel not allowed, channel number is incremented but index of structure doesn't change. As a part of fix, made sure that one to one correspondence is maintained. Change-Id: I05cbe92e2657d96e271b402b9fdbe41a32c7080d CRs-Fixed: 922865
| * | | | Release 4.0.10.202AnjaneeDevi Kapparapu2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.10.202 Change-Id: I4d1c9e83e10409c426b99b89c3c0c6c767358b31 CRs-Fixed: 688141
| * | | | qcacld-2.0: replace semaphore to completionLeo Chang2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HTC RX event wait semaphore waiting event infinte. Infinte waiting will hang device and cannot getting out from system hang. To collect FW RAM dump and make correct panic, semaphore should be replaced with time limitted compeletion Change-Id: Idabfc7916676c9e986e953b50108653a5b394278 CRs-fixed: 924387
| * | | | qcacld: IPA uC: return EPERM for IPA RM CONS REQ only during unloadingYun Park2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change to return -EINPROGRESS if WLAN unable to grant IPA CONS resource due to IPA resource loading is in progress. Return -EPERM only if WLAN unable to grant IPA CONS resource due to IPA resource unloading is in progress. Change-Id: Iea4d804d3f81b086e723230fb8eddc7d9561d7d1 CRs-Fixed: 926880
| * | | | qcacld-2.0: set drive strength to DSarada Prasanna Garnayak2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Set drive strength to D irrespective to chip. CRs-Fixed: 926487 Change-Id: Ic15f676d63ddeb4055d7c35a8bf68d6f2af0dd05
| * | | | qcacld-2.0: update kbuild for SDIO based interfaceSarada Prasanna Garnayak2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update kbuild to disable the features which is not required for SDIO based interface. CRs-Fixed: 926508 Change-Id: I6e9a25d15a20e2c75fb45a29b7e56b2401654231
| * | | | qcacld: Copy FW dump if FW asserts/kernel panic during driver loadingYue Ma2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are some cases that FW crashes while host driver is loading, but since SSR is not supported during driver load/unload, FW dump is not collected. Hence add the support to copy the FW dump in this case as well as kernel panic case. Change-Id: I17c30d8b9e784280da651ddf1af3a15f52616905 CRs-fixed: 859571
| * | | | qcacld-2.0: Allow Re-assoc to same AP only in open security modeAbhishek Singh2015-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation Driver do not support Reassoc in security mode and processing reassoc in security mode may leads to issue like keys are not negotiated properly. With this change Driver will allow reassoc to same AP only in open security mode. Change-Id: I35d802f564e41ee0b30386ee7b74d2b44eb80ecf CRs-Fixed: 923219
| * | | | qcacld-2.0: Fix KW issuesKomal Seelam2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Handle possible NULL pointer dereference to fix KW issues Change-Id: I55c58be0a97874625b7487f0316116e07d47dca7 CRs-fixed: 924538
| * | | | Release 4.0.10.201AnjaneeDevi Kapparapu2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release 4.0.10.201 Change-Id: Ic72ec2c7bc7d77121b210a030e0b3d075830d54d CRs-Fixed: 688141
| * | | | qcacld-2.0: Fix compilation issues for SDIO platformsKomal Seelam2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix compilation issues for SDIO platforms Change-Id: I5a97581406917ffe84e94854e2d6c356ce1df360 CRs-fixed: 924538
| * | | | qcacld-2.0: Initialize RSNMfpCapable and RSNMfpRequired properlyAbhishek Singh2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation In hdd_SetGENIEToCsr, RSNMfpCapable and RSNMfpRequired are not initialized with 0, so if the IE's provided does not have RSN IE these variables are not modified to 0 or 1 depending on PMF capability in RSN IE and thus will have some garbage value. This will lead to PMF enabled even if RSNIE is not present. Initializing RSNMfpCapable and RSNMfpRequired with 0 solves the issue. Change-Id: If35d9d957d578120f3c0f437734613f2ce2387a7 CRs-Fixed: 919527
| * | | | qcacld-2.0: Prevent runtime suspend untill clean-up completesKomal Seelam2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When runtime suspend fails because of wma_suspend_req() not completing in time, PM runtime workqueue posts resume request to MC thread to clean-up. If MC thread is busy or slow in processing resume request and after the timeout Runtime PM framework posts another suspend request then there may be race condition between MC thread processing resume request (Or even suspend request) and Runtime PM workqueue posting subsequent suspend request. Synchronize subsequent suspend request by not allowing the runtime suspend till resume requests completes in MC thread context. Change-Id: Ie9aaf72fbced41f8d23640b9032a3c2236dc6826 CRs-fixed: 921373
| * | | | qcacld: Prevent runtime suspend when recovery initiatedPrashanth Bhatta2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When self recovery initiated, CRASH_INJECT command is sent to firmware. If firmware crash doesn't reach the host in time then RuntimePM may kick in and try to suspend the PCIe link. At this time, firmware might already been crashed just that host missed the interrupt. Add the logic to prevent the Runtime suspend when initiating the recovery so that host driver doesn't attempt the suspend which may not go through and cause stability issues. Change-Id: Ie8d5fc6aa08e4864fa5f03119c25037f5aeb5cec CRs-fixed: 924538
| * | | | qcacld-2.0: eSmeCommandDelStaSession stuck in smeCmdActiveListkaliu2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1.Use iw tool to let dut connect to remote ap, dut is working on wlan0. 2.At same time, use hostapd to start sap also on interface wlan0. In item1, before connect to ap, dut will do an internal scan to search ap,if scan result matched configured ap profile, dut trys to connect to ap. In item2, when starting sap, found it's sta mode it will try to disconnect dut with remote ap and close sta session. #1 If ap start action happened in item1's scan period, trying disconnecting won't take effect as currently sta has not yet connected with remote ap. So after item1's scan finished, dut continues to do connection. #2 During closing sta session, sme issued eSmeCommandDelStaSession, as currently sta is doing connection, so session is in started status, this cause closure failed, so there is no chance to remove cmd in smeCmdActiveList. While cmd pending in smeCmdActiveList for 120s, driver issued crash. The solution is in item1 after scan complete to check whether it's needed to start following connection. If stop action has been issued during scan period, then don't do the connection. Change-Id: If632e21cb13277fba371ff1bf8df97febf856d09 CRs-Fixed: 923375
| * | | | qcacld: Record interrupt history for SLUB_DEBUG buildYue Ma2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Record interrupt history when interrupt/tasklet is invoked in SLUB_DEBUG build. Change-Id: Idc22341fe0dcd7cf75ddede3ff2fac17c418579d CRs-fixed: 924388
| * | | | cld-2.0: Send disconnect event for userspace initiated disconnectArchana Ramachandran2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From kernel 3.11 onwards, cfg80211_disconnect will not be notifying the userspace with disconnected event. Indicate disconnect event to nl80211 and thereby to the supplicant for userpsace initiated disconnect Change-Id: I4724d9b8c645991121bca8c489c0a8e152434fbb CRs-Fixed: 918706
| * | | | qcacld-2.0: Fix GSCAN event prcoessing during WoWRajeev Kumar2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - During WoW GSCAN events are encapsulated in WoW wake up event - Add change to use low level WMI TLV check and pad APIs to decode encapsulated GSCAN events properly from WoW wake up event Change-Id: I71ac4fdd438f92041673b26a7681316c60fbc53d CRs-Fixed: 924211
| * | | | qcacld-2.0: Prefer ini params logging preference over code preferenceLokesh Chouhan2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously trace logging levels are set from cfg.ini for different modules which again over written by code. Ultimately code logging preference was taking place. After changes if the log level for any module is set to DEFAULT(0xffff) then only code logging preference will be used else cfg.ini logging will be preferred. CRs-Fixed: 875973 Change-Id: Ia3df86908cec1d5c487d614a418721c0cd98fc52
| * | | | qcacld: Send TDLS setup request and response with VI tidPradeep Reddy POTTETI2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prima to qcacld-2.0 propagation. Send tdls mgmt frames with VI tid to give more priority to tdls mgmt frames. CRs-fixed: 873749 Change-Id: I9196680f09678185c1010b472851c1aca00b1635
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-30 03:26:28 +0000