https://bugs.kde.org/show_bug.cgi?id=497200

Jakob Petsovits <jpe...@petsovits.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://invent.kde.org/plas
                   |                            |ma/powerdevil/-/commit/54c5
                   |                            |159156984265ab6485a2e55152d
                   |                            |242eeb130
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Jakob Petsovits <jpe...@petsovits.com> ---
Git commit 54c5159156984265ab6485a2e55152d242eeb130 by Jakob Petsovits.
Committed on 02/03/2025 at 22:37.
Pushed by jpetso into branch 'master'.

daemon: Fix charge threshold support for Dell laptops, maybe more

Some kernel drivers expose `charge_types` in addition to start/end
charge thresholds for power supply batteries. A prominent example
is the `dell_laptop` starting with Linux 6.12, which supports
(at least some) Dell Latitude laptops.

This commit will attempt to write a charge type on Linux systems
if the battery's `charge_types` file exists in sysfs.
It will write `Standard` as charge type if the configuration asks
for fully charging the laptop, and `Custom` for all other charge
threshold values.

The KAuth helper also now supports writing explicitly provided
charge types, however the settings UI does not make use of this yet.

This commit does not (yet) implement reading current or supported
charge types, because that's not useful without a settings UI.
Note that charge threshold settings are only applied when values
are changed, so any pre-existing charge type (e.g. `Fast`) won't be
touched without an explicit interaction.

M  +75   -13   daemon/chargethresholdhelper_linux.cpp

https://invent.kde.org/plasma/powerdevil/-/commit/54c5159156984265ab6485a2e55152d242eeb130

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to