summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorSubbaraman Narayanamurthy <subbaram@codeaurora.org>2016-12-22 15:09:38 -0800
committerSubbaraman Narayanamurthy <subbaram@codeaurora.org>2017-01-03 19:30:23 -0800
commit3d493610e3122b10fab0f1ec5d99c1fef6621aff (patch)
tree5843e3f587be32455c9191a19b129658ebfb21d6 /tools/perf/scripts/python
parent1897bd682b846b12b2aedd44efef29dd9b47e78b (diff)
qpnp-fg-gen3: clear profile integrity bit upon battery removal
In certain cases like battery hotswap where a strong charger is connected and battery is re-inserted, the expectation from the user is to reload the battery profile. This cannot happen unless a dVdd reset happens and wipes out FG SRAM. To help with the aforementioned scenario, clear the profile integrity bit every time when the battery is re-inserted. This way, FG driver will reload the profile everytime upon battery insertion. When the battery is missing, cycle counters cannot be cleared as the access to FG SRAM might not succeed. Hence remove it from the battery removal path. It will be cleared anyways when the profile is loaded after the battery is inserted. While at it, show the cached value of battery_id instead of reading it every time from RR_ADC peripheral. When the battery is re-inserted, battery id is obtained from RR_ADC driver anyways which is sufficient. Change-Id: I0b9566f7a9fcc81e26e68280382e2d960c49eeb5 Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions