https://bugzilla.kernel.org/show_bug.cgi?id=221253

            Bug ID: 221253
           Summary: Add support for Thinkbook G7 ARP laptop 2024 for
                    setting Battery Charge Threshold (Ryzen)
           Product: ACPI
           Version: 2.5
          Hardware: IA-64
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Power-Battery
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 309705
  --> https://bugzilla.kernel.org/attachment.cgi?id=309705&action=edit
acpidump

Hi!

Could you please add support for Thinkbook G7 ARP laptop (2024, model 21MV) for
setting battery charge threshold.

If this is already supported, please advise what ACPI kernel module should one
use/load for Thinkbook G7 ARP laptop (2024) for setting battery charge
threshold?

Setting battery charge threshold is extremely important for preserving battery
life.
Constantly charging battery to 100% reduces its life several times!

Ryzen 5 7535HS (Zen 3+ APU).

With BOTH thinkpad_acpi and ideapad_laptop modules loaded there's files/devices
to set battery threshold in /sys/class/power_supply/BAT0:


lrwxrwxrwx 1 root root    0 Mar 17 16:09 subsystem ->
../../../../../../../../../class/power_supply
drwxr-xr-x 3 root root    0 Mar 17 16:09 ..
drwxr-xr-x 5 root root    0 Mar 17 16:09 .
drwxr-xr-x 3 root root    0 Mar 17 16:09 hwmon2
lrwxrwxrwx 1 root root    0 Mar 17 16:09 device -> ../../../PNP0C0A:00
-r--r--r-- 1 root root 4.0K Mar 17 16:09 type
-r--r--r-- 1 root root 4.0K Mar 17 16:09 present
-r--r--r-- 1 root root 4.0K Mar 17 16:09 status
-r--r--r-- 1 root root 4.0K Mar 17 16:09 voltage_now
-r--r--r-- 1 root root 4.0K Mar 17 16:09 voltage_min_design
-r--r--r-- 1 root root 4.0K Mar 17 16:09 technology
-r--r--r-- 1 root root 4.0K Mar 17 16:09 serial_number
-r--r--r-- 1 root root 4.0K Mar 17 16:09 power_now
-r--r--r-- 1 root root 4.0K Mar 17 16:09 model_name
-r--r--r-- 1 root root 4.0K Mar 17 16:09 manufacturer
-r--r--r-- 1 root root 4.0K Mar 17 16:09 energy_now
-r--r--r-- 1 root root 4.0K Mar 17 16:09 energy_full_design
-r--r--r-- 1 root root 4.0K Mar 17 16:09 energy_full
-r--r--r-- 1 root root 4.0K Mar 17 16:09 cycle_count
-r--r--r-- 1 root root 4.0K Mar 17 16:09 capacity
-rw-r--r-- 1 root root 4.0K Mar 17 16:10 charge_start_threshold
drwxr-xr-x 2 root root    0 Mar 17 16:28 power
drwxr-xr-x 2 root root    0 Mar 17 16:28 extensions
-rw-r--r-- 1 root root 4.0K Mar 17 16:28 charge_types
-rw-r--r-- 1 root root 4.0K Mar 17 16:28 charge_behaviour
-r--r--r-- 1 root root 4.0K Mar 17 16:28 capacity_level
-rw-r--r-- 1 root root 4.0K Mar 17 16:28 alarm
-rw-r--r-- 1 root root 4.0K Mar 17 16:35 charge_stop_threshold
-rw-r--r-- 1 root root 4.0K Mar 17 16:36 charge_control_start_threshold
-rw-r--r-- 1 root root 4.0K Mar 17 16:36 charge_control_end_threshold


But setting battery limit still FAILS (all ran from ROOT of course):

echo 85 > /sys/class/power_supply/BAT0/charge_control_end_threshold
-bash: echo: write error: No such device


echo 85 > /sys/class/power_supply/BAT0/charge_stop_threshold
-bash: echo: write error: No such device

No obvious error in DMESG for both commands above.

As soon as I unload thinkpad_acpi module (ideapad_laptop module still loaded),
all battery threshold file/devices dissapear from in
/sys/class/power_supply/BAT0:

lrwxrwxrwx 1 root root    0 Mar 17 16:09 subsystem ->
../../../../../../../../../class/power_supply
lrwxrwxrwx 1 root root    0 Mar 17 16:09 device -> ../../../PNP0C0A:00
drwxr-xr-x 3 root root    0 Mar 17 17:04 ..
-rw-r--r-- 1 root root 4.0K Mar 17 17:04 uevent
-r--r--r-- 1 root root 4.0K Mar 17 17:04 serial_number
-r--r--r-- 1 root root 4.0K Mar 17 17:04 technology
-r--r--r-- 1 root root 4.0K Mar 17 17:04 power_now
-r--r--r-- 1 root root 4.0K Mar 17 17:04 present
drwxr-xr-x 2 root root    0 Mar 17 17:04 power
-r--r--r-- 1 root root 4.0K Mar 17 17:04 manufacturer
drwxr-xr-x 3 root root    0 Mar 17 17:04 hwmon2
-r--r--r-- 1 root root 4.0K Mar 17 17:04 energy_now
-r--r--r-- 1 root root 4.0K Mar 17 17:04 type
-r--r--r-- 1 root root 4.0K Mar 17 17:04 capacity
-r--r--r-- 1 root root 4.0K Mar 17 17:04 cycle_count
-r--r--r-- 1 root root 4.0K Mar 17 17:04 voltage_now
-r--r--r-- 1 root root 4.0K Mar 17 17:04 status
-rw-r--r-- 1 root root 4.0K Mar 17 17:04 alarm
-r--r--r-- 1 root root 4.0K Mar 17 17:04 model_name
-rw-r--r-- 1 root root 4.0K Mar 17 17:04 charge_types
-r--r--r-- 1 root root 4.0K Mar 17 17:04 voltage_min_design
-r--r--r-- 1 root root 4.0K Mar 17 17:04 capacity_level
-r--r--r-- 1 root root 4.0K Mar 17 17:04 energy_full_design
-r--r--r-- 1 root root 4.0K Mar 17 17:04 energy_full
drwxr-xr-x 2 root root    0 Mar 17 17:04 extensions
drwxr-xr-x 5 root root    0 Mar 17 17:13 .


Tried all of these kernels: kernel 6.19.8-061908 installed Mainline app and
6.17 and 6.14 (multiple versions, supplied by distro).

lspci and acpidump output is attached.

Thank you very much.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to