public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Daniel Dev <daniel.dev@noex.uk>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [BUG] ucsi_acpi: Fails to bind on USBC000 devices, version=0 in NVS blocks probe
Date: Mon, 27 Apr 2026 12:09:24 +0300	[thread overview]
Message-ID: <ae8nxNSEGd2hGh5T@kuha> (raw)
In-Reply-To: <b1Wn_eFvTFShGbd970WWl4CWhge_6P2x7Wb6rab3QHNlE4OJ4p__O-QN3B6I-308ftr5oV5Zr7vywA0vdvmtNw6E0YJnVM2ek_5DcFnkXB0=@noex.uk>

Hi Daniel,

On Tue, Apr 21, 2026 at 11:15:56AM +0000, Daniel Dev wrote:
> Hello everyone,
> 
> I am reporting two related issues in ucsi_acpi that prevent it from binding on Lenovo ThinkPad T14 Gen 2a (AMD) platforms. The result is that /sys/class/typec/ is empty and USB-C display hotplug is non-functional unless a manual workaround is applied.
> 
> Hardware:
> - Machine: Lenovo ThinkPad T14 Gen 2a (20XLS10M00)
> - CPU: AMD Ryzen 7 PRO 5850U
> - Kernel: 6.19.12-200.fc43.x86_64 (Reproduced on 6.19.12, 6.19.9, and 6.18.19)
> - Distros tested: Fedora 43, CachyOS (Arch-based), Arch and Kubuntu (Debian-based)
> 
> ---
> 
> ### Bug 1: HID Mismatch (USBC000 vs PNP0CA0)
> The ACPI device uses "USBC000" as its primary HID, with "PNP0CA0" as a Compatible ID (CID).
> ```bash
> $ cat /sys/bus/platform/devices/USBC000:00/modalias
> acpi:USBC000:PNP0CA0:
> ```
> Because ucsi_acpi only matches on PNP0CA0, the ACPI bus does not automatically bind the driver. Adding USBC000 to the acpi_device_id table is required for automatic discovery on these platforms.

This sounds really odd? Why would this become a problem now, and not
before?

I'll see if I can reproduce this.

> ---
> 
> ### Bug 2: UCSI NVS Version = 0x0000 blocks probe
> Even when forced to bind (via driver_override), the probe fails because the BIOS does not populate the VERSION field in the UCSI ACPI NVS region at runtime.
> 
> Actual probe failure log:
> ```text
> Apr 21 11:29:37 fedora kernel: platform USBC000:00: bus: 'platform': __driver_probe_device: matched device with driver ucsi_acpi
> Apr 21 11:29:37 fedora kernel: platform USBC000:00: bus: 'platform': really_probe: probing driver ucsi_acpi with device
> Apr 21 11:29:39 fedora kernel: ucsi_acpi USBC000:00: probe with driver ucsi_acpi rejects match -19
> ```
> 
> Actual Raw NVS Dump (from UCSI region 0xCBC37000):
> ```text
> Apr 21 11:41:28 fedora kernel: ucsi_peek: version=0x0000 cci=0x00000002
> Apr 21 11:41:28 fedora kernel: ucsi_peek: raw NVS dump:
>                                  +00: 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00
>                                  +10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>                                  +20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ```

Again with the missing version. Please contact Lenovo. This is a bug
in their firmware. The version field must supply the actual ucsi
version.

thanks,

-- 
heikki

      reply	other threads:[~2026-04-27  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 11:15 [BUG] ucsi_acpi: Fails to bind on USBC000 devices, version=0 in NVS blocks probe Daniel Dev
2026-04-27  9:09 ` Heikki Krogerus [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=ae8nxNSEGd2hGh5T@kuha \
    --to=heikki.krogerus@linux.intel.com \
    --cc=daniel.dev@noex.uk \
    --cc=gregkh@linuxfoundation.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