All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Stephanie Gawroriski <xerthesquirrel@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Linux 6.18-rc6
Date: Thu, 27 Nov 2025 11:53:38 +0200	[thread overview]
Message-ID: <aSgfeHBsQI8XfWr2@kuha> (raw)
In-Reply-To: <2167318.tdWV9SEqCh@arborvitaetree>

Hi,

Wed, Nov 26, 2025 at 11:01:24AM -0500, Stephanie Gawroriski kirjoitti:
> Hi!
> 
> On Monday, 24 November 2025 04:50:03 EST Heikki Krogerus wrote:
> > I'm still trying to figure this out, but let's rule out one of my
> > concerns..
> > 
> > Can you check are the symlinks pointing to the correct USB devices
> > under /sys/class/typec ?
> > 
> > It's probable easiest with just one USB device connected to the
> > system. With one USB device connected to the system there should be
> > only one partner under /sys/class/typec (for example port0-partner),
> > so it should be easy to check if the symlink under that partner
> > device is pointing to the correct USB device.
> > 
> >         % ls -la /sys/class/typec/port<x>-partner/
> > 
> > You should see a symlink to an USB device under it. Can you check if
> > it's the correct USB device?
> > 
> > If it's not the correct USB device, then the ACPI table may have wrong
> > _PLD (Physical Location of Device) objects for these USB port or USB
> > Type-C connector device nodes. The code uses the _PLD to link the
> > correct USB port to the USB Type-C connector.
> > 
> > thanks,
> 
> The USB-C cable is plugged into the connector that is furthest to the back of 
> the device. Bus 2 and Bus 3 are connected to the same port, the ethernet 
> controller is connected to the dock, so I am guessing that it is using the 
> USB-only interface of the USB-C port, not sure why it would be not under Bus 
> 3?
> 
> These are the outputs along with the USB and PCI tree:
> 
> stephanie@arborvitaetree:~$ ls -la /sys/class/typec/port1-partner/
> total 0
> drwxr-xr-x 4 root root    0 Nov 26 10:30 .
> drwxr-xr-x 8 root root    0 Nov 24 15:14 ..
> lrwxrwxrwx 1 root root    0 Nov 26 10:30 2-3 -> ../../../../../
> pci0000:00/0000:00:0d.0/usb2/2-3
> lrwxrwxrwx 1 root root    0 Nov 26 10:30 3-3 -> ../../../../../
> pci0000:00/0000:00:14.0/usb3/3-3

These look correct to me, which is a relief.

At this point can I ask you to report this in bugzilla.kernel.org?

thanks,

