From: "Rangoju, Raju" <raju.rangoju@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Wed, 13 Nov 2024 11:41:31 +0530 [thread overview]
Message-ID: <19452eb2-10e7-e90e-fdf0-19269d04e84c@amd.com> (raw)
In-Reply-To: <2024111330-crusher-alike-a88d@gregkh>
On 11/13/2024 11:35 AM, Greg KH wrote:
> On Tue, Nov 12, 2024 at 07:02:40PM +0530, Rangoju, Raju wrote:
>>
>>
>> On 11/12/2024 5:54 PM, Greg KH wrote:
>>> 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?
>>
>> Hi Greg, Yes, backporting is needed, but some of products were released back
>> in 2018, not sure of the exact commit id to quote here for backporting as
>> there were no precise commits that added this initial support in the first
>> place.
>>
>> Would you mind tagging it to all stable kernels. Let me know if the patch
>> needs to be respinned.
>
> Yes, please resend it with the proper tag, don't ask maintainers to
> hand-edit changes for you, that does not scale at all.
>
Sure, I'll re-spin with a stable tag.
> thanks,
>
> greg k-h
prev parent reply other threads:[~2024-11-13 6:11 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
2024-11-12 13:32 ` Rangoju, Raju
2024-11-13 6:05 ` Greg KH
2024-11-13 6:11 ` Rangoju, Raju [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=19452eb2-10e7-e90e-fdf0-19269d04e84c@amd.com \
--to=raju.rangoju@amd.com \
--cc=gregkh@linuxfoundation.org \
--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 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.