Another thing spotted - mentioned earlier:

Acts very strangely. It is supposed to mean 100 mA termination current, as lowest value it accept is 6500, which is 50 mA, and lowest value accepted by chip. Hoever, highest value accepted by chip is 400 mA, which should be 6850 as sysfs value. Unfortunately, it accepts 6800 as max (changes itself to 6800, if higher value is presented)

Which is even more confusing, after changing it, You're absolutely enable to provide default value (6550) again - whatever one input there, it changes itself to 6500 or 6800, *only*. It refuses to accept anything in between, as said, even value that was set by default. fortunately, unloading module, enabling bme, disabling bme and loading module again, bring all related sysfs values to default.

I may be wrong, but this one sounds absolutely like bug to me.

/Estel

// Edit

branja, to charge with bq2415x_charger, You need to, as root:

To stop using it, You do:

Advantages - it's huge step toward introducing replacement for bme. Currently, only two direct advantages for end-user apply - possibility to set own charging current (higher one for bigger batteries, for example) and termination current (for terminating charging properly during heavy load), and possibility of charging during USB hostmode.

Basic goal is to replace BME, but of course, being totally open, bq2415x_charger have virtually countless possibilities. It should be easy to write scripts/program for - as example - enabling, when invoked, charging only to 80% (save battery health), or to introduce leaving device on charger without negative impact on battery (now BME doesn't necessary follow best practices re extending life of battery).