added find5_defconfig for android-4.3
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>
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>
diag: NRT read wakelocks held for very long time

During on-device logging with '-b' option,
NRT read wakelocks i.e. diag_nrt_modem_read
and diag_nrt_wcnss_read were held for more than
a day's time. This patch releases the wakelocks
even if SMD channel will be closed.

Change-Id: I7d211aaeaeb8d59369a191c5eef54c02a1b4a61d
CRs-Fixed: 513309
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
panel: change frame_rate from 60 to 55

This still need more testing but reducing the frame_rate
from 60 to 55 reduces the amount of vsync delay messages
from qdhwcomposer a lot

Change-Id: I21d2b60bdba0723c62535dff0299ef6beee885f4
touchscreen: disable S2W and DT2W by default

It can be enabled using /sys/android_touch
and in the future if we have something like
device settings

Change-Id: I35db4061cb724d3bffeb065e1b89af327a2fedb5
Merge "touchscreen: disable S2W and DT2W by default" into android-4.3
Merge "panel: change frame_rate from 60 to 55" into android-4.3
defconfig: Remove old cruft

We're not part of CM any more, and this defconfig is obsolete

Change-Id: I186fafd339227a77452aa4367c2f97b27ccc98c2
remove also obsolete AOKP defconfig

Change-Id: I31397484998d73b087c3dc96b999a2e61eb59b7d
ARM: 7698/1: perf: fix group validation when using enable_on_exec

Events may be created with attr->disabled == 1 and attr->enable_on_exec
== 1, which confuses the group validation code because events with the
PERF_EVENT_STATE_OFF are not considered candidates for scheduling, which
may lead to failure at group scheduling time.

This patch fixes the validation check for ARM, so that events in the
OFF state are still considered when enable_on_exec is true.

Change-Id: I8d0b35dc032c48b2422eb46ea615bd1a50c888c1
Cc: stable@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Jiri Olsa <jolsa@redhat.com>
Reported-by: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
ARM: 7809/1: perf: fix event validation for software group leaders

It is possible to construct an event group with a software event as a
group leader and then subsequently add a hardware event to the group.
This results in the event group being validated by adding all members
of the group to a fake PMU and attempting to allocate each event on
their respective PMU.

Unfortunately, for software events wthout a corresponding arm_pmu, this
results in a kernel crash attempting to dereference the ->get_event_idx
function pointer.

This patch fixes the problem by checking explicitly for software events
and ignoring those in event validation (since they can always be
scheduled). We will probably want to revisit this for 3.12, since the
validation checks don't appear to work correctly when dealing with
multiple hardware PMUs anyway.

Change-Id: I1d8768fafc978b8c4c1de15075bd094b33a57460
Cc: <stable@vger.kernel.org>
Reported-by: Vince Weaver <vincent.weaver@maine.edu>
Tested-by: Vince Weaver <vincent.weaver@maine.edu>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
ARM: 7765/1: perf: Record the user-mode PC in the call chain.

With this change, we no longer lose the innermost entry in the user-mode
part of the call chain.  See also the x86 port, which includes the ip.

It's possible to partially work around this problem by post-processing
the data to use the PERF_SAMPLE_IP value, but this works only if the CPU
wasn't in the kernel when the sample was taken.

Change-Id: I16b4ca522b7f062c92dba02286cf962c6e345999
Cc: <stable@vger.kernel.org>
Signed-off-by: Jed Davis <jld@mozilla.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
touchscreen: check for correct s2w enablement

S2W handling should only be done if the correct
flag is enabled

Change-Id: I3ecd0b24ca039c0127be15f24ca300e9f9ba62cc
Merge "touchscreen: check for correct s2w enablement" into android-4.3
find5: kernel: power: sync USB insert handling with CAF

Enable enable_tcxo_warmup_delay by default
To fix the bug that sometimes charger plugin
is not recognized

Also cleanup oppo specific code a little bit

Change-Id: I609b0be8ed3045d2a636ec46e5f0e3edadf081a7
touchscreen: fix initial touch not recognized on S2W wakeup

When wakeup using S2W the intitial touch is not
recognized e.g. when trying to unlock

Change-Id: Ib1e6427b87ab678a2fcd13ba219b21c553dad30b
msm_fb: display: Add support to YCBYCR MDP format

Add support of MDP_YCBYCR_H2V1 interleaved YUV format to MDP
for a-family targets.

Change-Id: I5afb84a95693d1ced114152364782a10c4d56bc2
Signed-off-by: Mayank Chopra <makchopra@codeaurora.org>
find5: CM config

Change-Id: Ia7887d0ad416f56728705f67f9a06e8b70f76869
Merge branch 'cm-10.2' of https://github.com/CyanogenMod/android_kernel_oppo_find5 into martincz