summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorPragaspathi Thilagaraj <tpragasp@codeaurora.org>2018-06-04 16:25:33 +0530
committernshrivas <nshrivas@codeaurora.org>2018-06-12 02:02:53 -0700
commitce1b3e9e38b1fc6fa68049658c5b4ddf060ce75d (patch)
treecccc8df0931aeda9a83d450d1a6e7b4e7980701f /tools/perf/scripts/python
parent12728a3d9778641359d0936738de8efb0135aac3 (diff)
qcacld-3.0: Populate correct dot11_mode during CSA
When CSA is recieved from the firmware, dot11_mode is copied from received message . In response to the CSA message, the host invokes wma_vdev_start with isRestart flag set to restart the vdev with the new updated channel, and channel params. The dot11_mode value is copied from the CSA which will not be a problem unless the switching channel is on the same band or on different band as long as its HT/VHT 2.4GHZ to HT/VHT 5GHZ bands or vice-versa. When the channel switch occurs from a 11a to 11g band or vice-versa, wrong dot11_mode is populated without being updated for the new band. As the phy_mode is calculated from the dot11_mode value, phy_mode check fails in wma_vdev_start in this case. So the host doesnt send vdev_restart. Populate the dot11_mode correctly and pass it to lower layers upon updation. This will ensure correct phy_mode is calculated and vdev_restart is sent. Change-Id: Iaf8788d51b47190c04744b8981dd594236fbae57 CRs-Fixed: 2248980
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions