From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220033] xhci: Compliance Issue - avg_trb_len not set for EP0 during Address Device Command
Date: Wed, 07 May 2025 10:21:08 +0000 [thread overview]
Message-ID: <bug-220033-208809-GgWZyHpuEE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220033-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220033
Mathias Nyman (mathias.nyman@linux.intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mathias.nyman@linux.intel.c
| |om
--- Comment #2 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
This is up for interpretation, spec is ambiguous
xhci 1.2 Section 6.2.3.1 "Address Device Command usage" does not mention
Average TRB Length at all.
But section 4.8.2 "Endpoint Context Initialization"
states that: "All fields of an Input Endpoint Context data structure (including
the Reserved fields) shall be initialized to ‘0’ with the following exceptions:
4.8.2.1 Default Control Endpoint 0
- Max Packet Size
- CErr
- TR Dequeue Pointer
- Dequeue Cycle State (DCS)
According to it the Average TRB Length should be initialized to 0
I don't object to setting the Average TRB Length earlier, especially if it
solves device enumeration issues for some xHCI vendor. We do need to make
sure it doesn't brake enumeration for other vendors.
Can you submit a patch to linux-usb mailing list for this?
--
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:[~2025-05-07 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 13:31 [Bug 220033] New: xhci: Compliance Issue - avg_trb_len not set for EP0 during Address Device Command bugzilla-daemon
2025-05-06 14:37 ` [Bug 220033] " bugzilla-daemon
2025-05-07 10:21 ` bugzilla-daemon [this message]
2025-05-07 19:58 ` bugzilla-daemon
2025-05-13 9:17 ` 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-220033-208809-GgWZyHpuEE@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