From: Greg KH <gregkh@linuxfoundation.org>
To: Raju Rangoju <Raju.Rangoju@amd.com>
Cc: linux-usb@vger.kernel.org, mathias.nyman@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: xhci: quirk for data loss in ISOC transfers
Date: Tue, 12 Nov 2024 13:24:53 +0100 [thread overview]
Message-ID: <2024111226-spender-saturate-dc6e@gregkh> (raw)
In-Reply-To: <20241112122104.120633-1-Raju.Rangoju@amd.com>
On Tue, Nov 12, 2024 at 05:51:04PM +0530, Raju Rangoju wrote:
> During the High-Speed Isochronous Audio transfers, xHCI
> controller on certain AMD platforms experiences momentary data
> loss. This results in Missed Service Errors (MSE) being
> generated by the xHCI.
>
> The root cause of the MSE is attributed to the ISOC OUT endpoint
> being omitted from scheduling. This can happen either when an IN
> endpoint with a 64ms service interval is pre-scheduled prior to
> the ISOC OUT endpoint or when the interval of the ISOC OUT
> endpoint is shorter than that of the IN endpoint. Consequently,
> the OUT service is neglected when an IN endpoint with a service
> interval exceeding 32ms is scheduled concurrently (every 64ms in
> this scenario).
>
> This issue is particularly seen on certain older AMD platforms.
> To mitigate this problem, it is recommended to adjust the service
> interval of the IN endpoint to not exceed 32ms (interval 8). This
> adjustment ensures that the OUT endpoint will not be bypassed,
> even if a smaller interval value is utilized.
>
> Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
You don't want this backported to any older kernels? Why not?
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-12 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 12:21 [PATCH v2] usb: xhci: quirk for data loss in ISOC transfers Raju Rangoju
2024-11-12 12:24 ` Greg KH [this message]
2024-11-12 13:32 ` Rangoju, Raju
2024-11-13 6:05 ` Greg KH
2024-11-13 6:11 ` Rangoju, Raju
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=2024111226-spender-saturate-dc6e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Raju.Rangoju@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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 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).