On Fri, Aug 21, 2015 at 10:16:30AM -0400, Alan Stern wrote:
> On Fri, 21 Aug 2015, Peter Chen wrote:
>
> > Thanks, Alan and Felipe.
> >
> > My problem should be the chipidea udc driver does not support functional
> > stall well, it fixes the handling between functional and protocol stall.
> >
>
> -Original Message-
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, August 20, 2015 7:40 PM
> To: Mehresh Ramneek-B31383
> Cc: linux-ker...@vger.kernel.org; ba...@ti.com;
> gre...@linuxfoundation.org; linux-usb@vger.kernel.org; Li Yang-Leo-R58472
>
> Subject: RE
On Sun, 21 Jun 2015 21:44:30 +0200
, Stefan Agner
wrote:
> On 2015-06-21 01:49, Peter Stuge wrote:
> > Stefan Agner wrote:
> >> libftdi requires to detach the kernel driver to get access to the device
> >
> > Control transfers ought to be possible without a detach.
>
> Good to know, thanks for
Hello Alan,
bisecting turned out to be much simpler than I was afraid of.
Here's the result:
638139eb95d2d241781330a321e88c8dafe46078 is the first bad commit
commit 638139eb95d2d241781330a321e88c8dafe46078
Author: Petr Mladek
Date: Fri Sep 19 17:32:24 2014 +0200
usb: hub: allow to process
On Mon, 2015-08-24 at 00:18 +0530, Muhammad Falak R Wani wrote:
> This patch introduces the use of function kmalloc_array(), instead
> of using kmalloc(), for allocating memory for an array and removes
> the corresponding call to kmalloc().
[]
> diff --git a/drivers/usb/core/driver.c b/drivers/usb/
This patch introduces the use of function kmalloc_array(), instead
of using kmalloc(), for allocating memory for an array and removes
the corresponding call to kmalloc().
Signed-off-by: Muhammad Falak R Wani
---
drivers/usb/core/driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
This patch fixes a coding style issue by adding parenthesis
to the sizeof operator, which is the preferred way of using it.
Signed-off-by: Muhammad Falak R Wani
---
drivers/usb/core/buffer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/core/buffer.c b/drivers/u
On Sun, 23 Aug 2015, Jonas Gorski wrote:
> Commit d445913ce0ab7f ("usb: ehci-orion: add optional PHY support")
> added support for optional phys, but devm_phy_optional_get returns
> -ENOSYS if GENERIC_PHY is not enabled.
>
> This causes probe failures, even when there are no phys specified:
>
>
Commit d445913ce0ab7f ("usb: ehci-orion: add optional PHY support")
added support for optional phys, but devm_phy_optional_get returns
-ENOSYS if GENERIC_PHY is not enabled.
This causes probe failures, even when there are no phys specified:
[1.443365] orion-ehci f1058000.usb: init f1058000.us
