msm: kgsl: Use msecs_to_jiffies for ADRENO_IDLE_TIMEOUT

This change is about to cherrypick of missing code part
from Change-Id: Ic0dedbad33630706d909931bf616bd69399f7ff1

Change-Id: I6c9766be0651e99251e1cb280f92e06e47875b4f
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
Revert "ramdisk: kill brightness at boot"

This reverts commit 45e645cf2a3423e4b1d07be5fd57d9258982e1ac.
Linux 3.4.68
N9005 MJ6 camera changes
N9005 MJ6 es325 firmware
N9005 MJ6 mdss changes
ramdisk: set permission for rear_camfw_load
camera: workaround for non-mj6 firmware fc - revert later
N9005 MJ6 rest of changes (minus TIMA stuff)
9005 MJ6 missed rtmutex related updates
ramdisk: lkconfig: add option to display current settings
msm: mdss: reduce minimum mdp ib bandwidth request

The minimum mdp ib for usecases such as portrait video is high,
causing unnecessary power increase, so it is reduced to a optimal
value for the purpose of both power saving and reducing chances of
underruns.

CRs-fixed: 538989
Change-Id: Ibabf16ef3081ef85d181cc8a70e4cfbe029156c1
Signed-off-by: Huaibin Yang <huaibiny@codeaurora.org>

Conflicts:

	drivers/video/msm/mdss/mdss_mdp_ctl.c
msm: actuator: fix to prevent untrusted pointer to lead DoS

fix to prevent untrusted userspace pointer in actuator kernel
driver to lead DoS

Change-Id: I1b64270deb494530d268539e7b420be5ec79b658
Signed-off-by: Vasko Kalanoski <vaskok@codeaurora.org>
msm: actuator: fix to prevent kernel heap buffer overflow

fix to prevent kernel heap buffer overflow allows user
controlled data to be written to the heap via the
msm_camera actuator IOCTLs

Change-Id: I4458831e28e0081fb2f5ae55506be866100e1b4f
Signed-off-by: Vasko Kalanoski <vaskok@codeaurora.org>
ramdisk: lkconfig: add screen off maxfreq support
msm: cpufreq: Only apply driver limits for scaling_min/max_freq writes

When new values are written to scaling_min/max_freq sysfs files, the
current code applies all the limits imposed by various ADJUST and
INCOMPATIBLE notifiers handlers before storing them.

When the ADJUST and/or INCOMPATIBLE notifiers change their limits
frequently, this behavior makes it almost impossible for a
user/userspace process to store the scaling_min/max_freq limits
that go beyond the instantaneous limits imposed by the notifiers.
Since these sysfs nodes are typically meant to set limits that need
to be enforced for the foreseeable future, this is not a very user
friendly behavior.

So, change the behavior to only apply limits that are enforced by
the cpufreq driver. Typically, these are just the absolute limits
of the HW and don't change very often.

Change-Id: I1ccfaa2d1ee4ea595f882485d359dbdb407a0176
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
camera: fix macro for EUR
leanKernel v1.2
camera: add KTT to macro for mj6
camera: fix camera for custom TMO ROMs which don't play well with mj6

* works fine on stock