From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221776] HP OmniBook X Flip - Broken UCSI firmware / Slow charging
Date: Mon, 10 Aug 2026 18:10:06 +0000 [thread overview]
Message-ID: <bug-221776-208809-nbcN89ir2T@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221776-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221776
--- Comment #3 from David Del Sol (daviddelsol1998@gmail.com) ---
Updating this report with the verified root cause, found since the original
filing.
The slow-charging issue is NOT UCSI firmware corruption. Root cause: the EC
only enables normal charging when the OS claims _OSI("Windows 2022"). Verified:
- DSDT/SSDT (via strings on /sys/firmware/acpi/tables/*) contain OSI checks
only up to "Windows 2022"; the kernel's default claimed OSI strings stop before
that.
- Adding acpi_osi=! acpi_osi="Windows 2022" to the kernel cmdline restores
31-33 W charging immediately, reproducibly, on kernels 7.1.6 and 6.18.42-LTS,
across multiple charge cycles (currently 27.8 W, battery 79%).
- This works with ucsi_acpi loaded -- the driver does not need to be
blacklisted, so the proposed ucsi_acpi.c DMI quirk in Comment 1 is unnecessary
and is withdrawn.
Per Greg's note: the correct upstream fix is a DMI-scoped OSI quirk in
drivers/acpi/osi.c (linux-acpi mailing list). Filed as a new report with full
evidence and EC RAM attachments:
https://bugzilla.kernel.org/show_bug.cgi?id=221866
Separate, intermittent issue (still open, tracked in 221866): on ~1 in 4
plug/unplug events the 65 W charger's PD contract occasionally sticks at 5 V /
3 A (~0.2 W to battery) until reboot. UCSI driver reload and suspend/resume did
not recover it. Not reproduced in later cycles; appears to be a PD
renegotiation race.
Closing this bug as resolved-by-workaround: acpi_osi=! acpi_osi="Windows 2022"
on the kernel command line.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-08-10 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:27 [Bug 221776] New: HP OmniBook X Flip - Broken UCSI firmware / Slow charging bugzilla-daemon
2026-07-21 18:30 ` [Bug 221776] " bugzilla-daemon
2026-07-22 5:29 ` Greg KH
2026-07-22 5:29 ` bugzilla-daemon
2026-08-10 18:10 ` bugzilla-daemon [this message]
2026-08-10 18:10 ` [Bug 221776] HP OmniBook X Flip - Slow charging root cause: EC gates charging on _OSI("Windows 2022") 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-221776-208809-nbcN89ir2T@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox