Hi Sebastian, I came across your generic gpio-charger driver while looking at a design using lrc4041 charging a super-capacitor that is providing a few seconds of backup power. Since the charger only reports status via gpios, it seems like a fit. At a closer look however none of my signals match exactly. I want to explore possibility of extending your driver, please can you comment if this driver is a suitable place for achieving below goals?: (Relevant) Signals: - PFO: Power-Fail, reports losing mains - CAPGD: Super-Capacitor Power-Good, reports whether capacitor is >= 92.5% - CAPFLT: Super-Capacitor Fault Status, effectively reports if charging stopped - CHGEN: Enable/Disable charging Intended use-case: Kernel should detect losing mains (or better !CAPGD), then either generate event for user-space to perform graceful shutdown, or trigger shutdown by itself. So far we have abused gpio-keys monitored from userspace. I think two properties from existing dt-bindings can match: gpios: <&PFO>; charge-status-gpios: <&CAPFLT>; In my opinion driver is missing: 1. disable-gpio: <&CHGEN>; 2. something to describe battery charge level. E.g. I have CAPGD signal which says either: - 0: level < 92.5% - 1: level >= 92.5% This could be simplified to 0% and 92.5% sincerely Josua Mayer
