ARM: fault: assume no context when IRQs are disabled during data abort.

Bail out early if IRQs are disabled in do_page_fault or else
  [14415.157266] BUG: sleeping function called from invalid context at arch/arm/mm/fault.c:301

Russell King's idea from
  http://comments.gmane.org/gmane.linux.ports.arm.omap/59256

Signed-off-by: JP Abgrall <jpa@google.com>
msm: pm2: Restore interrupt subsystem from sleep.

Change-Id: Id5128e47e1e78688d0b608b64454555f26a65043
Signed-off-by: Sridhar Gujje <sgujje@codeaurora.org>
Signed-off-by: Baji Patthan <bpatth@codeaurora.org>
msm: pm2: Log SMSM state
Apache: build A2220
ariesve: Fix bluetooth power on and deep sleep
msm: kgsl: Calculate busy interval considering GPU freq as float

GPU freq could be non-integral value and treating it as an integer
to calculate GPU busy insterval leads to higher busy interval
and more often we see negative idle stats. This change caculates
busy interval by treating gpu freq to the correct precision.

Change-Id: Ic54130803d7a0436b4ba31b09915eb7165d16590
CRs-fixed: 454972
Signed-off-by: Vinay Roy <vroy@codeaurora.org>
Revert "msm: kgsl: Update pagetable on context destruction for A20x"

This reverts commit f0d1c9b79e05972816b92bd43b29e98f764826ea.

Reverting this change since it corrupts Bin Base Offset between
two draws of a Binning pass, resulting in GPU hang.

(cherry picked from commit 3ec5d2db139d0941ec8360f6cc399223b18469e5)

Change-Id: Ie1853075533e15e6c8020a00e57b1695df81c9ba
Signed-off-by: Rajesh Kemisetti <rajeshk@codeaurora.org>
msm_fb: Build video enhancer for ariesve only
msm_fb: Kang logo routine from d2
lowmemorykiller: make default lowmemorykiller debug message useful

lowmemorykiller debug messages are inscrutable and mostly useful
for debugging the lowmemorykiller, not explaining why a process
was killed.  Make the messages more useful by prefixing them
with "lowmemorykiller: " and explaining in more readable terms
what was killed, who it was killed for, and why it was killed.

The messages now look like:
[   76.997631] lowmemorykiller: Killing 'droid.gallery3d' (2172), adj 1000,
[   76.997635]    to free 27436kB on behalf of 'kswapd0' (29) because
[   76.997638]    cache 122624kB is below limit 122880kB for oom_score_adj 1000
[   76.997641]    Free memory is -53356kB above reserved

A negative number for free memory above reserved means some of the
reserved memory has been used and is being regenerated by kswapd,
which is likely what called the shrinkers.

Change-Id: I1fe983381e73e124b90aa5d91cb66e55eaca390f
Signed-off-by: Colin Cross <ccross@android.com>
msm_fb : display : Block RGB downscale in MDP 4.0 and 4.1

Downscale is not allowed on RGB pipes in MDP 4.0 and 4.1. Hence,
fail the OVERLAY_SET ioctl for such configurations.

Signed-off-by: Pradeep Jilagam <pjilagam@codeaurora.org>
(cherry picked from commit 3545573720822ce97ec37586f10fdf74a6d4f090)

Change-Id: I8445c18ac21cb7322eb9eb4c802623df5da07eb7
Signed-off-by: Gopal Goberu <ggober@codeaurora.org>
video: msm: Clear previous histogram data on next startup

Clear the pointer to the userspace histogram struct when histogram is
started. Previously, when the histogram was stopped while a histogram read
was in progress, the pointer was not cleared, causing the next histogram
read to think that someone was already using the histogram.

CRs-Fixed: 361640
Change-Id: If09017149e98b35c49603372c554aa4c97f2de82
Signed-off-by: Carl Vanderlip <carlv@codeaurora.org>
(cherry picked from commit 19e4b71f617e307cacf0be077e08bec5c37df290)
Update defconfigs
yda165 driver: Remove pop-up noise at the end of power off sequence

Taken from the yda165 driver of SGSII.
net: wireless: bcmdhd: Move sources into main folder

For easier patching and comparing of changes.
net: wireless: bcmdhd: Update to Samsung's JB version

Should fix problem with wifi tethering.

Only issue I see is this error in dmesg when activating wifi:

<3>[   11.886657] mmc0: Data CRC error
<3>[   11.886749] msmsdcc_data_err: opcode 0x00000035
<3>[   11.886901] msmsdcc_data_err: blksz 4, blocks 1
<3>[   11.887542] mmc0: Data CRC error
<3>[   11.887603] msmsdcc_data_err: opcode 0x00000035
<3>[   11.887756] msmsdcc_data_err: blksz 4, blocks 1

Although I haven't noticed anything bad happening yet.
bluetooth: Fix issue with file transfer

Why is it always the simple things that causes the biggest problems?
bln: Changes to fix the suspend problems caused by BLN

Changes on bln module:
 - New centralized methods for wakelock management (init, destroy, acquire and release)
 - Some changes to call the new methods

Changes on cypress-touchkey:
 - Removed the wakelock declared on this module for bln
 - Replaced the previous code for bln wakelock management with the related calls of
   the new methods created on bln module side
 - During early resume, release the possible wakelock previously acquired for bln
   and not released yet
Update defconfigs
net: wireless: bcmdhd: Fix WEP connection