> -r--r--r-- 1 root root 4096 Nov 26 10:30 accessory_mode
> lrwxrwxrwx 1 root root    0 Nov 25 23:42 device -> ../../port1
> -r--r--r-- 1 root root 4096 Nov 26 10:30 number_of_alternate_modes
> drwxr-xr-x 5 root root    0 Nov 25 23:42 pd2
> drwxr-xr-x 2 root root    0 Nov 26 10:29 power
> lrwxrwxrwx 1 root root    0 Nov 25 23:42 subsystem -> ../../../../../../class/
> typec
> -r--r--r-- 1 root root 4096 Nov 26 10:30 supports_usb_power_delivery
> -rw-r--r-- 1 root root 4096 Nov 25 23:42 uevent
> -r--r--r-- 1 root root 4096 Nov 26 10:30 usb_mode
> lrwxrwxrwx 1 root root    0 Nov 26 10:30 usb_power_delivery -> pd2
> -r--r--r-- 1 root root 4096 Nov 26 10:30 usb_power_delivery_revision
> 
> stephanie@arborvitaetree:/sys/class/typec$ lsusb -tv
> /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
>     ID 1d6b:0002 Linux Foundation 2.0 root hub
> /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 20000M/x2
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
>     |__ Port 003: Dev 005, If 0, Class=Hub, Driver=hub/4p, 10000M
>         ID 8087:0b40 Intel Corp. 
>         |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 10000M
>             ID 2109:0822 VIA Labs, Inc. 
>             |__ Port 002: Dev 007, If 0, Class=Communications, Driver=cdc_ncm, 
> 5000M
>                 ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
>             |__ Port 002: Dev 007, If 1, Class=CDC Data, Driver=cdc_ncm, 5000M
>                 ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
> /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
>     ID 1d6b:0002 Linux Foundation 2.0 root hub
>     |__ Port 003: Dev 023, If 0, Class=Hub, Driver=hub/6p, 480M
>         ID 1d5c:5801 Fresco Logic 
>         |__ Port 001: Dev 024, If 0, Class=Billboard, Driver=[none], 1.5M
>             ID 291a:87e0  
>         |__ Port 004: Dev 025, If 0, Class=Hub, Driver=hub/4p, 480M
>             ID 2109:2822 VIA Labs, Inc. 
>             |__ Port 001: Dev 027, If 0, Class=Hub, Driver=hub/4p, 480M
>                 ID 1a40:0101 Terminus Technology Inc. Hub
>                 |__ Port 001: Dev 028, If 0, Class=Human Interface Device, 
> Driver=usbhid, 1.5M
>                     ID 17ef:608d Lenovo Optical Mouse
>                 |__ Port 002: Dev 029, If 0, Class=Human Interface Device, 
> Driver=usbhid, 12M
>                     ID 0c45:7692 Microdia 
>                 |__ Port 002: Dev 029, If 1, Class=Human Interface Device, 
> Driver=usbhid, 12M
>                     ID 0c45:7692 Microdia 
>                 |__ Port 004: Dev 030, If 0, Class=Video, Driver=uvcvideo, 
> 480M
>                     ID 17ef:4836 Lenovo 
>                 |__ Port 004: Dev 030, If 1, Class=Video, Driver=uvcvideo, 
> 480M
>                     ID 17ef:4836 Lenovo 
>                 |__ Port 004: Dev 030, If 2, Class=Audio, Driver=snd-usb-
> audio, 480M
>                     ID 17ef:4836 Lenovo 
>                 |__ Port 004: Dev 030, If 3, Class=Audio, Driver=snd-usb-
> audio, 480M
>                     ID 17ef:4836 Lenovo 
>         |__ Port 005: Dev 026, If 0, Class=Billboard, Driver=[none], 12M
>             ID 2eb9:0123  
>         |__ Port 005: Dev 026, If 1, Class=Vendor Specific Class, 
> Driver=[none], 12M
>             ID 2eb9:0123  
>     |__ Port 006: Dev 022, If 0, Class=Vendor Specific Class, Driver=[none], 
> 12M
>         ID 06cb:00fc Synaptics, Inc. Prometheus Fingerprint Reader
>     |__ Port 008: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M
>         ID 30c9:0051 Luxvisions Innotech Limited 
>     |__ Port 008: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M
>         ID 30c9:0051 Luxvisions Innotech Limited 
>     |__ Port 008: Dev 003, If 2, Class=Application Specific Interface, 
> Driver=[none], 480M
>         ID 30c9:0051 Luxvisions Innotech Limited 
>     |__ Port 010: Dev 004, If 0, Class=Wireless, Driver=btusb, 12M
>         ID 8087:0033 Intel Corp. AX211 Bluetooth
>     |__ Port 010: Dev 004, If 1, Class=Wireless, Driver=btusb, 12M
>         ID 8087:0033 Intel Corp. AX211 Bluetooth
> /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
> 
> stephanie@arborvitaetree:/sys/class/typec$ lspci -tv -nn
> -[0000:00]-+-00.0  Intel Corporation Raptor Lake-P 6p+8e cores Host Bridge/
> DRAM Controller [8086:a706]
>            +-02.0  Intel Corporation Raptor Lake-P [Iris Xe Graphics] 
> [8086:a7a0]
>            +-04.0  Intel Corporation Raptor Lake Dynamic Platform and Thermal 
> Framework Processor Participant [8086:a71d]
>            +-06.0-[04]----00.0  Sandisk Corp WD Blue SN5000 NVMe SSD (DRAM-
> less) [15b7:504a]
>            +-07.0-[20-49]--
>            +-07.2-[50-79]----00.0-[51-79]--+-00.0-[52]--
>            |                               +-01.0-[53-5f]--
>            |                               +-02.0-[60-6c]--
>            |                               +-03.0-[6d-78]--
>            |                               \-04.0-[79]--
>            +-08.0  Intel Corporation GNA Scoring Accelerator module 
> [8086:a74f]
>            +-0a.0  Intel Corporation Raptor Lake Crashlog and Telemetry 
> [8086:a77d]
>            +-0d.0  Intel Corporation Raptor Lake-P Thunderbolt 4 USB 
> Controller [8086:a71e]
>            +-0d.2  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0 
> [8086:a73e]
>            +-0d.3  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1 
> [8086:a76d]
>            +-12.0  Intel Corporation Alder Lake-P Integrated Sensor Hub 
> [8086:51fc]
>            +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host 
> Controller [8086:51ed]
>            +-14.2  Intel Corporation Alder Lake PCH Shared SRAM [8086:51ef]
>            +-14.3  Intel Corporation Raptor Lake PCH CNVi WiFi [8086:51f1]
>            +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller 
> #0 [8086:51e8]
>            +-15.1  Intel Corporation Alder Lake PCH Serial IO I2C Controller 
> #1 [8086:51e9]
>            +-16.0  Intel Corporation Alder Lake PCH HECI Controller 
> [8086:51e0]
>            +-1c.0-[08]----00.0  Intel Corporation XMM7560 LTE Advanced Pro 
> Modem [8086:7560]
>            +-1f.0  Intel Corporation Raptor Lake LPC/eSPI Controller 
> [8086:519d]
>            +-1f.3  Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca]
>            +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller 
> [8086:51a3]
>            \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller 
> [8086:51a4]
> 
> stephanie@arborvitaetree:/sys/class/typec$ ls -w 1 port0/
> data_role
> device
> firmware_node
> physical_location
> port0.0
> port0.1
> port0.2
> power
> power_operation_mode
> power_role
> preferred_role
> subsystem
> supported_accessory_modes
> uevent
> usb2-port1
> usb3-port1
> usb4_port1
> usb_capability
> usb_power_delivery
> usb_power_delivery_revision
> usb_typec_revision
> vconn_source
> waiting_for_supplier
> 
> stephanie@arborvitaetree:/sys/class/typec$ ls -w 1 port1/
> data_role
> device
> firmware_node
> physical_location
> port1.0
> port1.1
> port1.2
> port1-partner
> power
> power_operation_mode
> power_role
> preferred_role
> subsystem
> supported_accessory_modes
> uevent
> usb2-port3
> usb3-port3
> usb4_port7
> usb_capability
> usb_power_delivery
> usb_power_delivery_revision
> usb_typec_revision
> vconn_source
> waiting_for_supplier
> 
> 
> 
> 
> 

