Revert "sensorhub: refixing firmware mislabeling"

This reverts commit b2a4a5275ebd8e00eb366934e9367416fd43ede6.
Linux 3.0.56
ramdisk-aosp: symlinking the needed modules to /system/lib
Signed-off-by: Simone Renzo <simone201@gmail.com>
midas-tsp: Changes due to Note 2 headers
mali: Move ASV application to the init stage (thx to AndreiLux)

Previous to [asv: Change initcall level to an earlier stage] the ASV voltages
would be applied too late for them being read out on ramfs post-init, or to
be changed at boot by scripts without being overridden by the ASV application
shortly after.

Since now we are guaranteed an initialized exynos_result_of_asv, do the ASV
application immediately on init, instead of DVFS runtime, to avoid the issue.
asv: Change initcall level to an earlier stage

We cannot wait for all device_initcall's (And subsequently module_init calls) to
complete before doing the ASV level readout without doing silly workarounds in
those drivers, waiting for an uninitialized exynos_result_of_asv.

Just change the ASV driver initialization from device stage to subsys stage, as
it is not dependant on other drivers or modules.
wm8994: Wolfson Sound Control

aka Boeffla Sound (just renamed to fit my kernel)
all the huge props to @andip71 and gm (and supercurio of course)
wm8994: fixing HDMI audio streaming

this should fix it (as we have the same audio chip as the N10)
ramdisk-aosp: CM10.1 support
include/asm: using symlinking instead of complete folder
exynos-mem: Fix major security hole

This fixes the exynos-mem device security hole. The driver allowed any user
to access all of the device's lowmem through the provided mmap functionality.

We create a small little framework collecting the actual CMA memory blocks
that exist on the device; they are the root cause of the existence of this device
driver. We white-list only the CMA memory spaces as parameters to the mmap
function and deny access to any other memory space requests.

We furthermore just allow access to the "s3c-fimc" memory block as this is
seemingly the only space which upon access denial actually breaks functionality.
exynos-mem: Add fimc1 to mmap whitelist check

The assumption that only devices which use CONFIG_CMA_DMA use
exynos-mem is wrong. Remove that check.

Newer camera libraries as on Note 2 4.1.2 variants also map fimc directly,
but they are not reserved through kernel CMA allocation in the device file
but through Samsung's S5P framework.

There, the block is called "fimc1", so add that to the whitelist check.
s6evr02: Allow max brightness at 255

Change-Id: I464de83d010702ed68759f2bde438c127811bd2e
bluetooth-bcm4334: Make LPM behave like 4330 implementation

We know the 4330 implementation works on galaxys2-common

We don't have an nRST line so remove that.  Main other
difference is we use the UART LPM stuff based on
mach-u1

Change-Id: Ie953b0fa8c47ca1ebf58ef9eaa5a03265b449071
smdk4412: s3cfb_s6e8ax0: Stop fb shitstorm in kmsg

Change-Id: I09ae567b2397275ea021f5fc1b66fc4ac09d9021
smdk4412: s3cfb_s6evr02: Stop fb shitstorm in kmsg
patching the right note2 file
Linux 3.0.57
wolfson_sound: added mic light mode
updating to version 1.2.1
huge props to @andip71
wolfson_sound: adding version to the misc device
so we can show it in the control app
power: Samsung factory limit workaround

This avoids userspace factory limit of the CPU frequency without breaking power savings mode.