From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218465] Linux warning `usb: port power management may be unreliable` on Dell XPS 13 9360
Date: Mon, 12 Feb 2024 10:44:16 +0000 [thread overview]
Message-ID: <bug-218465-208809-4wush0TSHm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218465-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218465
--- Comment #2 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
High-speed (HS) ans SuperSpeed (SS) ports are peered based on their Physical
Location Description (_PLD) object in ACPI tables.
The SSDT7 ACPI table dump shows that _PLD is created by calling a GPLD
helper method with some parameters. For High-Speed ports (HS0x) this seems
to be called with increasing port numer up to HS port 5. From port 6 onwards
all parameters are 0.
Scope (\_SB.PCI0.XHC.RHUB.HS01)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (One, One))
Scope (\_SB.PCI0.XHC.RHUB.HS02)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (One, 0x02))
...
Scope (\_SB.PCI0.XHC.RHUB.HS05)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (Zero, 0x05))
Scope (\_SB.PCI0.XHC.RHUB.HS06)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (Zero, Zero))
Scope (\_SB.PCI0.XHC.RHUB.HS07)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (Zero, Zero))
For SuperSpeed ports (SS0x) the same is true. Ports 1-
Scope (\_SB.PCI0.XHC.RHUB.SS01)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (One, One))
Scope (\_SB.PCI0.XHC.RHUB.SS02)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (One, 0x02))
Scope (\_SB.PCI0.XHC.RHUB.SS03)
Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
Return (GPLD (Zero, Zero))
Scope (\_SB.PCI0.XHC.RHUB.SS04)
Method (_UPC, 0, NotSerialized) // _UPC: USB Port Capabilities
Return (GPLD (Zero, Zero))
Basically all HS port from 6 upwards and SS ports from 3 upwards report the
same _PLD, this messes up port peering and results in the following messages
during boot:
usb usb2-port1: peered to usb1-port1
usb usb2-port2: peered to usb1-port2
usb usb2-port3: peered to usb1-port6
usb: failed to peer usb2-port4 and usb1-port6 by location (usb2-port4:none)
(usb1-port6:usb2-port3)
usb usb2-port4: failed to peer to usb1-port6 (-16)
usb: port power management may be unreliable
usb: failed to peer usb2-port5 and usb1-port6 by location (usb2-port5:none)
(usb1-port6:usb2-port3)
usb usb2-port5: failed to peer to usb1-port6 (-16)
usb: failed to peer usb2-port6 and usb1-port6 by location (usb2-port6:none)
(usb1-port6:usb2-port3)
usb usb2-port6: failed to peer to usb1-port6 (-16)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-02-12 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 9:00 [Bug 218465] New: Linux warning `usb: port power management may be unreliable` on Dell XPS 13 9360 bugzilla-daemon
2024-02-06 9:02 ` [Bug 218465] " bugzilla-daemon
2024-02-12 10:44 ` bugzilla-daemon [this message]
2024-02-12 12:16 ` bugzilla-daemon
2024-02-13 17:47 ` bugzilla-daemon
2024-02-15 9:37 ` 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-218465-208809-4wush0TSHm@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.