Boeffla ramfs: Hardening for all reboot activities by disabling dynamic fsync before reboot
s3cfb_ops: Attempt to fix LPM (off charging mode) graphics issue

From 11b86abe52925fbd9a8232dad7ce9ef05c3da182 Mon Sep 17 00:00:00 2001
From: Ketut Putu Kumajaya <ketut.kumajaya@gmail.com>
Date: Fri, 26 Sep 2014 11:57:55 +0700
Subject: [PATCH 2/4] s3cfb_ops: Attempt to fix LPM (off charging mode)
 graphics issue
samsung_battery: Attemp to fix LPM (off charging mode) with KitKat bootloader

From 4bedd4878cc17535c4db0bc48f4752d7f7e37e89 Mon Sep 17 00:00:00 2001
From: Ketut Putu Kumajaya <ketut.kumajaya@gmail.com>
Date: Fri, 26 Sep 2014 21:02:14 +0700
Subject: [PATCH 3/4] samsung_battery: Attemp to fix LPM (off charging mode)
 with KitKat bootloader

Change-Id: Icbc7f7b0d6e52485eadc2d801224e01eaffe29e1
otg: when removing ED from readyQ also set flag

The driver keeps track of the "is this endpoint in the list" state with
the redundant flag ".is_in_transfer_ready_q". It should therefore always
be sync with the .next and .prev of the readyq_list list:

        struct ed *ed;
        otg_list_head *qlist = (typeof qlist) ed->readyq_list;

        (qlist->prev == LIST_POISON2 || qlist->next == LIST_POISON1)
          == !ed->ed_status.is_in_transfer_ready_q;

Should both properties be not in sync, bad things can happen. All code
paths in driver rely on the flag and then call list operations. If the
flag suggests the entry is in the list, otg_list_pop () will be called.
When the entry however is not in the list, the members .prev and .next
are poisoned and an attempt to do list operations on them results into a
NULL (or rather an invalid address which is the poison) pointer
dereference. Such a fault would then trigger a kernel panic and the
device rebooting.
In real life this happens when disconnecting USB devices frequently,
especially when in operation (transfering data while detaching).

While in most positions in the code, it was taken care to keep both
properties, the flag and the list entry state, consistent, one position
was left out, which is addressed with this patch.
Extensive testing shows that the device would crash easily and in a
reproducable manner without the patch but does not show any faults with
the patch applied.

Change-Id: I80f3a8e7d866c699ddcd1c61b04d956e39d2197c
CM ramfs: Update to version of CM nightly 26.09.2014
su: update su to version 2.35
Boeffla ramfs: Remove busybox installation in boeffla-config and change fstrim

- remove kernel fstrim and use the one provided by CM busybox instead
- Busybox installation is not required as all CM roms so far come with full busybox
cpufreq: Update to zzmoove 1.0-beta2

Credits to ZaneZam

Changelog:

- avoid kernel crash (usually a oops in smp.c) by checking if a core is online before putting work on it: this problem appeared on opo qualcomm
  platform with proprietary mpdecision hotplugging service. assumption is that there is a delay between initiating hotplugging events from 'userland'
  and gathering core state info in 'kernel land' so under some rare circumestances the governor doesn't 'know about' a changed core state and tries to
  put work on a meanwhile offline core or that hotplug event happend during putting work on a core in the governor.
cpufreq: Update to zzmoove 1.0-beta4

Credits to ZaneZam

Changelog:

- use again the conservative governor usual canceling of dbs work syncron instead of asyncron when exiting the governor as this change was
  only needed in combination with older hotplug implementations. as also done in opo version removed again all previously merged kernel crash
  fix attempts and precautions as they were not really needed
- bump version to beta4 to bring opo/i9300 versions in sync again
Release tag: 2.4-beta8