-- 
heikki

      reply	other threads:[~2025-11-27  9:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 22:42 Linux 6.18-rc6 Linus Torvalds
2025-11-17  8:20 ` David Wang
2025-11-17 10:33   ` Linus Torvalds
2025-11-17 12:56     ` David Wang
2025-11-17 13:30       ` David Hildenbrand (Red Hat)
2025-11-17 13:45         ` David Wang
2025-11-17 14:08           ` David Hildenbrand (Red Hat)
2025-11-17 15:28             ` David Wang
2025-11-17 16:59             ` Xi Ruoyao
2025-11-17 21:19               ` Joan Bruguera Micó
2025-11-17 17:28             ` Linus Torvalds
2025-11-17 17:53               ` David Hildenbrand (Red Hat)
2025-11-17 17:59                 ` Linus Torvalds
2025-11-17 18:24                   ` David Hildenbrand (Red Hat)
2025-11-17 19:17                     ` David Hildenbrand (Red Hat)
2025-11-18  1:10                       ` Linus Torvalds
2025-11-18  4:13                         ` David Wang
2025-11-18 13:55                           ` David Wang
2025-11-18 14:12                             ` David Hildenbrand (Red Hat)
2025-11-18 14:33                               ` David Wang
2025-11-18 14:44                               ` Carlos Llamas
2025-11-18 14:51                                 ` David Hildenbrand (Red Hat)
2025-11-18 14:53                                   ` Carlos Llamas
2025-11-18 15:09                                   ` David Wang
2025-11-18  7:28                         ` David Hildenbrand (Red Hat)
2025-11-18 16:49                           ` Linus Torvalds
2025-11-19 15:42                             ` Catalin Marinas
2025-11-18  3:59             ` Carlos Llamas
2025-11-17 16:42       ` Linus Torvalds
2025-11-17 18:13 ` Guenter Roeck
2025-11-18 17:23 ` Stephanie Gawroriski
2025-11-18 18:01   ` Linus Torvalds
2025-11-18 20:18     ` Stephanie Gawroriski
2025-11-19  9:08       ` Heikki Krogerus
2025-11-19 14:18         ` Stephanie Gawroriski
2025-11-19 15:04         ` Stephanie Gawroriski
2025-11-24  9:50           ` Heikki Krogerus
2025-11-26 16:01             ` Stephanie Gawroriski
2025-11-27  9:53               ` 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=aSgfeHBsQI8XfWr2@kuha \
    --to=heikki.krogerus@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xerthesquirrel@gmail.com \
    /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.