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.

Linux/BQ25882: Device tree documentation

Part Number: BQ25882

Tool/software: Linux

Looking for device tree documentation for this part. Or any part with compatible dts entry.

Thanks

JW

  • Hi JW,

    The linux drivers are at github.com/.../bq2588x. Please keep in mind that the BQ25882 only has I2C registers setting thresholds for its state machine. The driver is simply a recommended structure for I2C reads and writes to those registers.

    Regards,
    Jeff
  • Thanks Jeff, I am already using those drivers. The driver attempts to parse a list of properties from the dt and I was just wondering if any of those properties where documented anywhere.That said, they are kind of clear in their description.

    What is still not really clear to me is why the driver needs a reference to a USB power supply. I'm just using a stub now so I can pass the probe check, but it would be nice to have it set up properly. Is there any generic usb supply driver available?

    Anyway I have the thing running now on the kernel level and almost in Android, where charging status is only reflected correctly on startup.

  • Jan,

    I am not aware of any USB driver in the TI bms tree. The reason for the USB reference is that in accordance with the USB BC1.2 specification, a device like BQ25882 with D+/D- detection, is only expected to identify the initial USB input current available in order to bring up the system host. The host is then expected to perform USB enumeration for the final input current that the USB port or adapter can provide.

    Regards,
    Jeff
  • The driver also sets the online state of the USB psy, which in turn is used in Android's healthd. This is used to show the device's charging state in the Android UI. Anyway I hacked my way around that now, I'm not writing production code... The only remaining issue I have now is that the driver doesn't generate/update uevent so when I plug in the charger, the kernel sees the change but Android doesn't.
  • Jan,

    Unfortunately, I am not a programmer and can't help you further with software questions. I suggest submitting a question on an Android forum.

    Regards,
    Jeff