From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] usb: devio: update max count of DPs per interval for ISOC
Date: Fri, 28 Dec 2018 11:51:48 +0100 [thread overview]
Message-ID: <20181228105148.GA22073@kroah.com> (raw)
In-Reply-To: <1545992864-9530-1-git-send-email-chunfeng.yun@mediatek.com>
On Fri, Dec 28, 2018 at 06:27:44PM +0800, Chunfeng Yun wrote:
> The host shall be able to accept and send up to 96 DPs for
> devices operating at Gen 2 speed.
Why? What is this keeping from working properly today?
I need a much better changelog text here in order to be able to accept
this patch.
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> drivers/usb/core/devio.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
> index a75bc0b8a50f..82c16210e34c 100644
> --- a/drivers/usb/core/devio.c
> +++ b/drivers/usb/core/devio.c
> @@ -1564,12 +1564,10 @@ static int proc_do_submiturb(struct usb_dev_state *ps, struct usbdevfs_urb *uurb
> }
> for (totlen = u = 0; u < number_of_packets; u++) {
> /*
> - * arbitrary limit need for USB 3.0
> - * bMaxBurst (0~15 allowed, 1~16 packets)
> - * bmAttributes (bit 1:0, mult 0~2, 1~3 packets)
> - * sizemax: 1024 * 16 * 3 = 49152
> + * arbitrary limit need for USB 3.1 Gen2
> + * sizemax: 96 DPs at SSP, 96 * 1024 = 98304
> */
> - if (isopkt[u].length > 49152) {
> + if (isopkt[u].length > 98304) {
Are we going to have to keep bumping this up as speeds get faster and
faster?
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-28 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 10:27 [PATCH] usb: devio: update max count of DPs per interval for ISOC Chunfeng Yun
2018-12-28 10:51 ` Greg Kroah-Hartman [this message]
2018-12-29 2:48 ` Chunfeng Yun
2018-12-29 12:49 ` Greg Kroah-Hartman
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=20181228105148.GA22073@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@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).