Abhishek Singh b1954c63bc qcacld-3.0: Force P2PGO to SCC only if other beacon entity is active ... In case SAP+P2PGO+STA interface are present, with SAP in down state and STA in conencted state and P2PGO is started, it uses API policy_mgr_concurrent_beaconing_sessions_running checks if multiple beaconing interface are present to force the P2PGO to SCC or DBS channel and as SAP and P2PGO interface are present it returns true. Now the API to get concurrent channel get the channel of STA which is active and thus P2PGO moves to STA channel. Thus use the api to get channel for concurrent beaconing interface instead of any interface to take care of beaconing interface concurrency scenareos. With this concurrent channel will be non 0 only if any other beaconing entity is present and in up state and thus P2PGO will move to SCC or DBS only in case any other beaconing interface is actually up and beaconing on a channel. Change-Id: Ic4bacc8cc45386499c11e09e79d095e926318400 CRs-Fixed: 2395530		2019-02-15 18:28:24 -08:00
..
inc	qcacld-3.0: Remove eSAP_ASSOC_STA_CALLBACK_EVENT handling	2019-02-11 23:56:52 -08:00
src	qcacld-3.0: Force P2PGO to SCC only if other beacon entity is active	2019-02-15 18:28:24 -08:00