Age | Commit message (Collapse) | Author |
|
into android13-msm-pixelwatch-5.15-eos-release.
Change-Id: I9593dcdf9026cc1cf46ac1ece31b81b9af67233e
|
|
Bug: 300993484
Signed-off-by: Andrew Evans <andrewevans@google.com>
(cherry picked from https://partner-android-review.googlesource.com/q/commit:af3b30c9ba16eadd5d7e574c4c92930b7ec8e7c1)
Merged-In: Ib5bb450eb07c97da75d5343475bed3340d8be38f
Change-Id: Ib5bb450eb07c97da75d5343475bed3340d8be38f
|
|
into android13-msm-pixelwatch-5.15-eos-release.
Change-Id: I38728ce7673c91f217de0d3102453552f2146bdb
|
|
Currently, wakelock with timeout is acquired when psoc idle timer is
started to prevent suspend but it is not released when psoc idle timer
is stopped.
So, in scenarios where wlan is turned off/on frequently, psoc idle timer
will be started and wakelock with timeout will be acquired as part of
wlan off but after wlan is turned on suspend will not be allowed until
wakelock timeout occurs as wakelock is not released when psoc idle timer
is stopped.
To allow suspend after wlan is turned on, release wakelock which was
acquired as part of wlan off in psoc idle timer start.
Bug: 292006634
CRs-Fixed: 3578872
Test: Wifi Basic function is workable, Wifi On/Off stress test
(cherry picked from https://partner-android-review.googlesource.com/q/commit:9eb3194536a684a18cea8eebd09399f134e6ce5d)
Merged-In: I85ad9ce4ae9618a88601295d2194b4033be88c2d
Change-Id: I85ad9ce4ae9618a88601295d2194b4033be88c2d
|
|
This updates our sources to CodeLinaro release
AU_LINUX_ANDROID_LW.UM.2.1.R1.11.00.00.200.040 (LW.UM.2.1.r1-04000-SW5100.0),
which corresponds to ChipCode LW 2.0 r00078.3a.
Bug: 280095980
Change-Id: Ia39bc900fbf7fc5c2106d5ba3e8fd403e606e9fc
Signed-off-by: Daniel Price <danielprice@google.com>
|
|
Point to kernel/private/msm-google:OWNERS_pixelwatchbsp
Bug: 247160135
Change-Id: I93df73b2b464692ef8b5f308c628b13c84099852
Signed-off-by: Andrew Evans <andrewevans@google.com>
|
|
Change-Id: I1049fa61e5810c71420362bffa917b17a064e966
|
|
These options are properly set in wlan/platform, as well as in
device/qcom/wlan/monaco/monaco/wlan.mk (for in-android kernel module
building), but are missing from the Makefile, which is how we specify
our CONFIG_ flags for out-of-kernel module builds.
Return wear_defconfig to its original state, as these options should be
specified in Makefile instead of in wear_defconfig.
Bug: 271455581
Change-Id: Idd9c0a474d7b68ad714e88a2b10931e354417d32
Signed-off-by: Ben Fennema <fennema@google.com>
|
|
Release 2.0.9.17Y
Change-Id: Ia812b87cc3f158104917a83dc0939f4426ca00df
CRs-Fixed: 774533
|
|
In roam invoke scenarios, if FW fails to roam
it will send roam invoke failure.
Until roam invoke failure is received FW is trying
to roam.
Currently if FW aborts roam, host will trigger
disconnect and rso stop is sent due to this FW
is unable to retry roaming.
Fix is to not trigger disconnect at roam abort
and wait until FW sends roam invoke failure.
To handle this store roam invoke params in rso cfg.
Change-Id: I32eeda70ef9f4d8a049fec53053f9e0c6eb36e51
CRs-Fixed: 3433320
|
|
If roaming is triggered by source CM_ROAMING_NUD_FAILURE,
then per the INI gEnableNUDTracking to check whether
disconnect current connection or not.
gEnableNUDTracking=2, keeping the connection
gEnableNUDTracking=3, disconnect the connection
Change-Id: I0f321dcf5f3fc1bf7d0c93fa0d70bf4770ccaf35
CRs-Fixed: 3412213
|
|
Release 2.0.9.17X
Change-Id: Ie17cadfe8fedf22796b7c9104af9e965ac08ea93
CRs-Fixed: 774533
|
|
Currently in CSA path if the target channel is 6 GHz, it is not
checking the keymgmt used and allowing the open security to be
configured.
This changes add check for open security for 6 GHz if check_6ghz_security
ini is enabled.
Change-Id: Ie26ff05dc7c7a97a48398c2a81b091f66c6bd39e
CRs-Fixed: 3413618
|
|
Release 2.0.9.17W
Change-Id: I8845ae6a9431a8e5f13e35c462b2250367d18e01
CRs-Fixed: 774533
|
|
Send the driver disconnect internal reason code as an event to user space
using QCA_NL80211_VENDOR_SUBCMD_DRIVER_DISCONNECT_REASON vendor command.
Change-Id: I19959e097c5709d63fbd941583b934e291c3af1c
CRs-Fixed: 3371396
|
|
Release 2.0.9.17V
Change-Id: Ic12c403feda08a7acb935220e07fb8050c915cd4
CRs-Fixed: 774533
|
|
Firmware do not send WMI_PEER_STATE_CHANGE_EVENTID when WMI_PEER_AUTHORIZE
peer param is sent from host. Host waits for this event from firmware for
10ms and then times out. This leads to unnecessary delay of atleast 10ms
in enabling the TX queues every time after connection and roaming.
So this change cleans up the existing handling of WMI_PEER_STATE_EVENTID
and removes wait for sta_authorised_event. This will improve the latency
in enabling the queues from host.
Change-Id: Iaf54d8298dab3cd47ad4779ec9ee11dc8f0bad0d
CRs-Fixed: 3436763
|
|
Add missing break after the update of ret variable.
Change-Id: Ib9c54575d97d26f05239a2fb44a87a63440b9bdf
CRs-Fixed: 3277218
|
|
Release 2.0.9.17U
Change-Id: I0c40489957e5ad2a1384fa90c99dd68f731fc10d
CRs-Fixed: 774533
|
|
qcacld-3.0: Fix ofdm and cck flag info for mon mode data packets
Currently cck and ofdm flags are filled wrongly for monitor
mode data packets based on preamble and wireshark deriving
incorrect phy type for 11G & 11B.
This change is to update cck and ofdm flags based on packet
type.
Change-Id: I5fcdc463ea2a6d83253e39cc377a2471aeb4e144
CRs-Fixed: 3447567
|
|
Currently, For legacy modes monitor mode reporting incorrect tx rate
for data packet in radiotap header due to packetcapture_hdr rate
is hardcoded as '0'.
This change calculates the data rate of legacy packets using mcs
reported in tx completion.
Change-Id: I2a651b8fb36947672bd30f8a635f0e643219e520
CRs-Fixed: 3442376
|
|
Currently monitor mode HT & VHT data packet tx rate is not
matching with ota packet tx rate due to incorrect mcs value.
This change is to update proper mcs value for HT & VHT modes.
Change-Id: Ib4fb06a06ce35a4e8e683e5a22c8be226492b13f
CRs-Fixed: 3442509
|
|
Release 2.0.9.17T
Change-Id: I8fc59109780760f83767d1448ce14ea58f9a1742
CRs-Fixed: 774533
|
|
Currently host drops an AP from scan list if host country is set to
US and AP country is non-US. This implementation violates our
standard regulatory scan policy.
To address this issue, introduce a new INI to differentiate
between our standard regulatory policy with others.
Change-Id: Ie6bd2d1925048aef427136b34d00d361955f40b2
CRs-Fixed: 3377242
|
|
Release 2.0.9.17S
Change-Id: I0d16f538cd50e8c202ba8dfacad82916326a0ac0
CRs-Fixed: 774533
|
|
Reduce the log level of logging from warn to debug which occurs
during roaming.
Change-Id: I623ce4f6ba9fa4a54e3b06c6833f4630f49d7f44
CRs-Fixed: 3449210
|
|
This updates our sources to CodeLinaro release
AU_LINUX_ANDROID_LW.UM.2.1.R1.11.00.00.200.031 (LW.UM.2.1.r1-03100-SW5100.0),
which corresponds to ChipCode LW 2.0 r00062.1a.
Bug: 276757489
Change-Id: Ia6db76723ebe4697dbee8e8387c6cac25ee2e85f
Signed-off-by: Daniel Price <danielprice@google.com>
|
|
Release 2.0.9.17R
Change-Id: I2fdc4c3675755cc2bcdbd3f939ccc471a7737940
CRs-Fixed: 774533
|
|
Hostapd sends RSNIE with around 18AKMs. However, the driver
data structures allow storage upto 6 AKMs only. Therefore,
the dot11f unpack modules returns BAD IE. The akm suite
however carries the parsed count of 18.
The HDD caller checks only DOT11F_FAILED, which doesn't cover
many of the DOT11F_xx failure status codes. Therefore, instead
of failing BSS, the IE is processed further and access of 18
contiguous AKMs takes place leading to OOB read crash.
To fix this, check for all the failure status code and stop
the BSS upon RSN/WPA/WAPI IE parse failure.
Change-Id: I16399c8a5bd61b09d29cd88e35c0ec441c6b9af4
CRs-Fixed: 3445762
|
|
Enable CoAP(Constrained Application Protocol) feature
for qca6750.
Change-Id: Ie981024d1d71341aa5f8016ae87a8f12257ef607
CRs-Fixed: 3451295
|
|
Release 2.0.9.17Q
Change-Id: Icf35f84f3d497e92b87a8906a97cd5122a43f225
CRs-Fixed: 774533
|
|
Enable CoAP(Constrained Application Protocol) feature
for qca6490.
Change-Id: I756c9cabc8a3f463abba0e06ffe135daaca9e3f6
CRs-Fixed: 3451292
|
|
Enable CoAP(Constrained Application Protocol) feature
for kiwi_v2.
Change-Id: Ib940a1135f7de69c437a276fc8c8ba3cc1a7da5b
CRs-Fixed: 3257898
|
|
Add build support for CoAP(Constrained Application Protocol)
component.
Change-Id: I1578091ddc6348398d3a0dbc1c7378deddf10712
CRs-Fixed: 3257891
|
|
Release 2.0.9.17P
Change-Id: If4bd1d3b02c7757d5539524fb21329e4e360b385
CRs-Fixed: 774533
|
|
Firmware supports CoAP offload for STA mode only in
current stage, reject the request for non-STA roles
to align with that.
Change-Id: Ifa43295d0e800b87d29342038d0a690966a2c238
CRs-Fixed: 3310910
|
|
Pattern id and vdev id are not filled explicitly for
CoAP offload reply enable request, which will cause
failure when the ids are not 0.
To fix it, fill the vdev id and pattern id accordingly.
Change-Id: I74b4b26d08e48e9d08d041293cff6f4ab92272e1
CRs-Fixed: 3310734
|
|
Fill param 'timeout' for WMI_WOW_COAP_ADD_KEEPALIVE_PATTERN_CMDID,
which represents the period to send CoAP keepalive message.
Change-Id: I86b87470277eee00de9e33a07e635dd1a5412f3d
CRs-Fixed: 3275955
|
|
The osif request allocated in wlan_cfg80211_coap_cache_get_cbk()
is not freed for cases other than completed case, which will
result in memory leak in those cases.
To fix it, free osif request for all the cases.
Change-Id: I17998d0fb39e75b8b5f52a26d351056222c95536
CRs-Fixed: 3275889
|
|
Enable trace log for CoAP(Constrained Application Protocol)
component.
Change-Id: I4b49bdc48547617e943353c9b76d88870fe2ff05
CRs-Fixed: 3257886
|
|
Add support for CoAP(Constrained Application Protocol) realted
vendor command QCA_NL80211_VENDOR_SUBCMD_COAP_OFFLOAD.
Change-Id: I830379ca0dda765add5e1ddd949fd3e51dcb80e6
CRs-Fixed: 3254544
|
|
Add os if layer for CoAP(Constrained Application Protocol)
component. It provides interfaces to parse netlink messages
for vendor command QCA_NL80211_VENDOR_SUBCMD_COAP_OFFLOAD
and take action accordingly, including enable/disable offload
reply/periodic transmitting for CoAP messages, and fetching
CoAP messages those cached during offload processing.
Change-Id: Ibbf9baf3802d305f9989e024ce764a6071b1fc6b
CRs-Fixed: 3254541
|
|
Add component for the Constrained Application Protocol.
This component provides interfaces to enable/disable
offload reply/periodic transmitting for CoAP messages,
and also the interface for fetching CoAP messages those
been cached during offload processing.
Change-Id: I91397f598c2702a63e250d50641352d13117777e
CRs-Fixed: 3254535
|
|
Implement wmi interfaces for sending CoAP(Constrained
Application Protocol) commands and extracting CoAP events.
Change-Id: I74244ad071c70512223dcbe03a99204734751644
CRs-Fixed: 3254530
|
|
Release 2.0.9.17O
Change-Id: I1aa123b02a0c389bcdd24ab25d94fd0362f7fece
CRs-Fixed: 774533
|
|
Change the logging level of prints that occur during roaming
happens.
Change-Id: I54706d93a30441e48a0e3cb03d7373d2e5b50fee
CRs-Fixed: 3133890
|
|
Release 2.0.9.17N
Change-Id: I9be9ee5fef002e0e6a4483f5a413d286aa3ce90a
CRs-Fixed: 774533
|
|
Allow suspend only when bss color change countdown is zero, otherwise
wlan driver will enter into suspend while bss color change is in
progress and it will lead to delay in bss color change.
Change-Id: Ia14b49e34191ec56cb853d68e16be61c585cf25a
CRs-Fixed: 3444353
|
|
Release 2.0.9.17M
Change-Id: Id5884fed6f25998bf12ce8962d5486093882bd1f
CRs-Fixed: 774533
|
|
Currently, phy_mode AUTO is not considered for candidate scoring
config if the platform doesn't support 11BE currently. This is
added as part of 11BE changes and the mode is considered fine
before the change I7f35379b94dcb64dec0da463b95967125dc7fd14.
This doesn't seem to be intentional.
So, consider phy_mode AUTO also for legacy platforms.
Change-Id: Id2eaa8208f5bf5a875e1e72a2117a24b070e6e6b
CRs-Fixed: 3242455
|