net: wireless: bcmdhd: Allow vendor OUI customization for SoftAP

Change-Id: I103fead7e418830c69e5a586ccae3f1fdad90839
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
net: wireless: bcmdhd: Fix country update on dhd_stop()

b/17657029

Change-Id: I55bc07501d71a823f153a61462f5c3ca363b2a3e
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
net: wireless: bcmdhd: Fix parameter to set wifi tx back off for SAR

b/17675462

Change-Id: Ic724df586dd6c7535903c1d24d14911cf9e5f9a2
Signed-off-by: lungtsai_lin <lungtsai_lin@htc.com>
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
Staging: android: binder: Ratelimit binder debug messages

Ratelimit the binder debug messages, since they can get spammy and
flood the entire kernel log.

In some cases, enabling serial console with a spammy binder error can
cause a watchdog panic (and we don't have reports of this happening
with serial console disabled).

Bug: 17613664
Signed-off-by: Chris Fries <cfries@motorola.com>
net: wireless: bcmdhd add RECOVERY mechanism of PCIe LinkDown

17294478 [WiFi] - Need Sub-System Restart for WiFi
17728059 APR (N6): Kernel panics at dhd_prot_process_msgtype
17721881 [WiFi] - Watchdog reset after Event HANG sent up
Signed-off-by: Ecco park <eccopark@broadcom.com>

Change-Id: I5a0157cf519e6188467922aa5d0ab57e602c3b7e

Conflicts:
	drivers/net/wireless/bcmdhd/dhd_pcie_linux.c
net: wireless: bcmdhd: add recovery logic for resumed on timeout.

17755061 Wi-Fi stuck in Off position on Shamu
17734434 Kernel Panic when Scanning wifi networks

Due to unknown reason of linkdown of PCIe, our DHD goes to weird stage.
Normally we should get linkdown irq of PCIe, but for some case, we don't
get any linkdown irq of PCIe.
In this case, we cannot recover PCIe registers when we turn off/on again.
To recover PCIe register properly, we should set bus->islinkdown=true for
resumed on timeout.

Change-Id: Ie135b05edb47a274cecaaa50c8e418118b7bbf89
Signed-off-by: Ecco park <eccopark@broadcom.com>
net: wireless: bcmdhd: Fixed failure to enter PS mode while roaming in suspend

b/17433072 Device on wifi(suspend) gets to a bad state and keeps drawing 400mW

Change-Id: I265312ec72f80bbcce9242eed3aa9f25bb68f4ca
Signed-off-by: Ritter Yeh <ryeh@broadcom.com>
net: wireless: bcmdhd reduced the MAX_CNTL_TX_TIMEOUT to 1

Currently the recovery mechanism is not triggered because Wi-Fi
Framework will turn on Wi-Fi again as soon as we get resumed on timeout for the
first time.
Currently the recovery mechanism is triggered if we get resumend on  timeout two times
continually.
So, in order to trigger recovery mechanism, we need to the count from 2 to 1.

bug : 17755061 Wi-Fi stuck in Off position

Change-Id: I86a950243c742e561c3ac8a8722bd9a760331410
Signed-off-by: Ecco park <eccopark@broadcom.com>
net: wireless: bcmdhd change the turn off/on sequence of WLAN

1) diable pcie irq during turning off WLAN
2) clear resources during turning off WLAN
3) bug : 17755061
4) This sequence comes from our main repo
Signed-off-by: Ecco park <eccopark@broadcom.com>

Change-Id: I41bb48064f5c2f68045c258dcb3ec37d6f87e42e
net: wireless: bcmdhd: Fix compilation for non PCIE_FULL_DONGLE case

Change-Id: I6698e97be12b7b6ed2145420901558f756546b99
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
net: wireless: bcmdhd: Fix race condition during flow ring creation and deletion

b/17957931 EAPOL Tx frames are dropped by driver or firmware

Change-Id: Ib9c93867b09539bd22ad3c29b4543505104b0645
Signed-off-by: Ritter Yeh <ryeh@broadcom.com>
net: wirelss: bcmdhd fix the corner case of PCIe linkdown

1) [Issue 17755061] Wi-Fi stuck in Off position with new log, we missed the one
case for NON-IOCTL.  Sometimes we have issue for deleting flow ring.
2) For failure of WLAN-on, we don't set g_wifi_on to TRUE.  So, we don't do
anything to clear resource even through framework will call wl_android_wifi_off

Change-Id: I8078988eee3520780b1151422db88bf631a39084
Signed-off-by: Ecco park <eccopark@broadcom.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
net: wireless: bcmdhd: Enable dongle_isolation for PCIe/built-in type driver

b/17755061 Wi-Fi stuck in Off position

Signed-off-by: Ritter Yeh <ryeh@broadcom.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Change-Id: I70dc1385266fe26ef3a57116e653efab03fc33cf
net: wireless: bcmdhd enable STATIC MEMORY ALLOCATION

b/18187102 APR: kernel BUG at mm/vmalloc.c
Signed-off-by: Ecco park <eccopark@broadcom.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Change-Id: I9b53792487a0078ecd3240ad92e96dd702a1724b
net: wirelss: bcmdhd fixed pcie suspend/resume issue

Sometimes, system doesn't recover the config registers during resume
due to wakelock.  So, we need to save and restore the config registers in DHD

b/18220535 [WiFi] - Watchdog reset after PCIE link down and Event Hang

Signed-off-by: Ecco park <eccopark@broadcom.com>
Change-Id: Ib796b4833119a27bd79e3a667e40ee1e4d4878df
net: wireless: bcmdhd: Allow preallocation for WLFC_INFO

Bug: 18303260

Change-Id: I1602fa0706270071abe36797039af74670f1c734
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

Conflicts:
	drivers/net/wireless/bcmdhd/Makefile
net: wirelss: bcmdhd  fixed disconnect issue for connecting status

Sometimes Framework issues connect and disconnect rapidly and continuously
with different APs.  In this case, the timing gap between connect and
disconnect is less than 20ms.  For this scenario, FW doesn't do anything
when DHD executes dissasoc while state of FW is associating status.  In
order to cancel current assoc procedure correctly, we need to call
scan_abort function, not DISASSOC.  FW will clean up ongoing assoc
procedure if FW is associating status.

b/18470879 Device stop responding after conducting rapid fire testing
           for making connection

Change-Id: Ib440da06eb10313c478c004d1d73ed1b4e29a201
Signed-off-by: Ecco park <eccopark@broadcom.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>

Conflicts:
	drivers/net/wireless/bcmdhd/wl_cfg80211.c
net: wirelss: bcmdhd fix roaming bug

1) Bug : 18541286 wifi stuck on connected to an AP when N6 was miles away
we should update BSSID in wl_bss_roaming_done, not wl_notify_status for roaming case
It causes out-of-sync between FW and DHD
Signed-off-by: Ecco park <eccopark@broadcom.com>

Change-Id: I75e706d63aa962c8c2640797e2af6811990c989d
net: wireless: bcmdhd abort ongoing-scan for disconnection

sometimes we cannot get WLC_E_DEAUTH due to ongoing-scan
We need to abort ongoing-scan for disconnection

Bug: 18634452
Signed-off-by: Ecco park <eccopark@broadcom.com>
Change-Id: I2c416738418ce4915dcfbaa57bb3d701269eecc8
net: wireless: bcmdhd  reduce kernel logging

Bug : 18226601
Signed-off-by: Ecco park <eccopark@broadcom.com>

Change-Id: Iec8172bf803b76517136d1a8903027b5ed162d31