All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219517] New: REGRESSION: charge_control missing in 6.12
Date: Wed, 20 Nov 2024 15:56:51 +0000	[thread overview]
Message-ID: <bug-219517-215701@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219517
           Summary: REGRESSION: charge_control missing in 6.12
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: auslands-kv@gmx.de
        Regression: No

On my ASUS Vivobook S14 (TP3402VA) I noticed that with kernel 6.12(-rc4,-rc7)
several charge control related /sys entries are missing.

with kernel 6.12 the corresponding folder looks like this:
ls /sys/class/power_supply/BAT0/

alarm               charge_now   manufacturer   status      voltage_min_design
capacity            current_now  model_name     subsystem   voltage_now
capacity_level      cycle_count  power          technology
charge_full         device       present        type
charge_full_design  hwmon3       serial_number  uevent

Specifically missing is charge_control_end_threshold, which is normally used to
set individual charge end points. That worked nicely up to kernel 6.11, but is
defect now in the current 6.12 version.

Anything special you need from me to fix the problem?

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

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

             reply	other threads:[~2024-11-20 15:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 15:56 bugzilla-daemon [this message]
2024-11-20 21:19 ` [Bug 219517] REGRESSION: charge_control missing in 6.12 bugzilla-daemon
2024-11-21  5:50 ` bugzilla-daemon
2024-11-21  5:56 ` bugzilla-daemon
2024-11-21  6:09 ` bugzilla-daemon
2024-11-21  8:59 ` bugzilla-daemon
2024-11-21  9:07 ` bugzilla-daemon
2024-11-21  9:07 ` bugzilla-daemon
2024-11-21  9:09 ` bugzilla-daemon
2024-11-21 11:26 ` bugzilla-daemon
2024-11-21 11:28 ` bugzilla-daemon
2024-11-21 11:34 ` bugzilla-daemon
2024-11-21 13:24 ` bugzilla-daemon
2024-11-21 13:58 ` bugzilla-daemon
2024-11-21 21:41 ` bugzilla-daemon
2024-11-21 21:44 ` bugzilla-daemon
2024-11-22 12:21 ` bugzilla-daemon
2024-11-22 12:27 ` bugzilla-daemon
2024-11-22 14:36 ` bugzilla-daemon
2024-11-22 14:40 ` bugzilla-daemon
2024-11-23 22:22 ` bugzilla-daemon
2024-11-24 13:24 ` bugzilla-daemon
2024-12-10  4:18 ` bugzilla-daemon
2024-12-14 10:49 ` bugzilla-daemon
2024-12-15 19:28 ` bugzilla-daemon
2024-12-16  8:53 ` bugzilla-daemon
2024-12-16 15:01 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-219517-215701@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.