On Thu, 2020-11-26 at 17:43 +0100, Bastien Nocera wrote: > On Thu, 2020-11-26 at 15:57 +0000, Max Illis wrote: > > I raised a ticket on upower, but have been pointed here > > (https://gitlab.freedesktop.org/upower/upower/-/issues/125) > > > > _Some_ info is reported: > > > > ``` > > /sys/class/power_supply/hidpp_battery_1$ ls > > device manufacturer online powers serial_number subsystem > > uevent > > wakeup27 > > hwmon3 model_name power scope status type > > voltage_now > > ``` > > But nothing is reported by upower apparently due to `capacity` or > > `capacity_level` missing > > > The voltage is output, but it's not interpreted, so it's impossible to > know what XX volts corresponds to as a battery level. > > Hans, Benjamin, any ideas how this could be better handled? Are we > going to need voltage <-> capacity mapping? > > Cheers > > > > > I'm running Ubuntu 20.10 Linux 5.8.0-29-generic > > > > LMK if more info is needed > > Max > > > > max@xxxxxxxx > > 07803 009 004 > > > > max@xxxxxxxx > > 07803 009 004 > > Relevant UPower issue: https://gitlab.freedesktop.org/upower/upower/-/issues/110 Logitech gave us permission to use the battery curve in OSS software, I can get it from them. The issue is where to put it. I am not sure Benjamin would be happy with embedding it in the kernel driver. I think knowing that was been the blocking factor, although I did not do a good job trying to following it up. Cheers, Filipe Laíns
Attachment:
signature.asc
Description: This is a digitally signed message part
