The AXP803 is connected via the RSB bus to the A64 (I2C compatible), the USB pins are connected for charger class detection but carry no data...
You can program the AXP registers either from u-boot or the AXP linux kernel driver, also the Pine dts contains most of the registers for the AXP...
How the AXP is handled is a bit more complicated since the A64 has an embedded management processor (OpenRISC based AR100, see http://linux-sunxi.org/AR100) which gets loaded with firmware during boot as part of loading the ATF and u-boot. This embedded managmenet processor handles most of the power-management tasks and suspend states. I wrote up some of my research on that over here:
https://forum.pine64.org/showthread.php?...ght=AXP803
I recently figured out some more info on how to properly add battery parameters and will make a post about that...
Programming the charge LED registers works for me, also programing the LED on the GPIO can be done via sysfs or the LED class as you described above, but you have to adapt the mappings for the pinmux...
You can program the AXP registers either from u-boot or the AXP linux kernel driver, also the Pine dts contains most of the registers for the AXP...
How the AXP is handled is a bit more complicated since the A64 has an embedded management processor (OpenRISC based AR100, see http://linux-sunxi.org/AR100) which gets loaded with firmware during boot as part of loading the ATF and u-boot. This embedded managmenet processor handles most of the power-management tasks and suspend states. I wrote up some of my research on that over here:
https://forum.pine64.org/showthread.php?...ght=AXP803
I recently figured out some more info on how to properly add battery parameters and will make a post about that...
Programming the charge LED registers works for me, also programing the LED on the GPIO can be done via sysfs or the LED class as you described above, but you have to adapt the mappings for the pinmux...
Come have a chat in the Pine IRC channel >>