From: Greg KH <gregkh@linuxfoundation.org>
To: 3090101217@zju.edu.cn
Cc: balbi@kernel.org, ruslan.bilovol@gmail.com,
pavel.hofman@ivitera.com, jbrunet@baylibre.com,
jackp@codeaurora.org, colin.king@intel.com, pawell@cadence.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Jing Leng <jleng@ambarella.com>
Subject: Re: [PATCH] usb: gadget: f_uac2: fix superspeed transfer
Date: Mon, 14 Feb 2022 11:36:56 +0100 [thread overview]
Message-ID: <YgowyN4thlrJw6J9@kroah.com> (raw)
In-Reply-To: <20220214032606.17227-1-3090101217@zju.edu.cn>
On Mon, Feb 14, 2022 at 11:26:06AM +0800, 3090101217@zju.edu.cn wrote:
> From: Jing Leng <jleng@ambarella.com>
>
> ss_ep_int_desc endpoint doesn't have 'SuperSpeed Endpoint
> Companion Descriptor', so we should add it.
This is not a "fix" but rather a new feature.
Why does this endpoint need this descriptor? We need a lot more
description here please.
>
> Signed-off-by: Jing Leng <jleng@ambarella.com>
> ---
> drivers/usb/gadget/function/f_uac2.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/f_uac2.c b/drivers/usb/gadget/function/f_uac2.c
> index 097a709549d6..a6fc492f9148 100644
> --- a/drivers/usb/gadget/function/f_uac2.c
> +++ b/drivers/usb/gadget/function/f_uac2.c
> @@ -282,6 +282,14 @@ static struct usb_endpoint_descriptor ss_ep_int_desc = {
> .bInterval = 4,
> };
>
> +static struct usb_ss_ep_comp_descriptor ss_ep_int_desc_comp = {
> + .bLength = sizeof(ss_ep_int_desc_comp),
> + .bDescriptorType = USB_DT_SS_ENDPOINT_COMP,
> + .bMaxBurst = 0,
> + .bmAttributes = 0,
0 is the default value if it is not defined.
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-14 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 3:26 [PATCH] usb: gadget: f_uac2: fix superspeed transfer 3090101217
2022-02-14 10:36 ` Greg KH [this message]
2022-02-14 14:32 ` [PATCH v2] " 3090101217
2022-02-14 14:48 ` Greg KH
2022-02-17 5:55 ` [PATCH v3] " 3090101217
2022-02-17 6:10 ` Jing Leng
2022-02-17 15:24 ` Greg KH
2022-02-18 9:59 ` [PATCH v4] " 3090101217
2022-07-21 0:26 ` Jack Pham
2022-07-27 12:14 ` Greg KH
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=YgowyN4thlrJw6J9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=3090101217@zju.edu.cn \
--cc=balbi@kernel.org \
--cc=colin.king@intel.com \
--cc=jackp@codeaurora.org \
--cc=jbrunet@baylibre.com \
--cc=jleng@ambarella.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel.hofman@ivitera.com \
--cc=pawell@cadence.com \
--cc=ruslan.bilovol@gmail.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).