I am thinking mainly of tlp because that is what i use, but it would probably be good for an implementation to be able to use different backends, as i’m sure many people use power profiles daemon.
Both of these have a dbus interface, but tlp itself is mostly just shell scripts.
Battery charge levels might be tougher, AFAIK for a unified-ish interface there’s pretty much only tlp for not-that-many devices, and even then, you configure by writing to the tlp configuration file. Not impossible, but i’d wager it would be less effort to contribute a smoother way of setting it to tlp than doing so.
I am thinking mainly of tlp because that is what i use, but it would probably be good for an implementation to be able to use different backends, as i’m sure many people use power profiles daemon.
Both of these have a dbus interface, but tlp itself is mostly just shell scripts.
Battery charge levels might be tougher, AFAIK for a unified-ish interface there’s pretty much only tlp for not-that-many devices, and even then, you configure by writing to the tlp configuration file. Not impossible, but i’d wager it would be less effort to contribute a smoother way of setting it to tlp than doing so.