Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221142] ucsi_acpi actively breaks USB-C PD charging on Lenovo Legion Pro 7 (Arrow Lake)
Date: Fri, 20 Nov 2026 02:57:49 +0000	[thread overview]
Message-ID: <bug-221142-208809-7iyiepIC4y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221142-208809@https.bugzilla.kernel.org/>

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

Wei Huang (daway320@163.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daway320@163.com

--- Comment #4 from Wei Huang (daway320@163.com) ---
Hi Alex,

Syncing the mailing list outcome here for the bugzilla record.

The v3 patch ("usb: typec: ucsi: do not register UCSI on Lenovo
Legion Pro 7 16IAX10H") has been withdrawn after Alex's re-test
showed the premise does not hold:

- With ucsi_acpi and typec_ucsi blacklisted and confirmed not
  loaded, USB-C charging still drops - the EC itself loses sight
  of the adapter (ADPT clearing in EC register 0xA3), replug or
  charger swaps often do not recover it, and only a power cycle
  reliably does.
- Windows on the same machine charges reliably over USB-C using
  the stock Microsoft UCSI driver (UcmUsciAcpiClient), so UCSI
  traffic itself is not what breaks charging.

This means the ucsi_acpi driver is not the cause on this machine,
and the issue is being re-scoped to the EC/ACPI layer - the drops
coincide with bursts of "workqueue: acpi_os_execute_deferred
hogged CPU for >10000us" warnings from ACPI/EC event handling,
with UCSI not loaded.

Leaving the bug open for the follow-up data. The mailing list
thread, including the withdrawal and the suggested next capture
(an EC transaction trace during a drop, to separate GPE handler
vs polling query vs buffered event burst):
https://lore.kernel.org/linux-usb/20260902090531.2134150-1-huangwei@kylinos.cn/

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

      parent reply	other threads:[~2026-11-20  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 23:03 [Bug 221142] New: ucsi_acpi actively breaks USB-C PD charging on Lenovo Legion Pro 7 (Arrow Lake) bugzilla-daemon
2026-08-17  9:20 ` [Bug 221142] " bugzilla-daemon
2026-08-26  2:33 ` bugzilla-daemon
2026-08-26  3:55 ` bugzilla-daemon
2026-11-20  2:57 ` bugzilla-daemon [this message]

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-221142-208809-7iyiepIC4y@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