Call cpufreq_update_policy on DVFS events.
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
Oooops... Best if the lock is set correctly.  :/
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
Updates!

Updated defconfigs
Added Samsung Param driver
Removed Generic BLN driver(as we have one in the touchscreen driver)

Change-Id: Idf05e25e0190d314c12c8b634ba35d4156e7966c

Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
HACK: block fbearlysuspend to not break androids crt-off animation
Revert "Changes for bcmdhd."
Needed to cleanly pull in wifi driver updates in next commit.
This reverts commit b61afb5d981d9fc75ca7917a467dfc1763be71b5.
net: wireless: bcmdhd: update bcmdhd driver to 1.15.15
bcmdhd: Change packet filter settings to block multicast

A common complaint of users is that battery life on wifi
is very poor, with frequent wlan_rx_wake wakelocks.

It turns out Samsung "opened up" the packet filter
settings from Gingerbread to ICS.

This makes them match the tuna configuration, minus
the filter to allow mDNS through (which lets a bunch
of other stuff through too.)

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
Fix blocking allocations called very early during bootup
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
Revert "S5PC11X : FIMC apply v4l2 standard for asynchronous dequeue/queue"

This reverts commit 5f4b037e6ebb18d65a3ac896032eb559d7fe2baf.
block: don't mark buffers beyond end of disk as mapped

commit 080399aaaf3531f5b8761ec0ac30ff98891e8686 upstream.

Hi,

We have a bug report open where a squashfs image mounted on ppc64 would
exhibit errors due to trying to read beyond the end of the disk.  It can
easily be reproduced by doing the following:

[root@ibm-p750e-02-lp3 ~]# ls -l install.img
-rw-r--r-- 1 root root 142032896 Apr 30 16:46 install.img
[root@ibm-p750e-02-lp3 ~]# mount -o loop ./install.img /mnt/test
[root@ibm-p750e-02-lp3 ~]# dd if=/dev/loop0 of=/dev/null
dd: reading `/dev/loop0': Input/output error
277376+0 records in
277376+0 records out
142016512 bytes (142 MB) copied, 0.9465 s, 150 MB/s

In dmesg, you'll find the following:

squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   43.106012] attempt to access beyond end of device
[   43.106029] loop0: rw=0, want=277410, limit=277408
[   43.106039] Buffer I/O error on device loop0, logical block 138704
[   43.106053] attempt to access beyond end of device
[   43.106057] loop0: rw=0, want=277412, limit=277408
[   43.106061] Buffer I/O error on device loop0, logical block 138705
[   43.106066] attempt to access beyond end of device
[   43.106070] loop0: rw=0, want=277414, limit=277408
[   43.106073] Buffer I/O error on device loop0, logical block 138706
[   43.106078] attempt to access beyond end of device
[   43.106081] loop0: rw=0, want=277416, limit=277408
[   43.106085] Buffer I/O error on device loop0, logical block 138707
[   43.106089] attempt to access beyond end of device
[   43.106093] loop0: rw=0, want=277418, limit=277408
[   43.106096] Buffer I/O error on device loop0, logical block 138708
[   43.106101] attempt to access beyond end of device
[   43.106104] loop0: rw=0, want=277420, limit=277408
[   43.106108] Buffer I/O error on device loop0, logical block 138709
[   43.106112] attempt to access beyond end of device
[   43.106116] loop0: rw=0, want=277422, limit=277408
[   43.106120] Buffer I/O error on device loop0, logical block 138710
[   43.106124] attempt to access beyond end of device
[   43.106128] loop0: rw=0, want=277424, limit=277408
[   43.106131] Buffer I/O error on device loop0, logical block 138711
[   43.106135] attempt to access beyond end of device
[   43.106139] loop0: rw=0, want=277426, limit=277408
[   43.106143] Buffer I/O error on device loop0, logical block 138712
[   43.106147] attempt to access beyond end of device
[   43.106151] loop0: rw=0, want=277428, limit=277408
[   43.106154] Buffer I/O error on device loop0, logical block 138713
[   43.106158] attempt to access beyond end of device
[   43.106162] loop0: rw=0, want=277430, limit=277408
[   43.106166] attempt to access beyond end of device
[   43.106169] loop0: rw=0, want=277432, limit=277408
...
[   43.106307] attempt to access beyond end of device
[   43.106311] loop0: rw=0, want=277470, limit=2774

Squashfs manages to read in the end block(s) of the disk during the
mount operation.  Then, when dd reads the block device, it leads to
block_read_full_page being called with buffers that are beyond end of
disk, but are marked as mapped.  Thus, it would end up submitting read
I/O against them, resulting in the errors mentioned above.  I fixed the
problem by modifying init_page_buffers to only set the buffer mapped if
it fell inside of i_size.

Cheers,
Jeff

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Acked-by: Nick Piggin <npiggin@kernel.dk>

--

Changes from v1->v2: re-used max_block, as suggested by Nick Piggin.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Conflicts:
	fs/block_dev.c

Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
cpufreq: boostfreq: do not set to current value

dbs_tuners_ins.boostfreq should not be set upon boosting, as it
will fix the boostfreq to the current max value, despite the
fact that it can change later (via cpufreq reconfiguration)

Change-Id: I12741ff367b37d6161e06f3d5de21807c5415a9d
oops
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
HOpefully fix 720p
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
Include cel147
Signed-off-by: scotthartbti <scott.hart.bti@gmail.com>
S5PC11X: FIMC: Modify to run fimc after all configurations

- Modify to set context info before running fimc hw
- Check whether context num is valid in ISR

Bug: 5790269
Change-Id: I5c579ab22ed360d25063102d22ed07b05c707e01
Signed-off-by: jung-min.oh <jung-min.oh@samsung.com>
S5PC11X: FIMC: Call sw reset when stopping fimc

Modify to call sw-reset whenever fimc finishes handling a frame.

Found a case that a timeout error occurred on fimc
during video playback aging test and after that,
fimc didn't recover from the abnormal status
in spite of right configurations.

According to hw team, sw-reset is called for each frame
to prevent fimc from entering into an abnormal state
by clearing internal registers in fimc.

Change-Id: I7fe5f4124400bbe37ec2033eff1b8355d68a3323
Signed-off-by: jung-min.oh <jung-min.oh@samsung.com>
S5PC11X: FIMC: Handle off mode in suspend()/resume()

Avoid clock gating in suspend()/resume() when ctrl->status is set
to FIMC_OFF_SLEEP because the fimc doesn't support it.
Prevent the fimc from turning on during resume when it is not used.

This patch fixes issue 5400100,
which says mp3 playback power usage increased by 33%.

Also, don't allow capture modue op during output mode, and vice-versa.

Change-Id: I705523a674f1102a77195ee2ee170935bcf4d41e
Signed-off-by: jung-min.oh <jung-min.oh@samsung.com>
Revert "HOpefully fix 720p"

This reverts commit 78524380936ead586440009abb7353aa0b555339.
Add WakeUp

The /sys/power/wakeup_count file allows user space to put the system into a sleep state while taking into account the concurrent arrival of wakeup events.
ARM: dma-mapping: free allocated page if unable to map