smdk4412 devices: higher the number of s5p fb buffers

Change-Id: I72f48c7fd925a52d4888b9a3b64233d5abc9978f
smdk4412 devices: double memsize for fimd

Change-Id: I75c4f4ff5ec2e35a9a16749b0c36e84ec29ff141
Revert "smdk4412 devices: higher the number of s5p fb buffers"

This reverts commit 9b7a40b5e21e93fb608636d2c11f6eb51539395c.
Revert "smdk4412 devices: double memsize for fimd"

This reverts commit 106c5f53d1bb1d1cee929ef83ddf320954a1fd80.
s6evr02: Allow max brightness at 255

Change-Id: I464de83d010702ed68759f2bde438c127811bd2e
smdk4412: reboot bootloader boots into download mode

Change-Id: I7fff613ec8b4dcd4bae58ee4aab51c64e571025f
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
Merge "smdk4412: s3cfb_s6e8ax0: Stop fb shitstorm in kmsg" into mr1-staging
mem: fix permissions on exynos-mem

Change-Id: Ibf2312ce36952c28baa5476a5a856edde8d84de5
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.

Change-Id: I286be4a2546621c66d214c79f480822ecd8138db
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.

Change-Id: Ib35e9d1c29e977774265f1e123a7ef13353485ad

Conflicts:
	drivers/char/exynos_mem.c
n7100: CONFIG_USE_FIMC_CMA

Change-Id: I83e1c08d06ae5f749f70c11993218968fe9b09bf
Added core count load biasing
Merge branch 'jellybean' of https://github.com/MazWoz/android_kernel_samsung_smdk4412 into jellybean