• State TI Thinks Resolved
  • Locked Locked
  • Replies 54 replies
  • Answers 10 answers
  • Subscribers 65 subscribers
  • Views 1253 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BQ25180: Linux code compatible kernel 6.1.55

Leo Yang
Expert 5595 points
Part Number: BQ25180

Tool/software:

HI team,

Do we have Linux code base on kernel 6.1.55 for BQ25180?

Thanks,

Leo

  • 0 in reply to Alec Lehman
    Intellectual 270 points

    Hi Alec,

    Thanks for your support .

    I have changed BQ2518X_CHG_STAT_STEP from 4 to 5. But it doesn't seem to see any change. I'm not sure if POWER_SUPPLY_STATUS can accurately reflect the battery charging status in real time, because it keeps showing "Not charging".

    Thanks.

  • 0 in reply to Jason Chou
    TI__Expert 7920 points

    Hi Jason,

    Thanks for the update.

    Could you try:

    cat /sys/class/power_supply/bq2518x-mains/status

    Does this show the correct charging state in real time?

    Best regards,
    Alec

  • 0 in reply to Alec Lehman
    Intellectual 270 points

    Hi Alec, 

    Thanks for your support .

    The execution results of commands "cat /sys/class/power_supply/bq2518x-mains/status" and "cat /sys/devices/platform/soc@0/44000000.bus/44340000.i2c/i2c-0/0-006a/power_supply/bq2518x-mains/uevent" are the same about POWER_SUPPLY_STATUS.

    I found that after unplugging and plugging the battery, I could see "POWER_SUPPLY_STATUS=Charging". About one minute later, "POWER_SUPPLY_STATUS=Unknown" and Reg01 changed from 0x39 to 0x01.  Another minute later, "POWER_SUPPLY_STATUS=Not charging", and Reg01 changed from 0x01 to 0x61. Then Reg01 varied among 0x61, 0x51 and 0x41, but "POWER_SUPPLY_STATUS=Not charging" no longer changed.

  • 0 in reply to Jason Chou
    TI__Guru** 105590 points

    Hello Jason,

    Could you clarify the issue you are trying to resolve? From what I can tell there's an unexpected delay between the command and when data is updated and unpredictable data returned?

    Alec will be out until next week, it may be easier for him to assist you due to the length of the thread.

    Sincerely,

    Wyatt Keller