cfg80211: Don't build as module

Change-Id: Ie0761880fe1595ac2fb8cf3cc70ef2854f98f188
Revert "USB: android: Avoid re-enabling the same configuration"

Commit d9b1897713 doesn't allow re-enumeration of USB default composition
on bus reset. if adb close and adb open has been called within 1 second
of duration. with adb usb command, it restarts the adb into USB mode after
closing the adb device and re-opening the same within 1 second. To the
user it looks as if command is stuck. Terminating adb usb based command
prompt, killing adb server and doing adb shell again gets the adb
functionality. Here user doesn't see any USB re-enumeration with it. Hence
revert commit d9b1897713 which doesn't block the adb usb command and
re-enumeration of USB.

(cherry picked from commit ff3e0492ee60c8594b3f48eed87e086f4b3d5b0b)

Change-Id: I50ab56f94293b2e02b66c548ee703d26284bcc57
CRs-Fixed: 385973
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
USB: android: Don't disable configuration for every adb close

Certain ADB commands like "adb usb" and "adb root" restart the
adb daemon running on the device.  These commands require USB
bus reset, otherwise adb commands on the host side would stuck
for ever.

USB bus reset can be forced from device side by re-enabling the
same composition.  Earlier, configuration is disabled when adb
daemon closes /dev/android_usb device file.  The configuration
is enabled again after adb daemon opens the device file. This
approach solves the "adb usb" problem with the below side effects.

1. When USB cable is disconnected, the Rx request is flushed and
an error code is returned to user space.  The adb daemon is simply
restarted in this case which cause an unnecessary rebinding of
all functions.
2. The above scenario can happen if host reset the bus when device
is in configured state.  If device disable pull-up during, bus
reset, USB CV CH9 test cases are failing.

The commit d9b1897 (USB: android: Avoid re-enabling the same
configuration) fixed the above side effects. But silently ignores the
original "adb usb" problem.

This commit is another attempt to solve all the above mentioned problems
by forcing re-enumeration only when device is in connected state.  That
means, "adb usb" and "adb root" commands force usb bus reset where as
plugging out a cable does not.

(cherry picked from commit 1aa235a6c0a3d67bff24609766baf5a7d5d8e3e4)

Change-Id: I984f1320c6adfa925ed2f3beca5ae1464981e5fc
CRs-Fixed: 407882
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
USB: android: Fix adb device file closing bug

adb device file closing and config disabling can happen in
parallel during composition switch.  If adb device file
is closed prior to config disable, adb function driver request
android to disable configuration.  But this is not undone later
when adb device file is opened.  Due to this bug config remains
disabled after composition switch completion.  Fix this bug.

(cherry picked from commit c4d8e2ca7cfb2118bcc9f14a97568bfe42b76bcc)

Change-Id: Ia2b7024cfcc438f4e17ca1f165be03abcf380230
CRs-Fixed: 414360
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Revert "prima: load proper firmware"

This reverts commit f5d4a980165d7f8495736b2b1d7bd92769b26e8f.
prima: oppo qcom_cfg

Change-Id: I9c4f34e4ce7f83a5fe0099981fcd8328c7cf5375
prima:  Switch to prima_legacy from Sony msm8x60 kernel

Based on our firmware file sizes (28456 bytes instead of 29776),
it appears we have legacy Prima firmware, and need the legacy driver.

Change-Id: I686757e5dad7e15241844eb7799f5ab24e08c090
config: Switch to legacy Prima driver

Change-Id: I812ae0c608ad37a326e095b2b1f7444a17e3f9f0
cpufreq_conservative: Reduce minimum polling interval

Conservative's minimum polling interval is very long - this patch reduces
it so the user can tune it downwards, while still respecting hardware
transition_latency limits.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
cpufreq_conservative: Change default tuning settings

Half the polling rate, but more aggressive up/down thresholds.

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
cpufreq_conservative: Bump default frequency step up to 10 from 5

Based on a better understanding of how the governor operates,
this is a better choice on most Exynos devices.

Change-Id: I8ed87e2b61f621138aa5a20951d8a70037e986a9
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
config: Enable conservative governor

Change-Id: I53b96ab35138c9d82bec31e0782a34d9e29fce5c