Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-25 Thread Matthijs Kooijman
Hi Paul, Furthermore, I wonder about how this scheduler works exactly. What I see is: - the number usecs needed for a single transfer in a periodic qh is calculated - When the qh is scheduled, the first of the 8 microframes with enough usecs available is picked for this qh

RE: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-24 Thread Paul Zimmerman
From: Greg KH [mailto:gre...@linuxfoundation.org] Sent: Tuesday, July 23, 2013 2:59 PM On Wed, Jul 17, 2013 at 12:35:46PM -0700, Paul Zimmerman wrote: The transfer scheduler in the dwc2 driver is pretty basic, not to mention buggy. It works fairly well with just a couple of devices

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-23 Thread Greg KH
On Wed, Jul 17, 2013 at 12:35:46PM -0700, Paul Zimmerman wrote: The transfer scheduler in the dwc2 driver is pretty basic, not to mention buggy. It works fairly well with just a couple of devices plugged in, but if you add, say, multiple devices with periodic endpoints, the scheduler breaks

RE: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread Paul Zimmerman
From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Gordon Hollingworth Sent: Wednesday, July 17, 2013 11:00 PM I'd suggest just adding a Raspberry Pi Foundation copyright. Is that OK or do you need names for SOB? Ah yes, thanks for reminding me.

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread Matthijs Kooijman
Hi Paul, The transfer scheduler in the dwc2 driver is pretty basic, not to mention buggy. It works fairly well with just a couple of devices plugged in, but if you add, say, multiple devices with periodic endpoints, the scheduler breaks down and can't even enumerate all the devices. This

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread gre...@linuxfoundation.org
On Thu, Jul 18, 2013 at 04:45:55PM +, Paul Zimmerman wrote: From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Gordon Hollingworth Sent: Wednesday, July 17, 2013 11:00 PM I'd suggest just adding a Raspberry Pi Foundation copyright. Is

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread Stephen Warren
On 07/18/2013 10:45 AM, Paul Zimmerman wrote: From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Gordon Hollingworth Sent: Wednesday, July 17, 2013 11:00 PM I'd suggest just adding a Raspberry Pi Foundation copyright. Is that OK or do you need names

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread gre...@linuxfoundation.org
On Thu, Jul 18, 2013 at 11:34:47AM -0600, Stephen Warren wrote: On 07/18/2013 10:45 AM, Paul Zimmerman wrote: From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Gordon Hollingworth Sent: Wednesday, July 17, 2013 11:00 PM I'd suggest just adding

RE: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread Paul Zimmerman
From: Matthijs Kooijman [mailto:matth...@stdin.nl] Sent: Thursday, July 18, 2013 10:19 AM This seems related to a patch I made last year for the dwc_otg driver. On RT3052, we only have 4 host channels, so it was easy to run out of them using a 3G stick and a hub. The 3G sticks hog up 2 host

Re: [PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-18 Thread Gordon Hollingworth
I'd suggest just adding a Raspberry Pi Foundation copyright. Is that OK or do you need names for SOB? Gordon -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH] staging: dwc2: add microframe scheduler from downstream Pi kernel

2013-07-17 Thread Paul Zimmerman
The transfer scheduler in the dwc2 driver is pretty basic, not to mention buggy. It works fairly well with just a couple of devices plugged in, but if you add, say, multiple devices with periodic endpoints, the scheduler breaks down and can't even enumerate all the devices. To fix this, import