From: Kuninori Morimoto
Current usbhs gadget driver didn't complete STATUS stage after receiving.
It wasn't problem for us before, because some USB class doesn't use
DATA OUT stage in control transfer.
But, it is required on some device.
Signed-off-by: Yoshihiro Shimoda
Signed-off-by: Kuninori
From: Aleksander Morgado
Date: Wed, 28 May 2014 21:05:03 +0200
> Signed-off-by: Aleksander Morgado
Applied, thanks.
--
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 http://vger.kernel.org/majord
On 02.06.2014 03:38, Greg KH wrote:
>> Yes but... I should have avoided the term "GPIO".> No, you used the right
term :)
Sorry for using the right term :)
> No, I am not going to add custom ioctls to a single driver for this.
I did neither request nor expect that - did it sound that way?
> It
On Mon, Jun 02, 2014 at 02:57:39AM +0200, Philipp Hachtmann wrote:
> On 01.06.2014 04:31, Greg KH wrote:
> >As they are GPIO pins on this device, it should be the subsystem that
> >controls it. That way, userspace programs that are used to talk to a
> >GPIO device will "just work", and not have to
On 01.06.2014 04:31, Greg KH wrote:
As they are GPIO pins on this device, it should be the subsystem that
controls it. That way, userspace programs that are used to talk to a
GPIO device will "just work", and not have to be customized just for
this specific device and sysfs file.
So please us
Simon Gornall writes:
>
> Hi there,
>
> I'm in the process of designing a VME=>USB interface, and I wanted to use
the FT232H, but according to FTDI,
> the throughput on Linux is only ~9MBytes/sec using current kernels. In
the past, it was ~40MBytes/sec.
> Sadly my Arm board is delivered runni
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions. Also, a label is done away with and err2 and err3 renamed.
The following Coccinelle semantic patch was used for making the change:
@platform@
On Sun, 1 Jun 2014, Greg KH wrote:
> > It doesn't look to me like a crash. It looks more like the driver is
> > missing.
>
> Doh, I had based my kernel config on my desktop, and it didn't have the
> hid multitouch driver enabled.
>
> Turning that on and, wow, it works! Thanks for pointing out
On Sun, Jun 01, 2014 at 11:32:17AM +0200, Johan Hovold wrote:
> Remove the remaining two obsolete usb-serial subdriver entries from
> MAINTAINERS, which were missed in the recent purge by commit
> f896b7968b62 ("USB: Maintainers change for usb serial drivers").
>
> Signed-off-by: Johan Hovold
> -
On Sun, Jun 01, 2014 at 12:21:55PM -0400, Alan Stern wrote:
> On Sun, 1 Jun 2014, Bjørn Mork wrote:
>
> > Greg KH writes:
> >
> > > Ok, here's the dump for when the device keeps disconnecting itself from
> > > the bus (no call to check_highspeed() anymore).
> > >
> > > Things go better, but then
On Sun, 1 Jun 2014, Bjørn Mork wrote:
> Greg KH writes:
>
> > Ok, here's the dump for when the device keeps disconnecting itself from
> > the bus (no call to check_highspeed() anymore).
> >
> > Things go better, but then the device just goes quiet, and resets. Any
> > ideas? I'll dig further t
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/usb/musb/musb_host.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dr
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/usb/class/usbtmc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driv
Greg KH writes:
> Ok, here's the dump for when the device keeps disconnecting itself from
> the bus (no call to check_highspeed() anymore).
>
> Things go better, but then the device just goes quiet, and resets. Any
> ideas? I'll dig further this evening...
>
> 8800d906a0c0 2610372685 S Ci:2
The device which identifies itself as a "USB Keykoard" (no typo) with
VID:PID 1a2c:0023 does not seem to be handling the reports initialization
very well. This results in a "usb_submit_urb(ctrl) failed: -1" message
from the kernel when connected, and a delay before its initialization.
This patc
Remove the remaining two obsolete usb-serial subdriver entries from
MAINTAINERS, which were missed in the recent purge by commit
f896b7968b62 ("USB: Maintainers change for usb serial drivers").
Signed-off-by: Johan Hovold
---
MAINTAINERS | 12
1 file changed, 12 deletions(-)
diff -
On Sat, May 31, 2014 at 01:03:00PM -0300, Peter Senna Tschudin wrote:
> This patch remove the function klsi_105_tiocmset which was only
> returning -EINVAL. It also removes the function prototype and
> the .tiocmset entry in the struct usb_serial_driver.
>
> Verified by compilation only.
>
> Sign
17 matches
Mail list logo
