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: Wed, 26 Aug 2026 02:33:51 +0000	[thread overview]
Message-ID: <bug-221142-208809-cvqCzywdgA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221142-208809@https.bugzilla.kernel.org/>

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.

  parent reply	other threads:[~2026-08-26  2:33 UTC|newest]

Thread overview: 4+ 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 [this message]
2026-08-26  3:55 ` 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-221142-208809-cvqCzywdgA@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