Bläddra i källkod

qcacld-3.0: Use secondary_ch to calculate ACS result params

In shielding room, bring up one 2.4G SAP with HT40+ on channel 6,
but hostapd_cli command will report HT40-. Root cause is it uses
sec_ch_offset when calculate ACS result params, it's wrong.

Fix is to use secondary_ch when calculate ACS result params.

Change-Id: I41a5d0e4be0d2e3046d0004c25f11f2905a3b911
CRs-Fixed: 2221588
hqu 7 år sedan
förälder
incheckning
8f11faa1c0
2 ändrade filer med 2 tillägg och 2 borttagningar
  1. 1 2
      core/sap/src/sap_fsm.c
  2. 1 0
      core/sap/src/sap_module.c

+ 1 - 2
core/sap/src/sap_fsm.c

@@ -1763,8 +1763,7 @@ QDF_STATUS sap_signal_hdd_event(struct sap_context *sap_ctx,
 		sap_ctx->acs_cfg->pri_ch = sap_ctx->channel;
 		sap_ctx->acs_cfg->ch_width =
 				sap_ctx->csr_roamProfile.ch_params.ch_width;
-		sap_config_acs_result(hal, sap_ctx,
-			sap_ctx->csr_roamProfile.ch_params.sec_ch_offset);
+		sap_config_acs_result(hal, sap_ctx, sap_ctx->secondary_ch);
 
 		sap_ap_event.sapHddEventCode = eSAP_CHANNEL_CHANGE_EVENT;
 

+ 1 - 0
core/sap/src/sap_module.c

@@ -659,6 +659,7 @@ QDF_STATUS wlansap_start_bss(struct sap_context *sap_ctx,
 	sap_ctx->pUsrContext = pUsrContext;
 	sap_ctx->enableOverLapCh = pConfig->enOverLapCh;
 	sap_ctx->acs_cfg = &pConfig->acs_cfg;
+	sap_ctx->secondary_ch = pConfig->sec_ch;
 	sap_ctx->dfs_cac_offload = pConfig->dfs_cac_offload;
 	sap_ctx->isCacEndNotified = false;
 	sap_ctx->is_chan_change_inprogress = false;