* [Bug 221142] ucsi_acpi actively breaks USB-C PD charging on Lenovo Legion Pro 7 (Arrow Lake)
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
2 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2026-08-26 2:33 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=221142
--- Comment #2 from Alstergee (alex@alstergee.com) ---
Hi Wei,
Thanks for picking this up! Here's the DMI information:
`sudo dmidecode -t system`:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 83F5
Version: Legion Pro 7 16IAX10H
Serial Number: <redacted>
UUID: <redacted>
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_83F5_BU_idea_FM_Legion Pro 7 16IAX10H
Family: Legion Pro 7 16IAX10H
Contents of the requested `/sys/class/dmi/id/` files:
sys_vendor = LENOVO
product_name = 83F5
product_version = Legion Pro 7 16IAX10H
product_family = Legion Pro 7 16IAX10H
product_sku = LENOVO_MT_83F5_BU_idea_FM_Legion Pro 7 16IAX10H
board_name = LNVNB161216
board_version = SDK0T76461 WIN
Additional context that may be useful for matching:
bios_vendor = LENOVO
bios_version = Q7CN78WW
bios_date = 04/07/2026
board_vendor = LENOVO
chassis_vendor = LENOVO
chassis_type = 10 (Notebook)
The BIOS has been updated since I filed the report (Q7CN44WW -> Q7CN78WW,
April 2026). Symptoms are unchanged — ucsi_acpi still returns empty PDO
data and interferes with EC-side PD negotiation; blacklisting ucsi_acpi
still fully restores charging.
Also worth noting: the AMD variant of this laptop is DMI product 83RU
(Legion Pro 7 16AFR10H, BIOS prefix SMCN). It uses the same EC firmware
(ITE IT5508, EC ID 0x5508) and the community reports the same PD
negotiation failure there. It might be worth matching both product names
in the quirk if that's how the LG gram quirk is structured.
Currently running Ubuntu 26.04.1 LTS, kernel 7.0.0-30-generic.
Thanks,
Alex Bartz
eleso.app
FestivalWiFiGuys.com
Alstergee.com
[image: mobilePhone] +1 (801) 808-1498 <+1%20(801)%20808-1498>
[image: emailAddress] alex@alstergee.com <alex@festivalwifiguys.com>
CONFIDENTIAL & PRIVILEGED: This communication and any attachments may
contain information that is confidential, privileged, and/or exempt
from disclosure under applicable law. If you are not the intended
recipient, any review, use, dissemination, distribution, or copying is
strictly prohibited. If you received this in error, please notify the
sender immediately and permanently delete all copies.
On Mon, Aug 17, 2026 at 3:20 AM <bugzilla-daemon@kernel.org> wrote:
> 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 on the CC list for the bug.
> You reported the bug.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug 221142] ucsi_acpi actively breaks USB-C PD charging on Lenovo Legion Pro 7 (Arrow Lake)
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
2 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2026-08-26 3:55 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=221142
--- Comment #3 from Wei Huang (huangwei@kylinos.cn) ---
Hi Alstergee,
Thanks for the detailed DMI info - and for the note about the AMD
sibling (83RU). I've kept the quirk to 83F5 for now, since the failure
is only confirmed on your model; 83RU can be added once someone
confirms it there.
A patch has been submitted to the linux-usb mailing list:
usb: typec: ucsi: do not register UCSI on Lenovo Legion Pro 7 16IAX10H
https://lore.kernel.org/linux-usb/20260826034658.2170407-1-huangwei@kylinos.cn/
It adds a DMI quirk that makes ucsi_acpi skip binding on this model,
which is functionally the same as the blacklist workaround you already
verified - the module can stay loaded, but it will not touch the EC's
UCSI mailbox.
If you have a chance to test it (build a kernel with the patch applied,
make sure ucsi_acpi is no longer blacklisted, and reboot), the
confirmation I'd need is:
- a dmesg line like:
ucsi_acpi USBC000:00: UCSI implementation in firmware is broken,
ignoring
- normal PD charging restored (voltage_now non-zero, chargers hold).
If that works, it would help to have a formal Tested-by tag from you,
which lets the subsystem maintainer pick the fix up directly. Just reply
with:
Tested-by: Alex Bartz <alex@alstergee.com>
Thanks again for the quick and thorough help!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread