Increase qwerty keys debounce time from 15 to 20ms

- seems to help the correct detection of presses on slightly
  worn out keys

Change-Id: I9533b70b22f506db44bc0552bd47c560bb1f9e42
wlan: LFR - invalid channel in INI causes double free.

The crash is happening because of a double free in csrScanCopyRequest.

In csrScanCopyRequest, palCopyMemory is called which copies contents of
tCsrScanRequest from pSrcReq to pDstReq. This will include the address
of pointers as well (i.e. pIEField, ChannelList and SSIDList). Due to a
recent commit in CL663677, we ignore the scan request if the channel is
invalid to prevent spawning scans on ALL valid channels. When the scan
request is ignored, csrScanFreeRequest gets called for both pDstReq
(first) as well as pSrcReq. When we decide to ignore the scan request
due to invalid channel, SSIDList in pDstReq will point to the address
that was copied from pSrcReq. Due to this, we end up double freeing the
memory at address pSrcReq->SSIDs.SSIDList.

This is being addressed by re-initializing all the pointer variables in
pDstReq after the palCopyMemory.

When the scan request is ignored due to an invalid channel, there
will not be a scan callback because the request command was never
sent to PE. Due to this the roaming engine gets stuck and remains in
eCSR_NEIGHBOR_ROAM_STATE_CFG_CHAN_LIST_SCAN. This is being fixed by
calling csrNeighborRoamScanRequestCallback if the scan request
fails to unblock the roaming state machine.

Change-Id: I68f79e1a7cb640140968012fc646cf1bd0268a6b
CR-Fixed: 434971
(cherry picked from commit c7b1d3e9ad417c37b4923899780181e0a6196e97)
wlan: TX_Thread Spinng problem fix

If MGMT Q has pending frame, even AC Mask is DATA frames only,
WLANTL_GetFrames will retunr none 0 value.
This will make DXE indicate that DXE is out from low resource condition
and keep triggering to get frame from data Q.

Change-Id: I31e2d8f4fd1dd7e11d2ca705ee229db224ca2f05
CR-Fixed: 435323
(cherry picked from commit 7e48ca7b1f8054c33b0a8825367b7418e4ddc23e)
wlan: Kernel crash from freeing bss list

Data abort while traversing bss link list as next pointer is
NULL.Therfore we should reset ''pMac->ft.ftPEContext.pFTPreAuthReq' to
NULL, causing the FT session object not to
be checked for freeing in 'limFTCleanup'

Change-Id: I70eba6f1619f2d51bddf248f9ecf7a741586bf30
CR-Fixed: 436485
(cherry picked from commit 2d335f3ff97a4da06e1c3d6d4365ca5c2e2d49ec)
tracing/syscalls: Fix perf syscall tracing when syscall_nr == -1

syscall_get_nr can return -1 in the case that the task is not executing
a system call.

This patch fixes perf_syscall_{enter,exit} to check that the syscall
number is valid before using it as an index into a bitmap.

Link: http://lkml.kernel.org/r/1345137254-7377-1-git-send-email-will.deacon@arm.com

Change-Id: Ib91ef74205792e974ca3dafac2816a61ad3a8c57
Cc: Jason Baron <jbaron@redhat.com>
Cc: Wade Farnsworth <wade_farnsworth@mentor.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
tracing/syscalls: Ignore numbers outside NR_syscalls' range

ARM has some private syscalls (for example, set_tls(2)) which lie
outside the range of NR_syscalls.  If any of these are called while
syscall tracing is being performed, out-of-bounds array access will
occur in the ftrace and perf sys_{enter,exit} handlers.

 # trace-cmd record -e raw_syscalls:* true && trace-cmd report
 ...
 true-653   [000]   384.675777: sys_enter:            NR 192 (0, 1000, 3, 4000022, ffffffff, 0)
 true-653   [000]   384.675812: sys_exit:             NR 192 = 1995915264
 true-653   [000]   384.675971: sys_enter:            NR 983045 (76f74480, 76f74000, 76f74b28, 76f74480, 76f76f74, 1)
 true-653   [000]   384.675988: sys_exit:             NR 983045 = 0
 ...

 # trace-cmd record -e syscalls:* true
 [   17.289329] Unable to handle kernel paging request at virtual address aaaaaace
 [   17.289590] pgd = 9e71c000
 [   17.289696] [aaaaaace] *pgd=00000000
 [   17.289985] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
 [   17.290169] Modules linked in:
 [   17.290391] CPU: 0 PID: 704 Comm: true Not tainted 3.18.0-rc2+ #21
 [   17.290585] task: 9f4dab00 ti: 9e710000 task.ti: 9e710000
 [   17.290747] PC is at ftrace_syscall_enter+0x48/0x1f8
 [   17.290866] LR is at syscall_trace_enter+0x124/0x184

Fix this by ignoring out-of-NR_syscalls-bounds syscall numbers.

Commit cd0980fc8add "tracing: Check invalid syscall nr while tracing syscalls"
added the check for less than zero, but it should have also checked
for greater than NR_syscalls.

Link: http://lkml.kernel.org/p/1414620418-29472-1-git-send-email-rabin@rab.in

Change-Id: I372ae33eb3c6bfd50ad7ac235b442a7056482f17
Fixes: cd0980fc8add "tracing: Check invalid syscall nr while tracing syscalls"
Cc: stable@vger.kernel.org # 2.6.33+
Signed-off-by: Rabin Vincent <rabin@rab.in>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common into cm-11.0_mod