| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Memory allocated for dfs filters in dfs_attach() API
does not get freed in failure case.
Add changes to fix memory leak issue.
Change-Id: I8c025c25089f64256539a3fa74a2e7e20edb4cc1
CRs-Fixed: 1051017
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change refines 'qcacld-2.0: Extend cfg80211 configure API'.
1. Unit for propagation delay should be micro second, but it is
millisecond in last change.
2. Max/Min values for limits check are replaced by Macros.
3. Refine code style for variable definition.
Change-Id: I1735bc540b9182c724d9fafa6e5e0878d23b96fa
CRs-Fixed: 1035577
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.133
Change-Id: I7651b6a23fa7e88dd1aa951f41eb36ebb1313734
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
IPA Disconnect events are not sent to IPA driver in case
of SSR. This is resulting in mismatch between IPA driver
and HOST driver.
Reset IPA disconnect events during SSR, to have coherent
connect/disconnect counter.
Change-Id: Ie07e5840fc997f41b987fc7e548e1a7e3484c113
CRs-Fixed: 1034712
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
A STA entry is created for each peer joining
the network to take care of the peer specific
capabilities.
The VDEV need not be reconfigured for IBSS peer
with different channel width joining the network.
Change-Id: Iec6ec5d2b510b84538f4e5300b3f1c5cc63b334d
CRs-Fixed: 1046409
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Memory for dfs filter is not getting freed in some cases.
Add changes to fix memory leak issue.
Change-Id: Id8de875729e29be23febd2762994d7a189bab9eb
CRs-Fixed: 1049773
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Error level logs should be used only for error conditions.
Add changes to move unwanted logs to info level.
Change-Id: Ib5b3e1235ad36cf0594291f33e84758261e4d422
CRs-Fixed: 1049765
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.132
Change-Id: Ie039febd305a6d16986776b96fd1d1ba3e357cc9
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
wlan_tasklet is being rescheduled recursively if rx packet
pending count is greater than 0. In some cases during SSR
tasklet is being rescheduled as tasklet_kill ensures
synchronous execution of current running instance, it
does not stops the new instance if tasklet is being rescheduled.
This is causing null pointer deference of ol_softc object
in softirq context which is being deleted in SSR context.
Disable wlan tasklet to avoid rescheduling during SSR.
Change-Id: Ic267baf5a08611e20dc0592532ae0a2f16682240
CRs-Fixed: 1049051
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
hdd_bus_bw_compute_cbk function is responsible for computing bus bandwidth
by checking TX/RX stats per HDD adapter after taking them from adapter list.
However, it's scheduled on a global timer so the following scenario can arise:
1)At time of scheduling, HDD adapter is valid and is passed.
2)During TX/RX stats check, HDD adapter is freed as a result of interface down.
3)Null hddCtx from adapter is accessed as a result and kernel panic occurs.
Thus,validate adapter magic before accessing the hddCtx stored in adapter.
Change-Id: If076e122db0538d01140e16305f046e68a86212a
CRs-fixed: 1045004
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add API to find IPV6 mcast packet to use it in wma_wow_wake_up_stats
func. This is required to know if there is a IPV6 mcast packet embedded
in a link layer unicast packet.
Change-Id: Ic2af69032262237b8751019817ae181913346818
CRs-Fixed: 1049254
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
RTC timestamp is not calculated correctly in proto trace.
Add changes to correct timestamp.
Change-Id: I285d675bb2bbc06b951b5a4a55e31d8b0bfa7334
CRs-Fixed: 1049701
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
OEM requires to enable/disable runtime pm dynamically when driver
is functional.
Provide debugfs interface to support this requirement.
Usage:
echo 0 > /d/cnss_runtime_pm -> Disable Runtime PM
echo 1 > /d/cnss_runtime_pm -> Enable Runtime PM
On SSR, if user has vote to disable runtime pm,
we disable runtime pm once SSR is complete.
On Driver Reload, the driver comes back to reset state.
User has to vote if needed to control runtime pm.
CRs-Fixed: 1049662
Change-Id: I21756f4da251eb4a4a5e7c4ea0afc9c5a918d293
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.131
Change-Id: Ie9ddee5f9f4ec346444023bc788c9e0b5798d3b6
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Correct the updation of various wow wakeup counts.
Change wow_icmpv6_uc_bc_count to wow_icmpv6_count
as there is no broadcast in case of ipv6.
Change-Id: Iceaf1226edbf909ca3881e049c33f7d121860ef2
CRs-fixed: 1049254
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some Fatal events requires SSR to be triggered after bug report is
completed. The API used to trigger SSR is vos_trigger_recovery(),
but vos_wlanRestart() is used in this case.
To fix this use vos_trigger_recovery() API to initiate SSR on
fatal events.
Change-Id: I29d45f69a9c0e4eb528d017cb54c151366513d67
CRs-Fixed: 1049133
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If stale PE session is present during join and rejoin request, then trigger
bug report and SSR.
Change-Id: I0f6bd3996959184daa4672adb82f33a67c9b134f
CRs-Fixed: 1049113
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If roaming is initiated by firmware, after getting the candidate
list the CSR will start preauth with the candidates and thus
preauth will be the active command in SME.
Now if at the same time connect is issued from supplicant,
HDD will queue disconnect cmd in SME queue and wait for disconnect
to get complete for 2 sec. Now there is a chance that channel
change along with preauth timeout can take more than 2 secs.
In this scenareo the disconnect will timeout in HDD and will
return connect failure to supplicant. Next supplicant will issue
disconnect which is ignored by HDD as disconnect is already been
queued in SME. Now if supplicant again sends the connect command,
as part of connect command CSR will remove the disconnect command
from the SME queue and queue this connect command.
On preauth timeout the preauth state machine checks if disconnect
is queued and if it is queued it will abort preauth. But in this
case disconnect is removed by the connect request and thus preauth
retry continues and if preauth is success handoff will be queued
in SME queue.
Now the connect request is processed and if this connect request's
BSSID is same as the BSSID of the roam candidate, as all the CSR
states for this BSSID session indicate roaming, instead of
join it will try to reassociate and continue changing the CSR states
again. Eventually this connect will fail. Next the handoff command
is processed and as part of handoff it will try to cleanup
original session, but as CSR states are changed by connect request
the original session is not cleaned up properly. This results in
stale PE session entry which does not allow the scan to be sent to
firmware, returning the cached results and thus 0 scan results.
To fix this:
- Increase the WLAN_WAIT_TIME_DISCONNECT to 5 sec to make sure all
sessions are cleaned up before allowing the new connect to proceed.
- Increase the priority of preauth scans.
Change-Id: Id7cc1e6f3c31df8a8c8955eb3ff48cb60e5b5ab2
CRs-Fixed: 1048394
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently the driver does not report HT TX STBC capability
to the kernel. This prevents hostapd from starting if it
has been configured with HT TX STBC capability. To prevent
this issue correctly report the HT TX STBC capability to the
kernel.
CRs-Fixed: 1046306
Change-Id: Id182de3916f4e556dde30048776ea07b0fbfdc7d
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.130
Change-Id: Ib10500ea4e94f246b171783634597263b24ba3b9
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.129
Change-Id: I76042fc086e24dcfbb9c9e8d996c5a073f75375b
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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: 1018460
Change-Id: Ia14b84f1039dc4ffec6ad63550fed21e932f8012
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Reduce log levels and cleanup.
Change-Id: I05f88b7a49c4fc9c531dfe1574f38da2b416c827
CRs-Fixed: 1047807
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.128
Change-Id: Ibed4210488ecdd4abe868ec6d9f422d4706840cb
CRs-Fixed: 688141
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adding WMI defs for pdev and peer GET_ANTDIV_STATUS_CMD,
ANTDIV_INFO_EVENT msgs.
Change-Id: Iad3c57f0b4e10e68c86cef175b8cadcfd9e7fe1e
CRs-fixed: 865207
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adding new event for NAN Wake up with zero length.
Adding WMI_EP definitions.
Change-Id: I3940ffaf856fe9697818b6e56df3a49bf4750af0
CRs-fixed: 865207
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Define mechanism for WMI_SERVICE flags beyond 128.
Change-Id: I0832f646e76d3e883a36ce3d5d6a63ad7bf83a4c
CRs-fixed: 865207
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adding ANT_DIV WMI_PDEV_PARAMs.
Change-Id: I473e46c1236140c780059d2877e573bbe22b1586
CRs-fixed: 865207
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Release 4.0.11.127
Change-Id: I2ce7ca1165767e023d3f8f468fa005bbc451bb54
CRs-Fixed: 688141
|
