Fast Charge: Fix up and add some crazy ass amount of code to disable PC USB MTP recognition and make sure 1000 mA is applied
mm: Modify page_alloc to analyze zone for NULL condition before passing it on to fucntions like zone_dirty_ok.  This is trying to prevent: 'Unable to handle kernel NULL pointer dereference at virtual address 00000001' condition from PC is at get_page_from_freelist+0xe8/0x630 - LR is at zone_dirty_ok+0x18/0xe0
Revert "me4 upddate"

This reverts commit bf516005f303c1ebe632c9bef9a26782f1796981.
Revert "jf: update to MDL source drop"

This reverts commit e37d73c7a016f218dfbd8c54d5f930bb48f3a225.
msm_otg: remove initialization wake_lock
jf: JC: allow non samsung app to update firmware

insure stability
Change-Id: I5eb80edbcdfe48a86668461d781decd5bedef027
Merge in ME4 source jizzer style
sched: Set MC (multi-core) sched domain's busy_factor attribute to 1

busy_factor attribute of a scheduler domain causes busy CPUs (CPUs
that are not idle) to load balance less frequently in that domain,
which could impact performance by increasing scheduling latency for
tasks.

As an example, consider MC scheduler domain's attribute values of
max_interval = 4ms and busy_factor = 64. Further consider
max_load_balance_interval = 100 (HZ/10). In this case, a non-idle CPU
could put off load balance check in MC domain by 100ms. This
effectively means that a CPU running a single task in its queue could
fail to notice increased load on another CPU (that is in same MC
domain) for upto 100ms, before picking up load from the overloaded
CPU. Needless to say, this leads to increased scheduling latency for
tasks, affecting performance adversely.

By setting MC domain's busy_factor value to 1, we limit maximum
interval that busy CPU can put off load balance checks to 4ms
(effectively 10ms, given HZ value of 100).

Change-Id: Id45869d06f5556ea8eec602b65c2ffd2143fe060
Signed-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>
Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
driver:video: Remove some dmesg log spam
Disable Screen Off Mhz Call:  GOES LIVE
dmesg log spam: remove more cypress keypress spam and haptic feedback spam
[PATCH] Squash of two EHCI: HSIC commits from caf

EHCI: HSIC: disable pm runtime device before remove hcd
  Merge order of commits 21a480e and e50d914 introduced runtime pm
  disable depth counter imbalance fixed by e50d914 again. Fix the
  bug by disabling runtime pm before removing HCD.

Change-Id: I249a4f63db3a975652e6ce15545584e41bae284b
Signed-off-by: Ido Shayevitz <idos@codeaurora.org>

EHCI: HSIC: fix driver removal function for msm_hsic_host
  Upon driver removal function we need to disable the device pm runtime
  in order to, first, undo all the logic done in probe and second, to keep
  balanced disable depth counter in case of platform driver unbind.

  However the removal function can be called also in consequences of
  platform_device_del(), in this case the platform device was already
  disabled and removed so if we call pm_runtime_disable() again we
  decrease the disable_depth for the second time causing for unbalanced
  counter.

  Therefore we use an if statement to check if the device was already
  removed or not.
Fast Charge:  Fixups for those stubborn ass jizzer ROMs that refused to let OTG work
cpufreq: Fix missing screen_off_enable check
Samsung Update 2 source from I9505
GPU OC: Changed 544MHz to 545MHz to conform better to the PLL table, added 627MHz frequency
GPU: available freqs: Add code for new freq step 627Mhz

Change-Id: Ia1866af32e7541a5d4187f0508ae38c64c0ba1eb
GPU: available freqs: adjust for 544 to 545mhz change

Change-Id: I4c0ada48361e295009484de8c801db707ed2c5d7
Add deleted ppmu.h back in
cpufreq: ktoonservativeq: Add option to control wether or not to boost extra cores to cpu0's set speed, enabled by default