linux/drivers/usb/core/devio.c, branch v3.14

USB: core: correct spelling mistakes in comments and warning

2014-01-08T00:17:40Z

Signed-off-by: Rahul Bedarkar Acked-by: Randy Dunlap Signed-off-by: Greg Kroah-Hartman

drivers: usb: core: devio.c: Spaces to tabs for proc_control_compat()

2013-10-16T20:38:37Z

Replaced spaces by tabs for proc_control_compat() function. Signed-off-by: Matthias Beyer Signed-off-by: Greg Kroah-Hartman

drivers: usb: core: devio.c: Spaces to tabs for proc_reapurbnonblock()

2013-10-16T20:38:37Z

Replaced spaces by tabs for proc_reapurbnonblock() function. Signed-off-by: Matthias Beyer Signed-off-by: Greg Kroah-Hartman

Merge 3.12-rc3 into usb-next

2013-09-30T01:45:55Z

We want the USB fixes in here as well. Signed-off-by: Greg Kroah-Hartman

usb/core/devio.c: Don't reject control message to endpoint with wrong direction bit

2013-09-26T00:30:39Z

Trying to read data from the Pegasus Technologies NoteTaker (0e20:0101) [1] with the Windows App (EasyNote) works natively but fails when Windows is running under KVM (and the USB device handed to KVM). The reason is a USB control message usb 4-2.2: control urb: bRequestType=22 bRequest=09 wValue=0200 wIndex=0001 wLength=0008 This goes to endpoint address 0x01 (wIndex); however, endpoint address 0x01 does not exist. There is an endpoint 0x81 though (same number, but other direction); the app may have meant that endpoint instead. The kernel thus rejects the IO and thus we see the failure. Apparently, Linux is more strict here than Windows ... we can't change the Win app easily, so that's a problem. It seems that the Win app/driver is buggy here and the driver does not behave fully according to the USB HID class spec that it claims to belong to. The device seems to happily deal with that though (and seems to not really care about this value much). So the question is whether the Linux kernel should filter here. Rejecting has the risk that somewhat non-compliant userspace apps/ drivers (most likely in a virtual machine) are prevented from working. Not rejecting has the risk of confusing an overly sensitive device with such a transfer. Given the fact that Windows does not filter it makes this risk rather small though. The patch makes the kernel more tolerant: If the endpoint address in wIndex does not exist, but an endpoint with toggled direction bit does, it will let the transfer through. (It does NOT change the message.) With attached patch, the app in Windows in KVM works. usb 4-2.2: check_ctrlrecip: process 13073 (qemu-kvm) requesting ep 01 but needs 81 I suspect this will mostly affect apps in virtual environments; as on Linux the apps would have been adapted to the stricter handling of the kernel. I have done that for mine[2]. [1] http://www.pegatech.com/ [2] https://sourceforge.net/projects/notetakerpen/ Signed-off-by: Kurt Garloff Acked-by: Alan Stern Cc: stable Signed-off-by: Greg Kroah-Hartman

usbcore: fix read of usbdevfs_ctrltransfer fields in proc_control()

2013-09-17T16:49:24Z

Urb fields are stored in struct usbdevfs_ctrltransfer in CPU byteorder and not in little endian, so there is no need to be converted. This bug was reported by sparse. Signed-off-by: Xenia Ragiadakou Signed-off-by: Greg Kroah-Hartman

usbfs: Allow printer class 'get_device_id' without needing to claim the intf

2013-07-25T19:01:12Z

For certain (HP) printers the printer device_id does not only contain a static part identifying the printer, but it also contains a dynamic part giving printer status, ink level, etc. To get to this info various userspace utilities need to be able to make a printer class 'get_device_id' request without first claiming the interface (as that is in use for the actual printer driver). Since the printer class 'get_device_id' request does not change interface settings in anyway, allowing this without claiming the interface should not cause any issues. CC: Sanjay Kumar CC: Alan Stern Signed-off-by: Hans de Goede Signed-off-by: Greg Kroah-Hartman

Merge 3.10-rc5 into usb-next

2013-06-09T04:27:51Z

We need the changes in this branch. Signed-off-by: Greg Kroah-Hartman

usbfs: Increase arbitrary limit for USB 3 isopkt length

2013-05-29T08:06:36Z

Increase the current arbitrary limit for isocronous packet size to a value large enough to account for USB 3.0 super bandwidth streams, bMaxBurst (0~15 allowed, 1~16 packets) bmAttributes (bit 1:0, mult 0~2, 1~3 packets) so the size max for one USB 3 isocronous transfer is 1024 byte * 16 * 3 = 49152 byte Acked-by: Alan Stern Signed-off-by: Federico Manzan Signed-off-by: Greg Kroah-Hartman

usb: devio: Fixed error: 'do not use assignment in if condition'

2013-05-17T17:05:57Z

This patch fixes error: 'do not use assignment in if condition' in USB/devio.c. Signed-off-by: Tülin İzer Signed-off-by: Greg Kroah-Hartman