Currently the driver returns incorrect status to the user space
when mDNS offload feature is disabled. So, add a debug log and
return correct status when mDNS offload is disabled.
Change-Id: I4ae58467eb8ff464380d5a8b69b45545534de37e
CRs-Fixed: 3239903
Currently, separate reg_domain and country_code are defined for
qcacmn and qcld.
Define reg_domain and country_code in reg_db.h and include
reg_db.h to avoid multiple definitions.
Change-Id: Ic5b2f1e9612fd7cbb4a8944daa17ada87ee7a7a7
CRs-Fixed: 3212421
Add a sanity check to verify if the driver is loaded
before invoking soft driver unload.
Change-Id: Id6f735c1661104ac14410399a54953f962792644
CRs-Fixed: 3239752
Wrong value of tx status sent to supplicant for MGMT frame
via diag logging.
Convert the tx status value to enum diag_tx_status specific value.
Change-Id: Iba6d8011280d41a874509d2a1b4fed9a16ee585c
CRs-Fixed: 3236363
Currently, interface combinations are advertised as part of wiphy
registration but some of them lead to 3-port/4-port. Refine the
concurrencies to advertise only supported combinations as below,
1. Remove SAP+SAP_MAX_OBSS_STA combination
2. Remove the "reserved STA iface which was added to support
P2P device". No need to indicate any additional interface count
for P2P_DEVICE mode as driver doesn't advertise dedicated
P2P_DEVICE support.
3. Add NAN+STA and NAN+SAP combinations also.
Change-Id: I7ed594c2b719c243cbe38794b877f77240024620
CRs-Fixed: 3226284
Provide read permission to group and other for tsf sysfs entry.
This allows applications to read tsf value.
Change-Id: I59ab2228334cc3975830edd675e0b09be182bf9d
CRs-Fixed: 3209335
Currently dump in progress feature is not in use so
disable this feature with CONFIG_WLAN_DUMP_IN_PROGRESS
feature flag.
Change-Id: I1c93e3a3749ac5bb9fed38e30ed0b6069f02f0ed
CRs-Fixed: 3214636
Connectivity logs are sent through vendor command which
required to maintain a separate logging infrastructure.
Add Diag event logging in to send connectivity logs via
netlink in order to maintain a single logging infrastructure.
Change-Id: Ic3b868724ab7da25b7b3f28197e2f4b0f89897d3
CRs-Fixed: 3226658
Update peer HT/VHT width for wideband such as:
1. Wideband is restricted to 80 MHz if APs BW
is less than 80 MHz, if selfdot11mode is 11ac.
2. STA follows AP BW in all other HT/VHT cases
Change-Id: I9346a692582c322c10e36fe6679e38ec8acbb440
CRs-Fixed: 3234946
PASN authentication M1 should be initiated by I-STA.
Driver requests for the initiation of PASN auth from
wpa supplicant only for I-STA mode. For R-STA mode, M1
will be received from peer I-STA.
So update wifi pos module after peer create only for I-STA mode
and skip that for R-STA mode.
Change-Id: I09ac53bcd50cb012ad8cd5d351b91e6fb017c77d
CRs-Fixed: 3170770
With introduction of TDLS on 6 GHz, some of the channels
that peer can support will be same for 6 GHz band other
bands. So, extract frequency by using peer supported
operating class and supported channel list which can
be used for further processing.
If channel numbers are used then the duplicate channel
numbers are removed which may lead to skipping 6 GHz
supported channels.
Change-Id: Ic6838d05c3dab5a0cc17483890b83805e076684c
CRs-Fixed: 3233999
After WLAN_TWT_CONV_SUPPORTED enabled, TWT variables are moved from
COMP_MLME to COMP_TWT, APIs are updated too, hdd_update_tgt_twt_cap
just intersects enable_twt and twt_requestor of COMP_TWT instead of
COMP_MLME, legacy variable mlme_cfg->he_caps.dot11_he_cap.twt_request
isn't controlled by ini enable_twt now.
Change-Id: I71bb09704fd96591f37019ebbb77733cff04af25
CRs-Fixed: 3229121
Add regulatory notify event when wifi ON by GUI.
In new framework test, When turning on Wi-Fi, it is
expecting driver to indicate NL80211_CMD_[WIPHY]_ REG_CHANGE
event with country code to wificond.
Change-Id: Icb0bdec097db14905de6234573d05fffbe0e4500
CRs-Fixed: 3186188
User space timestamping tool expecting Tx packet send time
in Monotonic time and host is sending Tx packet send time in
Qtime.
Currently Qtime is always higher than System monotonic time,
This change is to calculate the drift between Qtime and
System monotonic time during tsf init and adjust calculated
drift to each Tx packet send Qtime to make Qtime and
System monotonic time are in sync.
Change-Id: Ibd686d5fdea6ebcbc0fe5b37c4211cb8dd073d76
CRs-Fixed: 3230594
hdd_config_wds_repeater_mode should be called if the vdev is roaming.
Otherwise, WDS does not work after roaming.
Also deliver peer authorize to SON if the vdev is roaming.
Change-Id: If6c660a5fd3e2c493d8d100cdbfa562404018aba
CRs-Fixed: 3193596
Currently in driver, for non-DBS hw mode, null peer is released in the
function ndi_remove_and_update_primary_connection. This causes null
pointer deferencing.
To fix this, add null peer check before releasing the peer.
CRs-Fixed: 3184390
Change-Id: Ia895c8487082e0fac6e7df63d3694fa3e152b355
Userspace may send RSNXE also in connect request irrespective
of the connecting AP capabilities to allow the driver to chose
best candidate based on score. But the chosen candidate may
not support the RSNXE feature and may not advertise RSNXE
in beacon/probe response. Station is not supposed to include
the RSNX IE in assoc request in such cases as legacy APs
may misbehave due to the new IE. It's observed that few
legacy APs which don't support the RSNXE reject the
connection at EAPOL stage. So, strip the IE if AP doesn't
support/advertise the RSNXE to avoid sending the RSNXE to
legacy APs.
Change-Id: Ia7dee29792718a6514da44b13b36b46586ef25ab
CRs-Fixed: 3228057
BTM and EAPOL events are sent through the vendor event to
the supplicant
Modify the BTM and EAPOL event log flow through the diag
event to the supplicant in order to maintain single
logging infrastructure
Change-Id: I1e21d1192be059cc48189bc57aacbc314d5297bc
CRs-Fixed: 3219065
Roam Diag logs are sent through the vendor event to the supplicant.
Modify the Roam Scan start and Roam Candidate log flow through
the diag event to the supplicant in order to maintain single
logging infrastructure.
Change-Id: Idd85b46f72a481aa99e243c81952010d2779afaf
CRs-Fixed: 3218639
Currently, host is overwriting 2 GHz capabilities by 5 GHz
which is causing to send same capabilities for both bands.
To solve this:
1. Send HE and EHT capabilities by band.
2. While populating the eht mcs and nss,
for 2 GHz, only populate values for BW upto 80 MHz
for 5 GHz, populate BW upto 320 MHz
3. Send correct eht cap length.
Change-Id: I9bbad81341b49e4a98b3fcccadd162e82d93d11e
CRs-Fixed: 3225630
