public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jack Pham <jackp@codeaurora.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable-5.14 2/2] usb: gadget: f_uac2: Populate SS descriptors' wBytesPerInterval
Date: Mon, 27 Sep 2021 18:56:43 +0200	[thread overview]
Message-ID: <YVH3yzBL8+HE+gtd@kroah.com> (raw)
In-Reply-To: <20210927161253.10977-2-jackp@codeaurora.org>

On Mon, Sep 27, 2021 at 09:12:53AM -0700, Jack Pham wrote:
> commit f0e8a206a2a53a919e1709c654cb65d519f7befb upstream.
> 
> For Isochronous endpoints, the SS companion descriptor's
> wBytesPerInterval field is required to reserve bus time in order
> to transmit the required payload during the service interval.
> If left at 0, the UAC2 function is unable to transact data on its
> playback or capture endpoints in SuperSpeed mode.
> 
> Since f_uac2 currently does not support any bursting this value can
> be exactly equal to the calculated wMaxPacketSize.
> 
> Tested with Windows 10 as a host.
> 
> Fixes: f8cb3d556be3 ("usb: f_uac2: adds support for SS and SSP")
> Cc: stable <stable@vger.kernel.org>
> Signed-off-by: Jack Pham <jackp@codeaurora.org>
> Link: https://lore.kernel.org/r/20210909174811.12534-3-jackp@codeaurora.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> [jackp: Backport to 5.14 with minor conflict resolution]

Both now queued up, thanks.

greg k-h

      reply	other threads:[~2021-09-27 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 16:12 [PATCH stable-5.14 1/2] usb: gadget: f_uac2: Add missing companion descriptor for feedback EP Jack Pham
2021-09-27 16:12 ` [PATCH stable-5.14 2/2] usb: gadget: f_uac2: Populate SS descriptors' wBytesPerInterval Jack Pham
2021-09-27 16:56   ` Greg Kroah-Hartman [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=YVH3yzBL8+HE+gtd@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jackp@codeaurora.org \
    --cc=stable@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