diff options
| author | Hanumanth Reddy Pothula <c_hpothu@codeaurora.org> | 2016-10-03 16:08:04 +0530 |
|---|---|---|
| committer | qcabuildsw <qcabuildsw@localhost> | 2016-10-06 11:24:30 -0700 |
| commit | 47d2926b35b27a2d13f3c287be6049e2da09dac2 (patch) | |
| tree | d6bd7c3e48328165ee7d32f02e04a47391aad788 | |
| parent | 489e79b0995b32fbd2371f591ad46a4ed42e4c6b (diff) | |
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
| -rw-r--r-- | core/cds/src/cds_api.c | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/core/cds/src/cds_api.c b/core/cds/src/cds_api.c index bcc146f1e1d4..0e6974a782ee 100644 --- a/core/cds/src/cds_api.c +++ b/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, |