BQ27426: fg_unseal reapeatly running over 1000 tims which affect the cell phone start up

Hi  team,

met a problem while debug bq27426:

we found there are small possibility that when power-up the cell phone, bq27426 unseal unsuccessfully, and below function repeat over 1000times and still could not unseal the gauge. which cause we could not wirte the register later.

i attached the function below:

also attched some logs file while occurs happen when power up the cell phone:

[    1.000764] bq27426- fg_get_seal_state: control_status = 0x288E

[    1.000768] bq27426- fg_unseal: :key - 0x80008000

[    1.060764] bq27426- fg_get_seal_state: control_status = 0x088E

[    1.080758] bq27426- fg_update_bqfs: Fuel Gauge parameter update, reason:New Version, version:1, batt_id=0 Start...

[    2.803853] bq27426- fg_update_bqfs_execute_cmd: CMD_C failed at line 0

[    2.803855] bq27426- fg_update_bqfs_execute_cmd: Read: FF, Cmp:C7

[    2.803856] bq27426- fg_update_bqfs: Failed at command: 86

[    8.430763] bq27426- fg_get_seal_state: control_status = 0x088E

[    8.470761] bq27426- fg_get_seal_state: control_status = 0x088E

[    8.700761] bq27426- fg_get_seal_state: control_status = 0x088E

[    8.930762] bq27426- fg_get_seal_state: control_status = 0x088E

[    9.160762] bq27426- fg_get_seal_state: control_status = 0x088E

[    9.390762] bq27426- fg_get_seal_state: control_status = 0x088E

[    9.620762] bq27426- fg_get_seal_state: control_status = 0x088E

[    9.850762] bq27426- fg_get_seal_state: control_status = 0x088E

[   10.080752] bq27426- fg_get_seal_state: control_status = 0x088E

[   10.310762] bq27426- fg_get_seal_state: control_status = 0x088E

[   10.540761] bq27426- fg_get_seal_state: control_status = 0x088E

[   10.770762] bq27426- fg_get_seal_state: control_status = 0x088E

[   11.000762] bq27426- fg_get_seal_state: control_status = 0x088E

[   11.230761] bq27426- fg_get_seal_state: control_status = 0x008E

[   11.460761] bq27426- fg_get_seal_state: control_status = 0x008E

Hope you could give us some comments and suggestions on this bug!

Thanks!

BR

Brandon.