ASoC: msm: qdsp6v2: add support to enable TTY during VoLTE call

Enable of TTY during VoLTE call is not supported. Add support to
enable TTY during VoLTE call.

CRs-Fixed: 697463
Change-Id: Ie104eddd7b404f278a0d4def770a3f6fffef901c
Signed-off-by: Venkata Narendra Kumar Gutta <vgutta@codeaurora.org>
msm: kgsl: Increase the timeout value for fault detection

Increment the timeout value for detecting faults from 50ms to
200ms. The fault detection mechanism is a backup to hardware
fault detection. 50ms is small since it has been observed that
this mechanism triggers false positives with 50ms.

CRs-Fixed: 672164
Change-Id: I8f382051e06bdc47f152309a2868092e1980604e
Signed-off-by: Shubhraprakash Das <sadas@codeaurora.org>
Signed-off-by: Tarun Karra <tkarra@codeaurora.org>
Signed-off-by: Sunil Khatri <sunilkh@codeaurora.org>
msm: kgsl: Force the ME off before reading the microcode

On A3XX reading the microcode while the CP is running is dangerous
beyond words.  By setting the offset address for the read, we are
essentially changing the instruction pointer for the ME while it
is running causing opcode errors, gpu faults and/or system errors.

We do not want to stop the CP at the beginning of the snapshot
process beacuse doing so changes the RBBM status and the state of
the CP registers which may damage the debug effort.  But by the
time we get to the microcode read we no longer care about the state
of the registers so we can freely halt the ME just before starting
the read.

Conflicts:
	drivers/gpu/msm/adreno_a3xx_snapshot.c

Change-Id: Ic0dedbad85d7ec26915f054dd597e226e8101a29
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Sunil Khatri <sunilkh@codeaurora.org>
Merge "msm: kgsl: Increase the timeout value for fault detection"
Merge "msm: kgsl: Force the ME off before reading the microcode"
Merge "ASoC: msm: qdsp6v2: add support to enable TTY during VoLTE call"
Revert "(CR) [ARM] msm: Offset sched_clock with suspend time"

This reverts commit b9433def698aa71df3e809d6e521cc3680a0ad92.

The only purpose of the original change was to increase kernel
log timestamp after system suspend to reveal the time spent in
suspend mode. But the implementation causes problems.
read_sched_clock() is used by CFS to compute task running time
but not used to compute total CPU time thus the total CPU times
in /proc/[pid]/stat and /proc/stat mismatch.

This affects end uses' experience as well. Because suspend time
is added into the running time of kernel thread that triggers
system suspend, end users see abnormally high Android OS battery
utilization in Settings->Battery.

Change-Id: Ibb3d60ac0e7ed61178b434b01ffb06826dae9c0c
Signed-off-by: Peng Liu <a22543@motorola.com>
Reviewed-on: http://gerrit.mot.com/645066
SLTApproved: Slta Waiver <sltawvr@motorola.com>
Submit-Approved: Jira Key <jirakey@motorola.com>
Tested-by: Jira Key <jirakey@motorola.com>
Reviewed-by: Christopher Fries <cfries@motorola.com>
Prima: Reset to kitkat-mr1-rel-razrm and  merge kitkat-mr3-rel-ghost

This fixes the odd disconnects on Razr HD

Change-Id: I62ef2ec3cb8f86d2f499ce545ad32a24136dbe1d
Merge remote-tracking branch 'caf/LNX.LA.2.7.4' into kk4.4