bcmdhd: set the correct bw in the firmware

bcmdhd: set the correct bw in the firmware

Due to incorrect bw setting, fw will always start
the MCC for P2P GO if the APs present in the
environment in that channel are all only 20 MHz.

This issue happens only for higher 5GHz passive
channels (149, 153, 157, 161) which are passive
by default.

Bug 200025947

Change-Id: Idf79e9ce60362584a999d8f244f98c10cc170611
Signed-off-by: bibhayr <bibhayr@nvidia.com>
Reviewed-on: http://git-master/r/482473
GVS: Gerrit_Virtual_Submit
Reviewed-by: Rakesh Goyal <rgoyal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>