Hi, On Fri, Feb 23, 2024 at 08:34:29PM +0500, Nikita Travkin wrote: > Sebastian Reichel писал(а) 23.02.2024 20:04: > > On Fri, Feb 23, 2024 at 07:32:17PM +0500, Nikita Travkin wrote: > >> >> + This driver provides battery and AC status support for the mentioned > >> > I did not see any AC status bits? > >> > >> I was referring to whatever ACPI spec calls "AC Adapter" but I guess > >> I should have used the word "charger" instead... Will reword this. > > > > But you only register a power-supply device for the battery and not > > for the AC adapter/charger. When you write "and AC status support" I > > would have expected something similar to this (that's from ACPI AC > > adapter driver): > > > > $ cat /sys/class/power_supply/AC/uevent > > POWER_SUPPLY_NAME=AC > > POWER_SUPPLY_TYPE=Mains > > POWER_SUPPLY_ONLINE=1 > > Ah, I see... Yeah looking at it one more time, I mistakenly assumed the > acpi ac code uses the same data fields as the battery but seems like it > reads the single online flag from a different place. I don't think there > is really a point on implementing that field since we can still easily > track the battery charging/discharging status so I will probably omit it > for now. Will reword the help text to not mention charger/ac adapter. If you have the information easily available, it's a good plan to expose it. Without a charger reporting online status at least the kernel's power_supply_is_system_supplied() will return false (which is e.g. used by AMD GPU driver to select power profile). Generic userspace (i.e. upower) probably behaves similar, since battery status is not the same as AC connceted. A system might not charge the battery but still run from AC itself. -- Sebastian
Attachment:
signature.asc
Description: PGP signature
