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: Mon, 17 Aug 2026 09:20:49 +0000 [thread overview]
Message-ID: <bug-221142-208809-gmeHTJa3um@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 (huangwei@kylinos.cn) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |huangwei@kylinos.cn
--- Comment #1 from Wei Huang (huangwei@kylinos.cn) ---
Hi Alstergee,
Thanks for the detailed report, and for verifying that blacklisting
ucsi_acpi restores normal PD negotiation on this machine.
The cleanest way forward is a DMI quirk for this model in
drivers/usb/typec/ucsi/ucsi_acpi.c - there is already a quirk mechanism
there, used for a similar EC firmware problem on LG gram laptops. To
write the quirk, I need the exact DMI identification strings of the
machine, which are not part of the report.
Could you please attach the output of:
sudo dmidecode -t system
Alternatively, the contents of these files:
/sys/class/dmi/id/sys_vendor
/sys/class/dmi/id/product_name
/sys/class/dmi/id/product_version
/sys/class/dmi/id/product_family
/sys/class/dmi/id/product_sku
/sys/class/dmi/id/board_name
/sys/class/dmi/id/board_version
With that information I can prepare a patch and submit it upstream.
Thanks!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-08-17 9:20 UTC|newest]
Thread overview: 2+ 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 ` 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-gmeHTJa3um@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