jewel: adjust refx100 to 6650.

Change-Id: Ic3102cfb87150028da4e4752ec42eb284b908710
display: evita: increase refx100 to reduce refresh line appearance
* Increased refx100 to 6650

Change-Id: Iff86d6b2cfc6e55ff8cdf7d3f0bdcef3afd0c5a9
ville: increase refx100 to reduce screen tearing

Change-Id: Ib1137ec381ee52e741f909225d6da3a515e5f378
Revert "msm_fb: display: fix compiler warning for uint64_t format"

This reverts commit 415bb26fce8608f03685c3de0fa43f56a7760bf8.

Revert "msm: msm_bus: Add support for 64-bit bandwidth requests"

This reverts commit 13aba771e3672dd8909a84395f19ae719ebfc468.
Revert "jewel: adjust refx100 to 6650."

This reverts commit d6cf6ae45a03d34d1c5b5d98d791e4b84001378f.
Linux 3.0.67

Change-Id: I6aeb84dec2e97ea8a0cb1254e89db2b8b5df5d5f
jewel: display: remove pinfo.clk_rate.

minimizes screen tearing.

Change-Id: I9be1b6073f3eaa5411e09e8d4be499734c62233d
Merge "Linux 3.0.67" into cm-10.1
Revert "ville: increase refx100 to reduce screen tearing"

Apparently this is causing complaints, will remove until better solution
is found.
This reverts commit cd56ea6856b70441c7baa525090c33a1d3b4ec64.
msm_fb: display: release mdp clk in mdp4_overlay_writeback_on()

mdp clk is not released in mdp4_overlay_writeback_on()

CRs-fixed: 433986

Change-Id: Ida121e03b0f08ca312c60fb8d945fe2011df853f
Signed-off-by: Mayank Goyal <goyalm@codeaurora.org>
msm_fb: display: add wfd suspend/resume to early suspend

wfd on/off was handled by fb_on/fb_close which are called from video
or userspace side. However, this is not the case for this branch. mdp
driver has to register wfd for suspend to make sure proper panel
on/off happen.

Change-Id: If1836598e5ae95e4b2b72e40dc85784a0d20c843
Signed-off-by: Huaibin Yang <huaibiny@codeaurora.org>
msm_fb: writeback panel commit should not happen when buffer is NULL

The change handles the NULL buffer case for writeback panel.
It avoids the H/W commit when buffer is NULL and also adds it to
free queue.

CRs-Fixed: 448340
Change-Id: I60f5d343d6de0f96353b081aa113f347c73c61af
Signed-off-by: Kalyan Thota <kalyant@codeaurora.org>
msm: display: reset vsync state when display is turned on

In the case that vsync ctrl is unbalanced, vsync IRQ is cleared
in suspend,  vsync cannot be enabled after resume.
Clear the status when display is turned on

CRs-fixed: 449155
Change-Id: I5ecf23053b60d1fbd91f042758d67d39c83ab444
Signed-off-by: Ken Zhang <kenz@codeaurora.org>
msm: vidc: Add support for NV21 color format encoding

This change adds NV21 color format encoding support.

CRs-fixed: 448511
Change-Id: If26f1241a006e2d325668b8e189f6ff76df8e125
Signed-off-by: Deepak Verma <dverma@codeaurora.org>
video: msm: use linear brightness ramp

Change-Id: Iad17353b2d00e232b70d31b74c0f7b8ff0603e2e
msm_fb: Update backlight level on resume after first pan display

Use shared workqueue to delay the update of backlight after
a first valid frame is displayed on the panel. This avoids any
transients being displayed during resume.

CRs-fixed: 361002
Change-Id: Ia2c2e39aae62e9ddfebe3a26fb4dbc969d0892c2
Signed-off-by: Padmanabhan Komanduru <pkomandu@codeaurora.org>
(cherry picked from commit 8c13d2615b1c608f941137166efb649353cc0bdb)
netfilter: xt_qtaguid: fix error exit that would keep a spinlock.

qtudev_open() could return with a uid_tag_data_tree_lock held
when an kzalloc(..., GFP_ATOMIC) would fail.
Very unlikely to get triggered AND survive the mayhem of running out of mem.

Signed-off-by: JP Abgrall <jpa@google.com>
netfilter: qtaguid: Don't BUG_ON if create_if_tag_stat fails

If create_if_tag_stat fails to allocate memory (GFP_ATOMIC) the
following will happen:

qtaguid: iface_stat: tag stat alloc failed
...
kernel BUG at xt_qtaguid.c:1482!

Signed-off-by: Pontus Fuchs <pontus.fuchs@gmail.com>
netfilter: xt_qtaguid: Allow tracking loopback

In the past it would always ignore interfaces with loopback addresses.
Now we just treat them like any other.
This also helps with writing tests that check for the presence
of the qtaguid module.

Signed-off-by: JP Abgrall <jpa@google.com>
msm_fb: dtv: Serve device off in a separate thread

DTV device should not be powered down until the audio engine has
shutdown. This change moves dtv audio off sequence to a separate
thread so that framebuffer close system call does not get blocked.

CRs-Fixed: 412575
Change-Id: I246a9e58f1367e653913773696510f375abf3d3a
Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>