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."
msm: kgsl: Add the buffer user address to the debugfs memory list

For each buffer in the debugfs memory list print the address it is
mapped to in the user process.  This is useful for matching up the
user side allocations with what the kernel thinks it has.

Change-Id: Ic0dedbadd07a8f704c0bf73b183aaeeddbbdd129
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
msm: kgsl: use %pK to restrict printing GPU / memory addresses

Use %pK in the output for the per-process memory dump to keep from
printing the GPU and user memory addresses for the GPU memory
objects own by the process.  This allows us to make the 'mem' file
world readable without exposing any really dangerous information.

Change-Id: Ic0dedbad21654110905d1b3744f562966584d8ed
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Sunil Khatri <sunilkh@codeaurora.org>
Merge remote-tracking branch 'origin/caf/kk_2.7_rb1.10' into omni
9.2.A.0.295

Conflicts:
	arch/arm/kernel/process.c
	arch/arm/mach-msm/Kconfig
	arch/arm/mm/mmu.c
	drivers/media/video/msm/vfe/msm_vfe32.c
	drivers/video/msm/msm_fb_panel.h
	drivers/video/msm/vidc/1080p/ddl/vcd_ddl_vidc.c
	mm/Kconfig
	net/netfilter/x_tables.c
Merge remote-tracking branch 'origin/caf/kk_2.7_rb1.26' into omni

Conflicts:
	arch/arm/mach-msm/Kconfig
	drivers/media/video/msm/vfe/msm_vfe32.c
staging: prima: update to 3.2.6.136 (aee0452684)
sony: add blue defconfig
prima: wlan: Revision 3.2.7.42
driver: led: as3676: expose simple light sensor value

Change-Id: I1db590f093e00d3a8cdc46c49f58e555ee083289
Merge remote-tracking branch 'caf/caf/kk_2.7_rb1.30' into omni
lc898300: implement sysfs interface for vibrator intensity

/sys/devices/i2c-12/12-0049/intensity

Change-Id: Ic85e234df06d779cc2f1729dea41c978c53b3fda
Blue: don't block FOCUS key in deep sleep

Fixes Peek functionality when you are unable to wake
the device with camera button until you depress it.

Change-Id: I1d2d7ff57bbf0316155bbc8c910a91afc3583323
Revert "lc898300: implement sysfs interface for vibrator intensity"

This reverts commit 79378637603021bbd6c08cf0acd3b3d9b8acdae9.
Perf: Check perf activity on correct CPU

The CPU hotplug notifier is not always preempt safe.
So relying on smp_processor_id() is not correct.

Use the cpu id from the notifier as the target
CPU to check for perf activity before hotplug or power
collapse.

Change-Id: I1a96b236904a2c8ae2f82bbceab4ca8a195395d1
Signed-off-by: Ashwin Chaugule <ashwinc@codeaurora.org>
Perf: Add L1 counters to tracepoints

Create a new tracepoint to get L1 PMU counter
information at every context switch. Counters
are captured only when the tracepoint is enabled
via perf or ftrace.

Change-Id: If05527b29e04c700170cfdf9f88d300b2f558ffa
Signed-off-by: Ashwin Chaugule <ashwinc@codeaurora.org>
Perf: Fix counts across power collapse

After entry and exit from power collapse, the perf pm_notifier was
calling perf_pmu_disable/enable functions from perf core. Perf core
maintains a counter that it uses to match disable and enable calls but
since pm_notifier is invoked asynchronously, the counter was getting a
non-zero value which prevented the pmu from being enabled. As a result of
this, we were seeing zero counts for some cores across power collapse.

Make the architecture specific calls directly from pm_notifier.

Change-Id: I744e190906a20e70e1e4798235215c385018b121
Signed-off-by: Sheetal Sahasrabudhe <sheetals@codeaurora.org>