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: Thu, 15 Feb 2024 09:37:21 +0000 [thread overview]
Message-ID: <bug-218465-208809-ZMDr0huLuU@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 #5 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
This DELL machine has ACPI entries for USB ports that are not usable.
These ports are supported by xHCI host hardware but are not internally or
externally connected anywhere. They have _UPC (USB port capability) ACPI
objects stating they are not connectable, and _PLD (Physical Location of
Device) that just returns 0 for their group token group position.
So all unusable USB2 and USB3 ports have similar _PLD entries, which then
confuses Linux when trying to pair together USB2 and USB3 ports.
Linux could probably ignore printing any warning messages for ports that
have _PLD entries but _UPC shows they are not connectable
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-02-15 9:37 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
2024-02-12 12:16 ` bugzilla-daemon
2024-02-13 17:47 ` bugzilla-daemon
2024-02-15 9:37 ` bugzilla-daemon [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=bug-218465-208809-ZMDr0huLuU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).