msm: kgsl: show timestamp in sync dump

Improve the debug information printed for kgsl points and timelines.

kgsl_sync_pt_value_str:
  - show timestamp passed to kgsl_add_fence_event()
kgsl_sync_timeline_value_str:
  - show most recent timestamp passed to kgsl_sync_timeline_signal()
  - show last retired timestamp according to kgsl_sync_get_timestamp()

Change-Id: I93fe408b06de054b11e05784cd7175ed3fcb76ad
Git-commit: 595e213985f63d6aa484c966a4f4a710b31ca209
Git-repo: https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git
Signed-off-by: Fred Fettinger <fred.fettinger@motorola.com>
Signed-off-by: Harsh Vardhan Dwivedi <hdwivedi@codeaurora.org>
base: sync: increase size of sync_timeline name

This makes it possible for drivers to use a longer, more descriptive
name for a sync_timeline, which improves the readability of the
sync dump in debugfs.

Change-Id: Ifb83aebf6fd820ebb26aca2ff230ac1116e65ce9
Git-commit: cb63e61b80ec905f01cbe1c21081aa0d1fef082d
Git-repo: https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git
Signed-off-by: Fred Fettinger <fred.fettinger@motorola.com>
Signed-off-by: Harsh Vardhan Dwivedi <hdwivedi@codeaurora.org>
msm: kgsl: generate descriptive names for kgsl-timeline

Generate names for kgsl-timelines using the following format:
<device>-<thread name>(<tid>)-<proc name>(<pid>)-<context id>

This makes it possible to identify the context of a timeline in the
sync dump, which makes it much easier to identify which context has
a GPU timeout.

Change-Id: I0ce0614a53a93fd81094d92c9bef7053e6d416d2
Git-commit: e3348f389f715cb2143a708ec6796d3f65e03821
Git-repo: https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git
Signed-off-by: Fred Fettinger <fred.fettinger@motorola.com>
Signed-off-by: Harsh Vardhan Dwivedi <hdwivedi@codeaurora.org>
mdss: mdss_fb: remove mmio access through mmap

Disable access to mm io and add
appropriate range checks to ensure valid accesses
through framebuffer mmap. This prevents illegal
access into memory.

Change-Id: Ic6e47ec726d330d48ce9a7a708418492a553543b
CRs-Fixed: 474706
Signed-off-by: Manoj Rao <manojraj@codeaurora.org>
mobicore: t-base-200 Remove dynamic assignement

Use cdevs instead of relying on the dynamic assignment of a
misc minor device. Make version information from buildTag.h
available in release version of kernel module.

Change-Id: I8f98828556067ae7c62bfef6767e7667569b79a3
Signed-off-by: Oana Medvesan <medvesan.oana@gmail.com>
[hnamgund@codeaurora.org: Drop changes to mobicore_driver/main.c
to align with other branches]
Signed-off-by: Hariprasad Dhalinarasimha <hnamgund@codeaurora.org>
Acked-by: Tony Hamilton <tonyh@qti.qualcomm.com>
arm/dt: msm8974-liquid: Correct edge sensitivity issues

Top and bottom of touchscreen sensitivity is lacking, so
improve the range that touch responds in.

CRs-fixed: 467971
Change-Id: Ieebfb6bd6d8bd3d4713bb5bf23793fa6c4a71479
Signed-off-by: Amy Maloche <amaloche@codeaurora.org>
cpufreq: ondemand: Fix store_powersave_bias() race with hotplug

store_powersave_bias() assumes that CPUs will not be taken offline or
brought online while executing its for_each_online_cpu() loops. Fix
this race by blocking hotplug while executing in these loop.

CRs-Fixed: 494407
Change-Id: I0d5520444ec21a8d9b12fb73c06ac8442449fa85
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
usb: usb_bam: hsic consumer request not necessarily resume the hsic core

When hsic consumer is requested, the hsic bam driver vote for resume
the hsic core. In this case hsic core resume is activated and we have
a flag (hsic_host_dev_resumed_from_cons_request) to know if resume
happened in this scenario or not.

However, if hsic core was already resumed when the hsic consumer request
arrived, for example since other driver voted for resume before that, then
no resume will happen and therefore the flag will remain set to true.
Therefore, on the next resume, we will consider the resume as resume
after consumer request and we will prevent from doing necessary operations
such as calling to ipa_resume. Therefore when the consumer is released
we will set this flag back to false so we will know that the next resume
that will happen is since of other resume scenario.

