diff options
| author | Subbaraman Narayanamurthy <subbaram@codeaurora.org> | 2017-01-20 18:34:28 -0800 |
|---|---|---|
| committer | Subbaraman Narayanamurthy <subbaram@codeaurora.org> | 2017-02-06 19:49:59 -0800 |
| commit | d928f051d5b138e3404790b8e39b7549b3d0a8fa (patch) | |
| tree | 4b369e887e4cc438c2c809e196976ab55687f711 /fs/jbd2/commit.c | |
| parent | 9d27ab2fe7be97624fc20450e22276ba0d0fb360 (diff) | |
qcom: qpnp-fg-gen3: Reconfigure BMD during bootup
Booting up with higher battery id (e.g. 300KOhms) can cause a
failure in driver probe because none of the SRAM transactions
can go through during boot. This seems to be happening because
FG ALG treats it as a battery missing. Since driver fails to
probe early, it cannot even handle an interrupt to reconfigure
BMD. Hence, reconfigure BMD every time when the battery id is
obtained.
Since getting battery id now requires couple of SPMI writes,
move fg_get_batt_id() out of fg_get_batt_profile() as the latter
will be called from fg_parse_dt(). This makes fg_parse_dt() only
for parsing device tree properties from the device.
Change-Id: I1638f7325ce73b03f1ea54455f777f92cf8d06b3
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions
