소스 검색

qcacld-3.0: In FTM mode, don't update config param, max peer limit

Presently, driver configuration from FTM mode to any other mode
is failing due to start module is failing, because configuration
parameter(max peer limit) is set to zero during FTM mode
initialization.

In FTM mode, during start modules, don't update configuration
parameter, max peer limit.

Change-Id: Ie5adea45b2dac099e797a1e25536cc959f3d5525
CRs-Fixed: 1073593
Hanumanth Reddy Pothula 8 년 전
부모
커밋
47d2926b35
1개의 변경된 파일7개의 추가작업 그리고 1개의 파일을 삭제
  1. 7 1
      core/cds/src/cds_api.c

+ 7 - 1
core/cds/src/cds_api.c

@@ -323,7 +323,13 @@ QDF_STATUS cds_open(void)
 	 * and keeps correct limit in cds_cfg.max_station. So, make sure
 	 * config entry pHddCtx->config->maxNumberOfPeers has adjusted value
 	 */
-	pHddCtx->config->maxNumberOfPeers = cds_cfg->max_station;
+	/* In FTM mode cds_cfg->max_stations will be zero. On updating same
+	 * into hdd context config entry, leads to pe_open() to fail, if
+	 * con_mode change happens from FTM mode to any other mode.
+	 */
+	if (DRIVER_TYPE_PRODUCTION == cds_cfg->driver_type)
+		pHddCtx->config->maxNumberOfPeers = cds_cfg->max_station;
+
 	HTCHandle = cds_get_context(QDF_MODULE_ID_HTC);
 	if (!HTCHandle) {
 		QDF_TRACE(QDF_MODULE_ID_QDF, QDF_TRACE_LEVEL_FATAL,