msm: msm_fb: wait for VSYNC instead of DMA_P for commit completion.

In the current implementation, we are waiting for DMA_P interrupt
in commit call to signal completion. This can cause 2 commits happening
in the same vsync period due to which IOMMU page faults can happen when
vsync comes while second commit is programming resgisters. To avoid this,
wait for DMA_P is replaced by wait for VSYNC.

Change-Id: I68d4d4b4e7a574f86faecd5b4812e1f5852f4209
Signed-off-by: Vishnuvardhan Prodduturi <vproddut@codeaurora.org>
Signed-off-by: Sridhar Gujje <sgujje@codeaurora.org>
Merge "msm: msm_fb: wait for VSYNC instead of DMA_P for commit completion."
msm: msm_fb: Replace wait for DMA_P with VSYNC in Pan_display Path.

This is a follow up change on gerrit 442946. Wait for DMA_P has to be
replaced with VSYNC even in Pan Display Path.

Change-Id: I8d600022cfa63f54d5b72ea5f64fc55315079b3a
Signed-off-by: Vishnuvardhan Prodduturi <vproddut@codeaurora.org>
Merge "msm: msm_fb: Replace wait for DMA_P with VSYNC in Pan_display Path."
Merge tag 'AU_LINUX_ANDROID_JB_2.6_RB1.04.03.00.144.005' into jb_2.6_rb1

AU_LINUX_ANDROID_JB_2.6_RB1.04.03.00.144.005 based on quic/aosp/jb_2.6_rb1

# gpg: Signature made Wed 18 Sep 2013 02:43:02 AM MDT using DSA key ID 80A901F1
# gpg: Good signature from "lnxbuild (lnxbuild account) <lnxbuild@qualcomm.com>"
Merge "Merge tag 'AU_LINUX_ANDROID_JB_2.6_RB1.04.03.00.144.005' into jb_2.6_rb1"
Merge AU_LINUX_ANDROID_JB_2.6_RB1.04.03.00.144.008 on remote branch

Change-Id: Idf7a9aceb07d4d96357b3d4c3ba71e57d8baaa98
Merge "Merge AU_LINUX_ANDROID_JB_2.6_RB1.04.03.00.144.008 on remote branch"
msm: msm_fb: Map RGB layers to the max possible size.

IOMMU Page Faults are observed on RGB layers during stability
because MDP is trying to fetch out of mapped area of the buffer.
This patch avoids the issue by overmapping the RGB layers to the
max possible RGB buffer size.

Change-Id: Idc7ac9acad70e351acac5dba2ae43b8731e84d35
Signed-off-by: Vishnuvardhan Prodduturi <vproddut@codeaurora.org>
EHCI: HSIC: improve port resume handling

This patch does the following to ensure that port is resumed
properly and SOF are sent with in 3 msec after the port resume
completion.

1. Use relaxed variants of readl and writel functions to access
registers in the resume critical path to avoid any delays introduced
by barriers.

2. Use ktime based checks to see if controller is started with in 3
msec after port resume is completed. These checks will catch the
cases where there is some delay between port resume and GPT timers
programming.

3. There is no good in polling for PORT_RESUME bit to be cleared.
Controller clears it after ~21 msec. Give 22 msec delay after port
resume and start the controller. Also add a ktime basec check to see
if controller is started with in 3 msec after port resume is completed.
If this timing is not met, perform the tight loop sequence again at
most 3 times.

CRs-Fixed: 553845
Change-Id: I29eab2fa0f684d91e1ac52d14faaffde1113b79b
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Merge "msm: msm_fb: Map RGB layers to the max possible size."
Merge "EHCI: HSIC: improve port resume handling"
msm_fb:hdmi:Fix for audio not routed to HDMI issue

Due to recent security fixes, in HDMI VSD block
parsing is failing which is causing driver to
consider the HDTV connected as DVI and hence no
audio is routed to TV. So removing the incorrect
length check in hdmi_edid_extract_ieee_reg_id function

Change-Id: Iea4a0969710ee1f4411b14973e7d1678f81183cc
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
Merge "msm_fb:hdmi:Fix for audio not routed to HDMI issue"
msm: msm_fb: Fix Regressions because of overmap changes.

Previous MDP overmap change is causing issues with HDMI because of
assumptions about overmap. This patch fixes all such issues.

Change-Id: Ifd2f8a0596d9df08538464bdcdd5946cf84db4d9
Signed-off-by: Vishnuvardhan Prodduturi <vproddut@codeaurora.org>
Merge "msm: msm_fb: Fix Regressions because of overmap changes."
Merge ad080c726a881f5d46fba09edb5e05f250923f73 on remote branch

Change-Id: I4590a3d9b741342c416cc181eab1226f07915a3b
Merge "Merge ad080c726a881f5d46fba09edb5e05f250923f73 on remote branch"
USB: OTG: Fix Full speed USB Headset issue

Some Full speed USB headsets requires higher cross over voltage. The
cross over voltage is directly proportional to the phy 3.3 rail voltage.
The current code uses [3.07 - 3.3] range for this regulator and it is
supplied with 3.075V.  To get 3.3V supply, use [3.3 - 3.3] range in
the host mode.

CRs-Fixed: 563496
Change-Id: I3d1705fd346212ecf42c4943995e43964ad14dc5
Signed-off-by: ChandanaKishori Chiluveru <cchilu@codeaurora.org>
msm: board: Set the max voltage level for LDO3 to 3.3V

Currently min/max voltage level for LD03 was set to 3.075V.
But some Full speed USB headsets requires higher cross over voltage.
The cross over voltage is directly proportional to the phy 3.3V
rail voltage. So modify the max voltage level of LD03 to 3.3V.

CRs-Fixed: 563496
Change-Id: I535d8d6382e708aa3bf17ed8dae832d00c52d88b
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>