On 13/12/2024 15:19, Dimitri Fedrau wrote: > >> But what I don't get is why GPIO chager needs it, since this is >> non-configurable for GPIO charger. >> > With properties charge-current-limit-gpios and charge-current-limit-mapping > one can define charge current limits in uA using up to 32 GPIOs. At the > moment the driver defaults to smallest current limitation for safety > reasons. When disabling charging should be possible as in the example, > the charger defaults to non-charging. By having a default the charge > current limit can be setup on probe and charging is enabled. OK, the commit msg should explain the intention and real use case you are solving here. Plus you miss the dependency - this property depends on charge-current-limit-mapping. Best regards, Krzysztof
