wlan: Fix for SAP/P2P GO to come up on configured channel

As part of moving from kernel 3.4 to 3.7, set_channel cfg80211 API was
removed. This API was called before start_bss and used by our driver to
configure the operating channel. With kernel upgrade, this API was not
called and we were passing initialized value "0" as the channel number
which host would internally convert to some valid 2.4GHz channel
(because of auto selection of AP channel when channel no passed is 0).
Thus SAP and P2P GO would come up on random 2.4GHz channels inspite of
user configuring them in hostapd.conf/p2p_supplicant.conf.
The fix is to:
Use the operating frequency info passed in the "cfg80211_ap_settings"
struct in wlan_hdd_cfg80211_start_ap to get the correct current
operating channel. I printed the freq and this structure gives the
correct freq while doing start_ap. Use this to call set_channel API

CRs-fixed: 448661
Change-Id: I137d57aa7986381f6b92eb5b15287f9b933bfaae
(cherry picked from commit 3a32cc5a5b8808c8a21e9f3e44fda9785aafb400)
1 file changed
tree: 49b6d6230abdb40ad4e0a50ac217368b9790c9b7
  1. CORE/
  2. firmware_bin/
  3. riva/
  4. Android.mk
  5. Kbuild
  6. Kconfig