On 9/28/18 8:15 AM, H. Nikolaus Schaller wrote:
Since my prototype wouldn't charge at all with a 4.18 kernel before, it now seems to at least pull in 0.4A.
Fine!
- does it report VBUS events on the console?
unplugging the microusb
[ 351.760651] bq24296_usb_detect: r8=00 r9=10 [ 351.765086] bq24296: VBUS became unavailable [ 352.797410] bq24296_usb_detect: r8=00 r9=00 [ 364.220633] bq24296_usb_detect: r8=04 r9=00 [ 364.225429] bq24296: VBUS became available [ 364.233549] bq24296_update_input_current_limit(6) [ 365.259249] bq24296_usb_detect: r8=2c r9=00
after this the input current limit is set to 0.5A , while before it was 2, manually changing it back to 2000000 upped the input current, although it only seems to pull in 1.0A max.
plugging in an usb otg device: [ 790.298962] bq24296_otg_enable(1) [ 790.805301] bq24296_usb_detect: r8=00 r9=10 [ 790.809831] bq24296: VBUS became unavailable [ 791.844583] bq24296_usb_detect: r8=00 r9=00
and removing it : [ 900.675855] bq24296_otg_disable(1) [ 901.035071] bq24296_usb_detect: r8=04 r9=00 [ 901.039503] bq24296: VBUS became available [ 901.043835] bq24296_update_input_current_limit(6) [ 902.075653] bq24296_usb_detect: r8=6c r9=00
the usb device itself (an usb/otg flash drive) doesn't show up. It works fine when plugging it in the normal usb port, but doesn't generate any vbus events there.
what does
cat /sys/class/power_supply/bq24297/input_current_limit
report?
2000000
- can you please try:
echo 2000000 >/sys/class/power_supply/bq24297/input_current_limit
input current stays the same, at slightly under 1.0A
On a 4.15 kernel (with the old driver) it usually sits at 1.5A on the same charger/cable/power meter setup
setting it to 3000000 seemed to push it slightly closer to 1.0A.
Attached is the full log.