All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221716] New: JHL9580 Barlow Ridge TB5: host_reset timeout, PCIe tunneling broken
Date: Fri, 03 Jul 2026 04:00:35 +0000	[thread overview]
Message-ID: <bug-221716-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221716

            Bug ID: 221716
           Summary: JHL9580 Barlow Ridge TB5: host_reset timeout, PCIe
                    tunneling broken
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: liqysir@qq.com
        Regression: No

JHL9580 Barlow Ridge (8086:5780/5781) Thunderbolt 5 / USB4 v2 host
    controller has incomplete Linux support through v7.2-rc1.

    Symptoms:
    - host_reset times out (REG_RESET HRR stays 0x01, even with 5000ms timeout)
    - REG_FW_STS is read-only (0x00000000), ICM firmware cannot start
    - USB3 tunneling works (XHCI pass-through), PCIe tunneling broken
    - eGPU GPU never appears in lspci

    Tested: kernel 7.0.0-22, 7.0.0-27, 7.1.2 — all same issue.
    Hardware: MSI MS-15M3 (Arrow Lake-HX Ultra 9 275HX) + GIGABYTE AORUS
RTX5090 AI BOX.

    Root causes identified:
    1. get_upstream_port() in icm.c does not recognize 0x5780
    2. icm_probe() has no case for 0x5781
    3. icm_firmware_reset() → pcie2cio_write() times out on Barlow Ridge

    Patch attempted (adds 0x5780/0x5781 to icm.c) — icm_probe succeeds but
    CIO reset times out. Correct Barlow Ridge CIO reset sequence needed.

    Full diagnosis email sent to linux-usb@vger.kernel.org.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2026-07-03  4:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-221716-208809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.