<apritzel>
wouldn't energy_full_design be a parameter of the battery itself, so something that should come from the DT?
<apritzel>
looks like there is a energy-full-design-microwatt-hours property for a node with the "simple-battery" compatible string, and the core code would automatically use that
<apritzel>
so when someone knows this number, it might be enough to add such a node to the DT, and link it via the "monitored-battery" property, cf. rk3399-pinebook-pro.dts
<diego71>
apritzel: interesting. I take a look in the evening and see what it happens
machinehum2 has quit [Read error: Connection reset by peer]
warpme has joined #linux-sunxi
kuba2k2 has joined #linux-sunxi
dsimic is now known as Guest12618
dsimic has joined #linux-sunxi
Guest12618 has quit [Ping timeout: 480 seconds]
kuba2k2 has quit [Ping timeout: 480 seconds]
machinehum has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.2]
warpme has quit []
kuba2k2 has joined #linux-sunxi
warpme has joined #linux-sunxi
junari has joined #linux-sunxi
bauen1 has joined #linux-sunxi
kuba2k2 has quit [Ping timeout: 480 seconds]
megi has quit [Quit: WeeChat 4.1.1]
kuba2k2 has joined #linux-sunxi
megi has joined #linux-sunxi
vertex004 has joined #linux-sunxi
machinehum has quit [Read error: Connection reset by peer]
kuba2k2 has quit []
vertex004 has quit [Remote host closed the connection]
tnovotny has quit [Quit: Leaving]
chewitt has quit [Quit: Zzz..]
warpme has quit []
warpme has joined #linux-sunxi
ftg has joined #linux-sunxi
dliviu has joined #linux-sunxi
nashpa has quit [Ping timeout: 480 seconds]
vertex004 has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
bauen1 has quit [Ping timeout: 480 seconds]
warpme has quit []
JohnDoe_71Rus has quit []
bauen1 has joined #linux-sunxi
vagrantc has joined #linux-sunxi
vertex004 has quit [Remote host closed the connection]