raise MDP bandwidth parameters
msm:board-8064: Correct ab/ib values of 1080p turbo vectors
This change corrects the ab/ib values of turbo vectors
intended for 1080p encoder.
iommu: msm: Configure memory attribute overrides

The default IOMMU memory attribute setting results in
reduced performance as a result of downgrading memory
attributes. Fix that.
Revert "Revert Drivers/media to pantech official source to fix camera"

This reverts commit 5577b532e39afedd35ab628c382795353f8a4e51.
Revert Drivers/media to pantech official source to fix camera again
ion: ioctl compat with old api to fix camera and audio
add debug log for pm8xxx-vibrator
Revert "ion: ioctl compat with old api to fix camera and audio"

This reverts commit a6d6dff629812ced6f6ec37bfa2fb77eaf0332e5.
Merge changes from Pantech Opensource(IM-A860L-163)
Fix audio&camera ion compat,Enable WFD,add changes from IM-A860L-136
raise MDP bandwidth parameters again
misc changes for A860
Modify configs
tiny changes on drivers/media
kernel: Add hooks for user-accessible timers in the kernel.
misc changes
Add cpu voltage control
added CPU freq governor wheatley
block: add simple io scheduler
block: fiops ioscheduler core FIOPS (Fair IOPS) ioscheduler
 is IOPS based ioscheduler, so only targets for drive without I/O seek. It's
 quite similar like CFQ, but the dispatch decision is made according to IOPS
 instead of slice.

The algorithm is simple. Drive has a service tree, and each task lives in
the tree. The key into the tree is called vios (virtual I/O). Every request
has vios, which is calculated according to its ioprio, request size and so
on. Task's vios is the sum of vios of all requests it dispatches. FIOPS
always selects task with minimum vios in the service tree and let the task
dispatch request. The dispatched request's vios is then added to the task's
vios and the task is repositioned in the sevice tree.

Unlike CFQ, FIOPS doesn't have separate sync/async queues, because with I/O
less writeback, usually a task can only dispatch either sync or async requests.
Bias read or write request can still be done with read/write scale.

One issue is if workload iodepth is lower than drive queue_depth, IOPS
share of a task might not be strictly according to its priority, request
size and so on. In this case, the drive is in idle actually. Solving the
problem need make drive idle, so impact performance. I believe CFQ isn't
completely fair between tasks in such case too.