From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rong Zhang <i@rong.moe>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
linux-usb@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: acpi: Disable on devices with broken firmware
Date: Mon, 11 May 2026 20:25:04 +0200 [thread overview]
Message-ID: <2026051146-husked-ladybug-0c9f@gregkh> (raw)
In-Reply-To: <20260512-ucsi-acpi-broken-devices-v1-1-0f8cd90c35b5@rong.moe>
On Tue, May 12, 2026 at 01:59:34AM +0800, Rong Zhang wrote:
> Some Lenovo devices have broken firmware, which reads/writes half-valid-
> half-garbage values.
How does this work with this firmware on other operating systems? What
is the odds of fixing the firmware?
> Given that everything is broken, disable ucsi_acpi on these devices. The
> impact of disabling it is minimal, as Lenovo laptops usually have most
> USCI commands more or less stubbed, and the EC can always handles USB-C
> events on its own.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221065#c33
> Signed-off-by: Rong Zhang <i@rong.moe>
> ---
> drivers/usb/typec/ucsi/ucsi_acpi.c | 91 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi_acpi.c b/drivers/usb/typec/ucsi/ucsi_acpi.c
> index 6b92f296e985..7632b441d401 100644
> --- a/drivers/usb/typec/ucsi/ucsi_acpi.c
> +++ b/drivers/usb/typec/ucsi/ucsi_acpi.c
> @@ -155,6 +155,91 @@ static const struct dmi_system_id ucsi_acpi_quirks[] = {
> { }
> };
>
> +static const struct dmi_system_id ucsi_acpi_broken_devices[] = {
> + /* Firmware reads/writes half-valid-half-garbage values. */
> +
> + /* BIOS: P1CN??WW */
> + {
> + .ident = "Lenovo IdeaPad 5 2-in-1 14AHP9",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83DR"),
> + },
> + },
> + {
> + .ident = "Lenovo IdeaPad 5 2-in-1 16AHP9",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83DS"),
> + },
> + },
> +
> + /* BIOS: R0CN??WW */
> + {
> + .ident = "Lenovo IdeaPad Slim 5 14AKP10",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83NJ"),
> + },
> + },
> + {
> + .ident = "Lenovo IdeaPad Slim 5 14AKP10",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83HX"),
> + },
> + },
> + {
> + .ident = "Lenovo IdeaPad Slim 5 16AKP10",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83HY"),
> + },
> + },
> +
> + /* BIOS: QXCN??WW */
> + {
> + .ident = "Lenovo Yoga 7 2-in-1 14AKP10",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83JR"),
> + },
> + },
> + {
> + .ident = "Lenovo Yoga 7 2-in-1 16AKP10",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83JU"),
> + },
> + },
> +
> + /* BIOS: LNCN??WW */
> + {
> + .ident = "Lenovo Yoga Pro 7 14ARP8",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83AU"),
> + },
> + },
> + {
> + .ident = "Lenovo Slim Pro 7 14ARP8",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83AX"),
> + },
> + },
> +
> + /* BIOS: PSCN??WW */
> + {
> + .ident = "Lenovo Yoga Pro 7 14ASP9",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "83HN"),
> + },
> + },
> + { }
> +};
That is a lot of devices to exclude, are you sure that none of them will
ever work properly?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-11 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:59 [PATCH] usb: typec: ucsi: acpi: Disable on devices with broken firmware Rong Zhang
2026-05-11 18:25 ` Greg Kroah-Hartman [this message]
2026-05-11 19:12 ` Rong Zhang
2026-05-11 23:11 ` Mark Pearson
2026-05-12 12:46 ` Rong Zhang
2026-05-12 18:28 ` Mark Pearson
2026-05-12 19:16 ` Rong Zhang
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=2026051146-husked-ladybug-0c9f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=i@rong.moe \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=platform-driver-x86@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