FULL SOC is expected to be capped @ 99% for
system SOC calculations.

Change-Id: I5f99223ff55b1831793066c432d04ed60823881c
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>

The current check always returns a positive value due
to a unsigned in wrap-around. Fix it.

Change-Id: I28fea4ff67ffed82465e5cfa785414069e4a180b
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>

Adjust the PON SOC based on FULL and CUTOFF SOC to make sure
its scaled appropriately based on the float and cutoff-voltage
values.

Change-Id: I14b274dd7cad98b55fdce1aaa27783272231afd2
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>

Cancel the alarm timer and work only if the charger
termination workaround is enabled to avoid
a NULL pointer exception.

Change-Id: I573239db0f373d9188fc379653cedd305d2a552c
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>

In few scenarios where the buffers are not
queued from HAL, request queue overflow is seen.
Added changes to reset the queue at destroy and
when the buffer is not available to process.

Change-Id: I7239175dda9cbc26fb65f568cbc5f7183ceaa24d
Signed-off-by: Meera Gande <mgande@codeaurora.org>

In few scenarios, where the register update ioctl is
missed, the handling of frame drop is not working
in such scenarios as the frame drop pattern is not
set correctly. Once the epoch handling is done,
we need to re-configure the buffer and pattern.

Change-Id: I87b2cecda7e7e1addc68511dad6a80498051f87a
Signed-off-by: Meera Gande <mgande@codeaurora.org>

In few scenarios, the request frame may get
delayed and current and request frame id may
become same. While user space is informed to
delay a frame in such scenarios, the pattern
shouldn't get reset.

Change-Id: I63f1301fbbe7cba024a686cbd783af25232f1293
Signed-off-by: Meera Gande <mgande@codeaurora.org>

In few scenarios, the request frame may get
delayed and current and request frame id may
become same. To handle such scenarios, made
changes to inform user to delay a frame and
process the request.

Change-Id: I31fa04c386922c48a043c511a163c76316e21987
Signed-off-by: Meera Gande <mgande@codeaurora.org>

Currently tmp memory is deleted in device destroy method, but
there is no check for NULL. So it can cause for double free issue.

Change-Id: Ide8d8d24c0f9cea68597ecbf6b6b84269062384a
Acked-by: Pooja Kumari <kumarip@qti.qualcomm.com>
Signed-off-by: Mohammed Javid <mjavid@codeaurora.org>

This change is for general scheduler improvement.

Change-Id: I0caae436c933656c9a7b5135c6d4a8179be06631
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

LBF_ALL_PINNED flag should cleared in can_migrate_task() if the task
can run on the destination CPU during load balance. In current code,
can_migrate_task() return incorrectly without clearing this flag
in case if the task can't be migrated to the destination CPU due to
cumulative window demand constraints. Since LBF_ALL_PINNED flag
is not cleared, load balancer thinks that none of the tasks running
on the busiest group can't be migrated to the destination CPU due
to affinity settings and tries to find another busiest group. Prevent
this incorrect reattempt of load balance by clearing LBF_ALL_PINNED
flag right after the task affinity check in can_migrate_task().

Change-Id: Iad1cf42b1aaf70106ee5ecfbd9499ccb6eb7497e
[clingutla@codeaurora.org: Resolved merge conflicts]
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

There is a minor change to the frequency plan of the gold
cluster. Update the energy model accordingly.

Change-Id: I266a559fce11211e03f02c0f568c718ca77a9619
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

When the local group has idle CPUs and there is no imbalance
within the group, allow pulling the task from an overloaded group
by boosting the imbalance. The boost is needed for scenarios
where busiest group is overloaded but it's avg_load is not much
higher than the local group's avg_load.

For example, local group has 4 smaller capacity CPUs with 1024 as
total capacity and running two CPU intensive (load=1024) tasks.
Its avg_load is 1024. The busiest group has 1 highest capacity CPU
with 1024 as total capacity and running two CPU intensive (load=1024)
tasks. Its avg_load is also 1024. There is no difference in avg_load
between local group and busiest group. But the busiest group is
clearly overloaded.

The imbalance is derived from PELT runnable load average which takes
more time to reflect the full load. Since the group overloaded
condition uses WALT utilization metric, it reflects the full load
faster. So allowing idle load balance to pull more tasks when the
busiest group is overloaded would be beneficial for the performance.

This load balancer behavior is also inline with the current
task placement policy where a BIG task would be placed on the
lower capacity CPU when the higher capacity CPUs are overloaded.

Change-Id: I58ce198f38f6b949a0ef910550ef1a8b2b0528ca
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

This change is for general scheduler improvement.

Change-Id: Ie162a57537bb9ada66a4254d606e17d54b7a3a49
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
[pkondeti@codeaurora.org: code refactoring and implemented freq to load
calculations.]
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

This change is for general scheduler improvement.

Change-Id: I01e6610bba2e8c66a628d6289eeed4e854264fdd
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
[clingutla@codeaurora.org: resolve trivial merge conflicts.]
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>

Following addition and changes are added to 4.9 kernel
uapi headers:

uapi: Add new acquire/release HW IOCTLs
uapi: Adds UBWC blob payload structure to enable userspace
      control over UBWC configururation.
icp:  Send cmd buffer memory region to FW
isp:  start CSID with clock rate per sensor
isp:  Add support for BUS driver version 175
uapi: Add new Dual PD IFE output port

Change-Id: I94bcad553303f0eebed0f043f3610726e9793c3d
Signed-off-by: Raja Mallik <rmallik@codeaurora.org>

This dumps the necessary mdp registers for debug
when a fatal error occurs in msm8909w. The fatal
error can be a dma timeout or ppp timeout or an
smmu fault. This even populates necessary info to
debug structure.

Change-Id: I240cd762dc310cc22891985d2044087690b5c6ce
Signed-off-by: Jayaprakash <jmadiset@codeaurora.org>

As msm8909w wtp has different hardware design with msm8909 mtp,
update digital codec and sound card config for msm8909w wtp device.

Change-Id: I43885012dc2caee81a5a476657bf48f0f4ee4bfa
Signed-off-by: Manjunatha Madana <mamanj@codeaurora.org>

Add device tree support for sdw2500. This implementation
is based on snapshot of the sdw2500 device tree from
msm-3.18 commit bba04f93
("ARM: dts: msm: add synaptics touch firmware for wearables").

Change-Id: I6fdd6eb1813e1fc6d4c1b5fac8aa261e18d3e53a
Signed-off-by: Manjunatha Madana <mamanj@codeaurora.org>