All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Wade Berrier <wberrier@gmail.com>,
	Sean Young <sean@mess.org>, <linux-media@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] USB: change bInterval default to 10 ms
Date: Fri, 16 Sep 2016 12:02:06 -0300	[thread overview]
Message-ID: <20160916120206.4fa95a58@vento.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1609161017070.1657-100000@iolanthe.rowland.org>

Em Fri, 16 Sep 2016 10:24:26 -0400 (EDT)
Alan Stern <stern@rowland.harvard.edu> escreveu:

> Some full-speed mceusb infrared transceivers contain invalid endpoint
> descriptors for their interrupt endpoints, with bInterval set to 0.
> In the past they have worked out okay with the mceusb driver, because
> the driver sets the bInterval field in the descriptor to 1,
> overwriting whatever value may have been there before.  However, this
> approach was never sanctioned by the USB core, and in fact it does not
> work with xHCI controllers, because they use the bInterval value that
> was present when the configuration was installed.
> 
> Currently usbcore uses 32 ms as the default interval if the value in
> the endpoint descriptor is invalid.  It turns out that these IR
> transceivers don't work properly unless the interval is set to 10 ms
> or below.  To work around this mceusb problem, this patch changes the
> endpoint-descriptor parsing routine, making the default interval value
> be 10 ms rather than 32 ms.
> 
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> Tested-by: Wade Berrier <wberrier@gmail.com>
> CC: <stable@vger.kernel.org>

Acked-by: Mauro Carvalho Chehab <m.chehab@s-opensource.com>

> 
> ---
> 
> 
> [as1812]
> 
> 
>  drivers/usb/core/config.c |   28 +++++++++++++++++-----------
>  1 file changed, 17 insertions(+), 11 deletions(-)
> 
> Index: usb-4.x/drivers/usb/core/config.c
> ===================================================================
> --- usb-4.x.orig/drivers/usb/core/config.c
> +++ usb-4.x/drivers/usb/core/config.c
> @@ -240,8 +240,10 @@ static int usb_parse_endpoint(struct dev
>  	memcpy(&endpoint->desc, d, n);
>  	INIT_LIST_HEAD(&endpoint->urb_list);
>  
> -	/* Fix up bInterval values outside the legal range. Use 32 ms if no
> -	 * proper value can be guessed. */
> +	/*
> +	 * Fix up bInterval values outside the legal range.
> +	 * Use 10 or 8 ms if no proper value can be guessed.
> +	 */
>  	i = 0;		/* i = min, j = max, n = default */
>  	j = 255;
>  	if (usb_endpoint_xfer_int(d)) {
> @@ -250,13 +252,15 @@ static int usb_parse_endpoint(struct dev
>  		case USB_SPEED_SUPER_PLUS:
>  		case USB_SPEED_SUPER:
>  		case USB_SPEED_HIGH:
> -			/* Many device manufacturers are using full-speed
> +			/*
> +			 * Many device manufacturers are using full-speed
>  			 * bInterval values in high-speed interrupt endpoint
> -			 * descriptors. Try to fix those and fall back to a
> -			 * 32 ms default value otherwise. */
> +			 * descriptors. Try to fix those and fall back to an
> +			 * 8-ms default value otherwise.
> +			 */
>  			n = fls(d->bInterval*8);
>  			if (n == 0)
> -				n = 9;	/* 32 ms = 2^(9-1) uframes */
> +				n = 7;	/* 8 ms = 2^(7-1) uframes */
>  			j = 16;
>  
>  			/*
> @@ -271,10 +275,12 @@ static int usb_parse_endpoint(struct dev
>  			}
>  			break;
>  		default:		/* USB_SPEED_FULL or _LOW */
> -			/* For low-speed, 10 ms is the official minimum.
> +			/*
> +			 * For low-speed, 10 ms is the official minimum.
>  			 * But some "overclocked" devices might want faster
> -			 * polling so we'll allow it. */
> -			n = 32;
> +			 * polling so we'll allow it.
> +			 */
> +			n = 10;
>  			break;
>  		}
>  	} else if (usb_endpoint_xfer_isoc(d)) {
> @@ -282,10 +288,10 @@ static int usb_parse_endpoint(struct dev
>  		j = 16;
>  		switch (to_usb_device(ddev)->speed) {
>  		case USB_SPEED_HIGH:
> -			n = 9;		/* 32 ms = 2^(9-1) uframes */
> +			n = 7;		/* 8 ms = 2^(7-1) uframes */
>  			break;
>  		default:		/* USB_SPEED_FULL */
> -			n = 6;		/* 32 ms = 2^(6-1) frames */
> +			n = 4;		/* 8 ms = 2^(4-1) frames */
>  			break;
>  		}
>  	}
> 



Thanks,
Mauro

  reply	other threads:[~2016-09-16 15:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25  4:06 mceusb xhci issue? Wade Berrier
2016-04-25 17:15 ` Sean Young
2016-04-26  3:16   ` Wade Berrier
2016-04-27 20:07     ` Sean Young
2016-05-15  2:29       ` Wade Berrier
2016-05-18 14:52         ` Wade Berrier
2016-07-09 14:59           ` Mauro Carvalho Chehab
2016-07-12 15:52             ` Alan Stern
2016-08-11 20:18               ` Alan Stern
2016-09-10 19:58                 ` Wade Berrier
2016-09-15 19:13                   ` Alan Stern
2016-09-15 22:48                     ` Wade Berrier
2016-09-16 14:24                       ` [PATCH] USB: change bInterval default to 10 ms Alan Stern
2016-09-16 15:02                         ` Mauro Carvalho Chehab [this message]
2016-09-16 14:25                       ` mceusb xhci issue? Alan Stern
2016-09-16 15:03                         ` Mauro Carvalho Chehab
2016-09-15 19:37               ` Alan Stern

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=20160916120206.4fa95a58@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=greg@kroah.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sean@mess.org \
    --cc=stern@rowland.harvard.edu \
    --cc=wberrier@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 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.