| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.113
Change-Id: I600b9423f8043f8edf5e771208621e86383717ce
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
Resolved static analysis issues, variable initialization,
return on failure, validate data before using.
Change-Id: Ia6ffd422ae3f9bc8419f32aa914839a091841335
CRs-Fixed: 975049
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
From Kernel-3.18 onwards pending scan request is handled
as part of NETDEV_DOWN event, by invoking the cfg80211_scan_done
callback which frees the scan request structure. To support this,
driver will not invoke scan_done_callback if interface is down.
In case, if interface down and up are called back to back there
is a chance that kernel frees scan request as part of NETDEV_DOWN
and after which before driver triggers scan_done_callback if
interface is made up, driver scan_done_callback is through its
execution and accesses the freed scan request results in kernel
panic.
To mitigate this, don't return from hdd_stop until scan request
is aborted. Though this fix is to avoid kernel panic due to 3.18
kernel specific changes, it is acceptable across all the kernel
versions.
Change-Id: Iba8bd7a32fac33e8a0c3eea293aad682a1105397
CRs-Fixed: 977264
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
If Probe Responce received in PNO indication does not
contain DSParam IE or HT Info IE then add dummy channel to the
received BSS info so that Scan result received as a part of PNO
is updated to the supplicant.
Change-Id: I25ac973cc90fc9f5258ff8f012c90dd9e9394eb0
CRs-Fixed: 629288
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The current DBG message array is quite old, it miss many update
according to dbglog_id.h. Update this array to match the latest
dbglog_id.h
Change-Id: Ia0adc7a73c85bc9feacc57620ef98d686c8e15d0
CRs-Fixed: 1032801
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since wiphy register is done before we configure band information
using ini parameter, wrong channels are being updated to the
supplicant through linux_reg_notifier, which is causing p2p
connection failures.
This commit ensures that channel list for configured band is updated
before linux_reg_notifier is called.
Change-Id: Ie0c68a24befad9806b366e1e1e7e686bdfc71ddd
CRs-Fixed: 1021751
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In __wlan_hdd_cfg80211_scan(), no.of channels printed as received no.of
channels from supplicant instead of filtered no.of non DSRC channels.
Fix to update the correct no.of channels
Change-Id: I5f424a043535b0fdcc7886ba062b34fbc2e6dca0
CRs-Fixed: 1036775
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.112
Change-Id: I6c46125c192546f2d585dc8d773e4778c19abc9e
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
P2P action frame confirmation can be called from work queue
wma_mgmt_tx_ack_work_handler as well as from MC thread during
remain on channel completion. So it can lead to race condition
where frame confirmation is called twice and driver tries to free
frame buffer twice.
To avoid this use PE global lock to detected duplicate call for
P2P action frame confirmation.
Change-Id: Id193b5a979fad5effa7c6b00d89452ad876ae00e
CRs-Fixed: 1035077
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Host gets the config value in ini file and send WMI_COEX_CONFIG
command with the config type and the config values to firmware.
CRs-Fixed: 1035630
Change-Id: Icf72a5113d3ea15bf9698d22c8891f8da4b1067c
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
On HL platforms, Ramdump collection is taking significant delay.
Increasing 100 more sec before driver crashes in rmmod context.
Change-Id: I10f1d6ec37deb5ead36e3dbaf9ad9db513d24f82
CRs-Fixed: 1035251
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Due to commit Id574e1309db8d8b01b4765e27b3638bb92c3d5a0,
Host stop memory tracking before trace-buffer get free.
Later host try to free the trace_buffer but memory list
is empty hence vos_bug raised in SLUB enabled build.
As a part of fix, Free trace-buffer before vos_mem_exit
and free trace_buffer in insmod failure case.
Change-Id: I75ef52a7dc286d8bea012b1e2b8ccf57343a3575
CRs-Fixed: 1036271
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.111
Change-Id: I35e3b32b78d5682401521c9111d50ecac94b0e19
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In the hdd_wlan_startup function correct the error conditions in case of
any initialization failure, there is crash instance where in the nl socket is
initialized but not released by the driver incase of vos_open failure.
Release the nl socket during the load failure and also correct the other
error conditions.
Change-Id: I5eb63b42de0f2327b391427dd5b43235103ed06b
CRs-Fixed: 1033220
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit Ie963f80b3c3e5ea5e4dd0f46b3dbdbea9d6c7f49.
Change are causing crash in ACS enabled scenario.
Change-Id: Icbd195702dd70f5bbb97eefc2c3044d0e46a76e4
CRs-Fixed: 1035799
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.110
Change-Id: I4d2b7c578001ae10c05814dcbefbbea541ddf502
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Cleanup as part of limP2PActionCnf triggers only when
mgmtFrameSessionId is not 0xff. If cleanup does not happen
in error scenario, it can result in not clearing cfgState->buf
which can lead to dropping of further action frames in
__wlan_hdd_mgmt_tx. Fix this by filling mgmtFrameSessionId
with proper session id.
Change-Id: Icc0f5b576ff71776dc448a673b6e12defe0c514e
CRs-Fixed: 1033836
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add NULL check for adf_ctx before using it in ol_tx_ll.
Change-Id: Ice4c32caf65f5fc6fceaf3fbcf536baabd58f716
CRs-fixed: 1035125
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently there is only one ini item gSoftApMaxPeers
to configure max SAP clients number, and this item will also affect GO
clients. Add another ini item to set GO clients number.
Change-Id: I9aaacf035efb042f8216ca0d7f1ec3f21f11b212
CRs-Fixed: 1023547
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The station_info_flags is removed from cfg80211.h since Kernel 4.0.
Since they're duplicate information that's already in nl80211
attributes.
Change-Id: I7c8e2f2dabd5713cb25523df5b25e59d0c4b06aa
CRs-Fixed: 1033754
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.109
Change-Id: I867b6007e3ed6d0fc70b0242be668d922e148ab8
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
WLAN_FEATURE_MBSSID flag is originally added to support MBSSID,
specifically for the MOBILE ROUTER build, and is now enabled
for all builds, there is no longer need to have a separate
feature flag, so remove it.
This commit cleans up the following modules - voss/mac/sap/sme.
Change-Id: I79ad9767b7945af0c567b6294ac07e7697898e9e
CRs-fixed: 1023038
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In current driver, WE_UNIT_TEST_CMD has below problem.
- apps_arg[1] can have zero value and can lead to
buffer overead
Change the code to handle the number of args if user has
given zero.
CRs-Fixed: 1029540
Change-Id: Idc8e1d77d9623daeb98d0c4b7ad8a8d6cfa9c2d2
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
hif_reset_target is not defined for HL target without platform
driver, this is causing driver load failure in x86 SDIO
platform. Fix driver load failure for x86 SDIO platform.
Change-Id: I3e52ec63d8d0f027f0fec953f8728db71c91c235
CRs-Fixed: 1030729
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If a PMF Sta is already connected to one interface and try
to switch to other interface without sending deauth/disassoc,
sta entry is not deleted from previous vdev and one more entry
is created on current vdev. Due to this htt is not able to get
valid peer for EAPOL packets and EAPOL packets are dropped leading
to connection failure.
To fix this, Add check to delete PMF Sta from one vdev when
assoc request is received on another vdev.
Change-Id: Ida2e20fe08af3c6ed426822a71db1fd6854a0bea
CRs-Fixed: 1033224
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, Host free the packet trace buffer in the beginning
of hdd_driver_exit. But same freed packet trace buffer is used
during Hdd disconnect handler in MCThread context .
As a part of this fix, Host free packet trace buffer in the end
of hdd_driver_exit which ensure all thread's are stopped at that
moment. Apart from it, add few sanity checks and error logs.
Change-Id: Id574e1309db8d8b01b4765e27b3638bb92c3d5a0
CRs-Fixed: 1028095
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When the driver is configured to "force SCC" mode by
gWlanMccToSccSwitchMode = 2, in STA+SAP case, the
driver will check the SAP channel to avoid the
MCC in same band(2.4G or 5G) and override if necessary.
During ACS process, the SAP sapContext->channel is 0.
The driver doesn't validate it before uses it in
sapGotoChannelSel when applies the "force SCC" logic.
That causes an invalid channel selection for the SAP.
And finally causes the hostapd starting failed.
This fix is to skip the override logic if the
sapContext->channel is 0. When the SAP is starting with
a valid channel, the override logic will be activated
again.
Change-Id: I8e3d171ac47d8be149df98ae3e30c8df391a15b0
CRs-Fixed: 1033277
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, capabilities suBeamformeeCap and muBeamformeeCap are set
during association request but not in re-association request. This
can lead to failure in beamforming after roaming. Fix this by updating
them during roaming as well.
Change-Id: I28e86b93a5114f3b76733effe4428a92cf94b441
CRs-Fixed: 1033328
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
Currently, variable hdd_ReassocScenario is not reset during
11r roaming. This causes rssi value to be stale during 11r roaming
as rssi doesn't gets updated when hdd_ReassocScenario is set
in wlan_hdd_get_roam_rssi/wlan_hdd_get_rssi. Check for
11r association using pRoamInfo->is11rAssoc as well before resetting
hdd_ReassocScenario. This check for 11R association allows
rssi to be updated during 11r roaming.
Also, add a check for 11r association to allow other functionality
during key complete for 11r roaming.
Change-Id: Ie1b4b205618d6744a15cd27e2b8f1391f76564c9
CRs-Fixed: 978677
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When HT40 rate flag is set, it's likely that packets are sent in
HT20 rate, therefore, the driver need check HT20 rate set to
calculate mcs index.
Change-Id: I29022ec26d72a5361f152dc20af13783d0dac984
CRs-Fixed: 1027530
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Consider the parameters 'acs_channel' and 'acs_dfs_mode' only
when ACS is enabled for that SAP. Otherwise driver is going to
override the channel even if user configures a fixed channel in
hostapd.conf file.
Change-Id: Ibe24828690ace91338ade10fd00c49fc4acdbd81
CRs-Fixed: 1026420
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
qcacld-3.0 to qcacld-2.0 propagation
Add new user country XA to regulatory tables. This is an 'engineered'
country for Japan that has channels 5150-5230 marked as passive.
Change-Id: I6c582bc0635ecae2c37b98d761f72f222c408d2f
CRS-Fixed: 1007217
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.108
Change-Id: Iab8e95eeb2464bf7189d240f8f8834c0bf235a42
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
APPS crash due to invalid access of device pointer during self recovery
as the Ramdump Global Pointer is not initialized.
Initialize Ramdump Global pointer before scheduling work for self recovery.
Change-Id: Icc606743da144958bc936f5ee22393dc135731bf
CRs-Fixed: 1033917
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently Host configures MaxTxPower as 22dbm
during join which fails the TRP requirement to meet
23dbm.
Change the code to configure the max tx Power to 30dbm
in FW during join.
Change-Id: I926288972e17a9276af2744d6a070b82333d5242
CRs-Fixed: 1023616
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When Dut is configured as 1*1, after roaming to 2*2 AP,
the linkspeed is not right, it will display 144Mpbs rather
than 72Mbps. Because it uses wrong peer_nss and
peer_rate_caps in WMI_PEER_ASSOC_CMDID.
Change-Id: I8700621fbef9c9b4867ac698f7f721d4ffb7d967
CRs-Fixed: 1031447
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.107
Change-Id: I31d32b2ea9a3c85ea976d4c04c322e38ca07c07b
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Unmap a previously mapped buffer if host fails to en-queue
buffer to CE destination ring.
Change-Id: If23398b01124638cfb266f5755fc9e45d3969ac9
CRs-Fixed: 1033307
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When driver receives channel avoidance event, it sets the flag
is_ch_avoid_in_progress and sends LTE Coex event to application
to restart the SAP. In legacy implementation, the application used
to reload the driver on receiving this LTE Coex event.
In current implementation application is just restarting the
corresponding SAP interface. So the contents of pHddCtx still valid
after SAP restart.
The variable 'is_ch_avoid_in_progress' is also one of the parameter
of pHddCtx and valid after SAP restart. If we dont reset this after
start bss then it can lead a scenario where driver ignores the LTE
Coex event based on previous value of variable
'is_ch_avoid_in_progress'.
Change-Id: I7e9301323410e0e2ae456aa30da9c628dd7841c2
CRs-Fixed: 1032857
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In pe_reset_protection_callback psession's beaconParams struct is
reset to 0 and thus short preamble support being part of this
structure is set to 0. Due to this beacons always have barker
preamble set to 1 even if no non short preamble enabled STA is
connected.
To avoid this do not reset the short preamble support and beacon
interval in psession's beaconParams structure.
Change-Id: I631fb202fba6bc129d03ff21cff2adef328abff2
CRs-Fixed: 1032578
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.106
Change-Id: I255364eb3482c046f256adc68e435233ac4e571f
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Sometimes it is possible for the host to receive the ack for
go negotiation request after the go negotiation confirmation
is sent. So supplicant assumes go negotiation confirmation is
success though it is not and results in connection failure.
To address this, drop the pending ack for the go negotiation
request. so that the supplicant will wait for the ack of the
negotiation confirmation.
CRs-Fixed: 1032185
Change-Id: I54f305319e23b1ffcbd54cc6e7dcc74d39a2e511
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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)
Change-Id: Ie963f80b3c3e5ea5e4dd0f46b3dbdbea9d6c7f49
CRs-Fixed: 1013559
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, Host uses the separate startup_task for calling
hdd_wlan_startup and break insmod context. Essentially all
the operation performed in startup_task can be performed
in insmod context so this task is not necessary. Due to
having a separate task host have the following issue, assume
wlan driver probe get fail then startup_task becomes a zombie
thread which may lead to invalid access.
As a part of this fix, host call the hdd_wlan_startup in
insmod context and remove the startup_task.
Change-Id: I0ac8b4ef01f91539852935242176e6c1f0f3ba25
CRs-Fixed: 1027526
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add changes to dump stack only once. Also, change thread stuck
timer to 10 seconds from 5 seconds (THREAD_STUCK_TIMER_VAL) and
probe thread only when thread stuck counter is zero to avoid
out of wrapper messages. Remove unnecessary error logs also.
Change-Id: I6c2ab331256b190fd0ce67f8fb95ed4d7cb5e61a
CRs-Fixed: 1032098
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
SKB control block size limit is 48 byte, add compile time assert
if SKB control block is exceeding 48 byte.
Change-Id: I169e79f6033096f8d4325657dc3a94677e1ea54d
CRs-Fixed: 1020119
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.105
Change-Id: I52d4d2d4f1859197d836001aa961d0bf7581d3a9
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
wlan_tasklet is scheduled recursively if there is any pending
packet to process. Set ce_suspend to true after tasklet completion
to prevent race condition between wlan_tasklet and hif_pci_suspend.
Change-Id: I87f82c5faf7e3c8343c8bffcb421a78c1ab47d61
CRs-Fixed: 1032612
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Host asserts as target is stuck in HTC connect message
handler due to mbox UNDERFLOW error. Target register
indicates TX_OVERFLOW and RX_UNDERFLOW error simultaneously.
Reset card to recover from target mbox error.
Change-Id: I38eea06360226322bb4f7fcbf810635b09da5593
CRs-Fixed: 1030729
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
While RTT ranging happens, userspace application initiates FTM
request via host to FW. After sending the FTM request, host
might go to sleep mode sometimes so FW will not be able to send
the OEM response event resulting in poor ranging results.
This change registers OEM response event as WOW wakeable so FW
wakes up host whenever it receives OEM response which helps OEM
response to reach userspace application on time for better
ranging results.
Change-Id: I71b77cfa09c5039b487e9a93490837a084314fb3
CRs-Fixed: 1018887
|