Change-Id: Ied21c2d6c7b299a79bf43a093440cab8123a0407
Signed-off-by: Ido Shayevitz <idos@codeaurora.org>
msm8974-Camera: Fix the reset stable issue on DB 8074

From the user space were passed pointer  that not allocated and
it cause to memory corruption and reset issue.

Change-Id: Iaa2521757f11d37836566d7982d010c33bf98f87
Signed-off-by: Tanya Finkel <tfinkel@codeaurora.org>
ASoc: msm: Fix for pcm_read getting stuck in alsa core

Advance hardware pointer by period size even if the packet
coming from qdsp6 is of less size. QDSP6 sometimes
(for rapid device switches) gives packets worth less
than period size and this results in hw_ptr appl_ptr mismatch.

CRs-Fixed: 486276
CRs-Fixed: 488449
Change-Id: I893f9a52e4cd507fd72e4a7aba3c5fa76527d1bf
Signed-off-by: Sidipotu Ashok <sashok@codeaurora.org>
msm: camera_v2: handle error notify private ioctl.

Handle the error notify private ioctl by adding the appropriate
error event to the HAL queue.

Change-Id: Icbfa0ee78ba5209b347fb500b58e718c0cae4999
Signed-off-by: Ankit Premrajka <ankitp@codeaurora.org>
msm: ipc: Load default subsystem under appropriate scenario

Only client and service ports are used for communication with the remote
subsystems. Load the default subsystem only when the clients lookup their
services or when the local services get registered with the IPC Router.

Change-Id: I18729bb849c656a826de4f67f9ffe159dd3cf5f6
Signed-off-by: Karthikeyan Ramasubramanian <kramasub@codeaurora.org>
msm: mdss: cleanup dsi interrupt handling logic

Use reference counting for DSI interrupt enable/disable, masking out
DSI_MDP_DONE interrupt.

Change-Id: I83a8136b8bfeeebd2cbb6a8f711b4dd818f49bd2
Signed-off-by: Xiaoming Zhou <zhoux@codeaurora.org>
msm: mdss: cleanup MDP interrupt handling logic

Simplify MDP vsync and dma done interrupt handling logic.

Change-Id: Ieac19ce4c6efc42c6005b2c0cab97be8a67ad263
Signed-off-by: Xiaoming Zhou <zhoux@codeaurora.org>
msm: pil-q6v5-mss: Skip Q6 shutdown sequence when restarting MSS

Execution of the Q6 shutdown sequence is not necessary since the
whole subsystem is reset as part of pil_mss_shutdown() anyway.
Furthermore, access to the Q6 registers required by
pil_q6v5_shutdown() may be blocked after MSS boot (depending on
security configurations) making such access fail.

Fix this by removing the unnecessary call to pil_q6v5_shutdown(),
and the associated clock and power-rail setup required to make
that call.

Change-Id: Ica82474b6157f7b12abb877e7443f6335480855c
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
defconfig: automatic update

Change-Id: I4eb690b98959ec4f0b3a40d7cc5c844fd9938609
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
defconfig: CONFIG_MEDIA_TUNER_CUSTOMISE=y

Disable unused tuners.

Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
gcc 4.7 cleanups

Fix warnings due to -Wmaybe-uninitialized in GCC 4.7.

Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
Turn off -Wmaybe-uninitialized when building with -Os

gcc-4.7 and higher add a lot of false positive warnings about
potential uses of uninitialized warnings, but only when optimizing
for size (-Os). This is the default when building allyesconfig,
which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.

In order to avoid getting a lot of patches that initialize such
variables and accidentally hide real errors along the way, let's
just turn off this warning on the respective gcc versions
when building with size optimizations. The -Wmaybe-uninitialized
option was introduced in the same gcc version (4.7) that is now
causing the false positives, so there is no effect on older compilers.

A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,
we might now see /fewer/ warnings about possibly uninitialized
warnings than with -O2, but that is still much better than seeing
warnings known to be bogus.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Git-commit: e74fc973b6e531fef1fce8b101ffff05ecfb774c
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
gcc-wrapper: trim whitelist for gcc 4.7

With recent code and defconfig changes, the number warnings needing to
be ignored has gone done.  Update the wrapper accordingly.

Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>