| Commit message (Collapse) | Author | Age |
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.30
Change-Id: I7d60d82a44ff5e20afa469ee24c72031d4043857
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently whenever country code changes, nvtable is updated
only for channels which are enabled in wiphy.
vos_update_band updates wiphy on basis of nv table.
There can be an issue when band change, country code and again band
change happens.
Driver will not have channel information to enable channels for second
band change as at the time of driver change nv table will have only
channels associated with previous band.
Now with this fix, nv table will have all the channels.
Along with channels nv table will store wiphy flags as well.
vos_update_band will update those flags whenever band
change happens.
Change-Id: Ia1d7d85cd0acbfa95e23410825559506253a579c
CRs-Fixed: 978660
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Current logic use the "not present" structure tDot11fQosMapConfigure
to calculate the array index which lead to the array overflow and
crash of VosMCThread. Add check code to avoid this problem.
Change-Id: Ifa08b24a06e409fed1bd445574127fef02f21d19
CRs-Fixed: 978582
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Just delete the station but not send deauthentication in "limProcessAuthFrame"
when station is connected. Fuzz test tool considers the deauthentication
response as one failure.
Change-Id: I480c677ccad2b64b193fd10815b297348b55ddb3
CRs-Fixed: 979147
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RF bands attribute of WPS IE in Probe.Req from STA/P2P device
is 2.4 and 5GHz although BandCapability=1 (2.4GHz) in qcom_cfg.ini
file. Set the value of RF bands attribute of WPS IE by checking
return value of function hdd_is_5g_supported and value of
BandCapability in qcom_cfg.ini.
Change-Id: I7a60ef79336c586dbad35308e958563c5205888a
CRs-Fixed: 979025
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
Change to initiate BUG report in case of fatal event
Add INI support to Enable/Disable it.
The fatal event handled are as below:
- Roaming failed after successfull preauth.
- MC thread is Stucked for 15 sec.
- Sme command timeout.
- PE defer queue is full.
- VOS run out of message wrapper.
- Management tx timeout.
- HDD level wait for event timeout.
Change-Id: I46fb96e1d90f4ab6df2b9f343a0bfc75cb89a417
CRs-Fixed: 912560
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add counters in the txrx layer to calculate the tkip and ccmp replay counters
for the mib stats.
Change-Id: I89b1f38d7b488252cd131a0ad08baf76746a8c79
CRs-Fixed: 982186
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
For packet logging, extra 24 bytes are seen in both management
and data tx packets. This causes packets to be seen as malformed
in parser. Fix this by using skb->len.
Change-Id: I3aeacd94f57bd856877faac9b644d3ab9ff7bf90
CRs-Fixed: 982302
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
currently txq of MCAST_BCAST packet is using tid
HTT_TX_EXT_TID_NON_QOS_MCAST_BCAST when inserted into scheduler,
so use same tid when flush
Change-Id: I7b32e518e9e31a65ec96daeaabd3b9a79d3e1693
CRs-Fixed: 979681
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
fix compile error when enable pe module log
Change-Id: I4c3b26cda5230770a746fca00a389f1c1d70324d
CRs-Fixed: 982746
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.29
Change-Id: I6bee183f604250197810d20f1b0ff69789862906
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
CNSS platform driver refactored the PM QoS request API
to pass the type of latency requirement needed by the client
instead of hard coding latency type. Add latency type as a
function parameter for PM QoS request API.
CRs-Fixed: 972777
Change-Id: Ibd340f78df0388a8fad8847c61ff097e9b6f302c
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, On sending disassoc from HDD lim will process
disassoc and clear's session of station and thus leading to
drop deauth in lim since context is already cleared. Hence
deauth frame is not sent from SoftAP although deauth command
is executed on hostapd_cli.
Fix will ensure to send disassoc command through new API
and doesn't clear's session and the same is cleared after
sending deauth.
Change-Id: I912a91f1df4001bb2d4f1f0d6031cc102d1bbd65
CRs-Fixed: 981121
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
As per currunt logic in the driver, channel 9 is never allowed
as HT40+ in non-FCC regdomain. Also channel 8 is allowd for HT40+
in FCC domain. The logic used in populating the 40Mhz valid center
channels doesn't consider the proper channel offset to
enable/disable the 40Mhz center channels and Sometimes disable/enable
the center channels belonging to some other channel, especially
when the edge channels are handled.
To avoid this issue while populating the 40Mhz valid center
channels, use the flag IEEE80211_CHAN_NO_HT40PLUS and
IEEE80211_CHAN_NO_HT40MINUS to get the proper center channel offset
and enable/disable the 40Mhz center channels corresponding to the
current channel.
Change-Id: I5677711ea77200b1944577bdaeecd5982ecf5e2d
CRs-Fixed: 775312
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If param extra of __iw_get_scan is null, it will cause crash, so check
the param.
Change-Id: I4fdcec9a88331f7b2566d541c1de05a967690653
CRs-Fixed: 979671
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.28
Change-Id: Ie8f27162fa704eaad62ecdedd0e2a8125a272b2a
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
1) Whenever the beacon request measurement is done, always
send a beacon report despite finding any AP's or not on the
requested channels
2) Send the report always so that it implicitly also cleans up
the RRM context in the LIM and enables to process the
subsequent requests. Otherwise, the cleanup is not done and
RRM processing will be stuck
CRs-Fixed: 982133
Change-Id: I3ce023fbd4aa9d18f8d025a220a5c1d979a555f5
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We do not support TDLS on DSRC so do not encode DSRC channels
in TDLS frames.
Change-Id: I3ad523ab21d1383df189d3856f6e0759b1a2bb6a
CRs-Fixed: 975657
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation.
DUT is enabling QOS based on fixed capabilities in host which
is leading to issue of sending data frames withou QOS header
even though peers are capable.
Fix is to ensure that QOS will be enabled by interpreting
WMM IE.
Change-Id: I852326f0ab27ae87bb354fc3c9eea90f425e653b
CRs-Fixed: 955872
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, the QOS capability of the TDLS link is updated
based on the BSS capability. Thus, if the BSS is not QOS
capable, the TDLS link eventually is not considered as QOS capable.
To address this, update the TDLS link with the TL with the
QOS capability based on the TDLS handshake between the peers.
The information of QOS is obtained to the driver through
the change_station callback from the supplicant and thus
the information is updated to the TL accordingly.
Also, this commit advertises that the station is QOS capable
by default in the TDLS setup request /response handshakes.
Change-Id: I6a36fd77b333e66e8c030f5230b4aaaee6d7a00c
CRs-Fixed: 776081
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
While suspending threads suspend complete event is set before
resume wait event is initialized.
In case resume is followed by suspend there might arise a condition
where resume wait event is set even before its initialization.
Thus after initializing the wait event thread will keep on waiting
on the event and thus get stuck.
To avoid this initialize the thread resume wait event before
setting the suspend event.
Change-Id: Iaffacd23f363f386fbaef4de066784cfd4d9e139
CRs-Fixed: 972287
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.27
Change-Id: I5350eb01103311f3240078a4379a211350f54c22
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Capture WMI version in a global variable for crashscope
to extract WMI logs.
Change-Id: I2f06eaf182bb67dceade397652f801e6311b8f68
CRs-Fixed: 978901
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Do not enable HL Bundle by default.
CRs-Fixed: 972009
Change-Id: I668346346a6aaf09f9b54080d010f181f72b010f
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Due to the race between MCThread and Supplicant thread, After
the ROC callback is invoked from the MCThread where the ROC
context is freed, cancel ROC from supplicant thread is getting
invoked which tries to access the ROC context which is already
freed.
To address this, protect roc context in roc callback while freeing
the ROC context.
CRs-Fixed: 978044
Change-Id: I42c126d0998e16a9c896264d268f03a6c66ef3d0
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently, if no country is set with FCC3_FCCA regdomain
,then default country is picked as 'NA' i.e no country set from the country
list. This causes certain channels to be disabled in the valid channels
list; A valid country needs to be set as the default one. For this
the offending 'NA' entry needs to be removed.
Change-Id: Ib132ff92e1aacc1012e6a1eeb3437be78f7f98df
CRs-fixed: 980447
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.26
Change-Id: I78c66f3a7a8556edccf42457e2519eb57facbc15
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When OCB mode is configured, default TX parameters can be provided.
These default TX parameters are used if a packet is sent without
a TX control header.
Change-Id: I72b3799cb0a9e00a60548facf25e57be241d82d7
CRs-Fixed: 964279
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In case of DFS channels and EBT is disabled, beacons are
forwarded to host in every 50msecs which increase power consumption.
Add the changes to set beacon filter once DUT connect to AP.
CRs-Fixed: 973958
Change-Id: I1a9379eacbd13f8dc7fae08923cd91f087d1b2b2
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rename inconsistent name of the function which is used to check
if a p2p or sap session is connected or not.
Change-Id I0c6606fe5491250cc8340cab0b49ffe709ceec13, added SoftAP code
to csrIsP2pSessionConnected(). So, change the function name
csrIsP2pSessionConnected() to csrIsP2pOrSapSessionConnected().
Change-Id: Ifbc290c1bb67df911329157968e201e20ca39693
CRs-Fixed: 862267
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: I520aca1fc46cf3fbb30d2f068f6da43a2b2986e6 modified
copyright from 2012-2014, 2016 to 2012-2016, 2016.
This fix revert back to the original copyright 2012-2014, 2016.
Change-Id: I44a4db7290b5c59b89e4cf500a683dfd7a9fa24c
CRs-Fixed: 974607
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix compilation issue on 9x07 due to HL
bundling changes.
CRs-Fixed: 972009
change-Id: I31fc69f930a7317e8f9874d94df78e08f7a54de1
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.25
Change-Id: I7a7fcbdd6150be89ae32433905f99c65ea6cbe3e
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
NLMSG_ALIGN adds 1/2/3 bytes if length of data is not multiple of 4.
This can cause length mismatch between nl_payload_len (without header
length) and skb->len. This can cause mismatch in length vs message
available on the socket check in nl and can result in NL discarding
the message. Fix this by removing NLMSG_ALIGN to make lengths same.
Change-Id: I5e513a448a13450b590960ac49462af27e2eb385
CRs-Fixed: 978511
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In SAP DFS test, DUT can't goto suspend if SAP started
on DFS channel and later switched to non-dfs channel due to
Radar detected.
During SAP Starting, driver will acquire the wake lock
for dfs channel by hdd_hostapd_channel_prevent_suspend
in the eSAP_CHANNEL_CHANGE_EVENT event handler. But the SAP
is still in STOPPED state. We acquire the wake lock again
after SAP started in eSAP_START_BSS_EVENT event handler.
This causes driver to acquire wake lock twice for the
same dfs channel. And finally causes the device can't
suspend normally.
This change add check in eSAP_CHANNEL_CHANGE_EVENT
handler to only call hdd_hostapd_channel_prevent_suspend
when SAP is in started state to avoid lock/unlock mismatch.
Change-Id: Ief90697b7b6f19f6fcf0ab94f973a37e74ca3366
CRs-Fixed: 972657
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add logic to queue and bundle packets before
giving it to scheduler to ensure predictive HTC
bundling to reduce SDIO overhead and improvement
in TX throughput
CRs-Fixed: 972009
Change-Id: I5135adf62a83fbb457c0ee09dbe5d7ae6abd661d
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently extscan_results_available event is posted to user space after a
bucket scan is completed. If the extscan start request is configured for
multiple buckets, then the user space application tries to fetch cached
results on every extscan_results available.
If the get_cached_results is issued with flush=1, then every get_cached_results
will have 0 scan results and since flush=1 is set, due to a bug in firmware
even the temporary scan cache is flushed, there by we miss reporting the
APs found in the previous bucket scans and only the last get_cached_results
will report the APs found in the last bucket scan. Whereas the expectation is
get_cached_results must report all the APs found in the complete scan cycle.
The proposed fix is in both firmware and host:
1. Firmware to ignore get_cached_results flush=1 and not to flush the temporary
scan cache in the middle of extscan cycle.
2. Host to consume bucket_started event within host driver and map
extscan_results_available with cycle_complete instead of bucket_complete.
Change-Id: I399204261fa3d8515146c590630a3bb663ee801c
CRs-Fixed: 975402
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
prima to qcacld-2.0 propagation
sme_RoamConnect() has a direct path to call hdd_smeRoamCallback(),
which will change the conn_state.
If direct path, conn_state will be accordingly changed to
NotConnected or Associated.
Driver is not changing connection state to eConnectionState_Connecting
when connecting with iwconfig.
If connection state is not changed, connection state will remain
in eConnectionState_NotConnected state.
In hdd_AssociationCompletionHandler, "hddDisconInProgress" is set
to true if conn state is eConnectionState_NotConnected.
If "hddDisconInProgress" is set to true then cfg80211 layer is not
informed of connect result indication which is an issue.
Change-Id: Ieeaef582a04aa90ddcdcc373b00b68442c795337
CRs-Fixed: 900008
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Wake up logger thread to flush packets to user space when last
packet is reached. This can help in collecting all tx/rx packets
during connection.
Change-Id: I87e3b9635b4a3bc7a62709c02555a20e9380d310
CRs-Fixed: 978524
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.24
Change-Id: I87d672c3647da789df3936a2a5512391534118d8
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Observed kernel panic due to the race between initialization of
logging wait_queue in supplicant thread context and the same
uninitialized wait_queue is referenced in MCThread context.
To mitigate this issue, don't send logs to upper layers if logging
service is not initialized.
Change-Id: I96e3efb3947279be64b83a27a7e2458d04021c4e
CRs-Fixed: 963275
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per the current implementation band_center_freq1 is kept same as the
channel frequency in VHT 40 channel width in 2.4GHz and there are
references to MODE_11AC_VHT80_2G channel mode which we wont support.
Ensure proper updation of band_center_freq1 in MODE_11AC_VHT40_2G and
remove unused references to MODE_11AC_VHT80_2G.
Change-Id: I9f37bcbe9a7cde58516466e0d078791b21794a67
CRs-Fixed: 977272
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
After sdio cmd 53 timed out sdio core driver failed to initialize
the sdio func device private data structure. Check against NULL
pointer in driver cleanup before use to avoid crash.
CRs-Fixed: 978067
Change-Id: Ib76f375eb55d4ebfd60ec39eb8fc13515d4361fa
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
From the current logs there is no information whether the offload
IPv6 address type is unicast or anycast.
In this change, modify the logs to indicate the IPv6 address type.
Change-Id: I7ec757223689225357e903d223c72f18e35985d5
CRs-Fixed: 977084
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.23
Change-Id: I6d565a69786b5a7dc4f123f5bfac19e3c28cb5c3
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
qcacld-3.0 to qcacld-2.0 propagation
11P channels are wrongly retrieved along with other valid channels
while using csr_get_cfg_valid_channels function call.
AS per the current implementation the above function call is used
to get the valid channel used for scan and roaming scenarios. Since
11P channels are not valid in scan and roaming scenarios
csr_get_cfg_valid_channels function is updated to retrieve non 11P
valid channels.
Change-Id: I25567b2791ac776480534534e10d900c2f9a6184
CRs-Fixed: 965218
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If SME posts message to WMI after vdev_detach happens,
there can be a race condition.
In this case VDEV_SET_PARAM will be called after VDEV_DELETE.
Fix this with introduction of new Boolean flag "is_vdev_valid" which
will be true after VDEV_CREATE is done. This flag will be false
when deletion of vdev happens.
WMI will do VDEV_SET_PARAM only if "is_vdev_valid" true.
Change-Id: Idffd0979bd9bdefa1225d2ea6a24180d81000f48
CRs-Fixed: 964146
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per current implementaion whenever ACS is enabled via
INI all the update beacon from cfg80211 module fails because
sapconfig channel points to AUTO_CHANNEL_SELECT(0).
When driver ACS is enabled skip channel validation to fix
this issue.
Change-Id: Ie3e7d19332629fc860752b2240690fd6a15bb0a2
CRs-Fixed: 977101
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The delayed service for an asynchronous SDIO bus request
in async_task will block following SDIO bus requests. This
will introduce bad influence to TCP TX.
Once efficiency of bus request release was improved, there
will be a great improvement for TCP TX t_put on SDIO HL
card. So a thread for TX completion is created in this change.
Change-Id: Ia96f471b1d2c8782374f71242e5c2a1014eea7c8
CRs-Fixed: 961642
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.22
Change-Id: I74b58af5fd6e3628dbd808cf049b1b45f38d8c88
CRs-Fixed: 688141
|