linux-toradex.git/drivers/usb/dwc3, branch v3.9.2 Linux kernel for Apalis and Colibri modules usb: dwc3: ep0: fix sparc64 build 2013-03-08T07:42:50+00:00 Andrew Morton akpm@linux-foundation.org 2013-03-08T07:42:50+00:00 c390b0363d6cc201db93de69b5e88f482322d821 drivers/usb/dwc3/ep0.c: In function `__dwc3_ep0_do_control_data': drivers/usb/dwc3/ep0.c:905: error: `typeof' applied to a bit-field Looks like a gcc-3.4.5/sparc64 bug. Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Felipe Balbi <balbi@ti.com> 
drivers/usb/dwc3/ep0.c: In function `__dwc3_ep0_do_control_data':
drivers/usb/dwc3/ep0.c:905: error: `typeof' applied to a bit-field

Looks like a gcc-3.4.5/sparc64 bug.

Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Felipe Balbi <balbi@ti.com>
usb: dwc3: gadget: remove unnecessary code 2013-03-04T07:33:25+00:00 Felipe Balbi balbi@ti.com 2013-02-15T08:45:42+00:00 e5b29b25f8f88ece53579fa87580bb2973815977 the params variables on dwc3_gadget_conndone_interrupt() is only memset() to zero but never used in that function, so we can safely drop the variable and memset() call. Signed-off-by: Felipe Balbi <balbi@ti.com> 
the params variables on dwc3_gadget_conndone_interrupt()
is only memset() to zero but never used in
that function, so we can safely drop the variable
and memset() call.

Signed-off-by: Felipe Balbi <balbi@ti.com>
usb: dwc3: glue layers shouldn't know about the core IP 2013-03-04T07:33:24+00:00 Felipe Balbi balbi@ti.com 2013-02-12T08:48:55+00:00 d82f3e3cd88053836a2dd928b5545873cbdcf7da remove inclusion of "core.h" from all glue layers as they don't need to know details about the core IP. Signed-off-by: Felipe Balbi <balbi@ti.com> 
remove inclusion of "core.h" from all glue
layers as they don't need to know details
about the core IP.

Signed-off-by: Felipe Balbi <balbi@ti.com>
usb: dwc3: omap: fix a typo on of_device_id 2013-03-04T07:33:23+00:00 Felipe Balbi balbi@ti.com 2013-02-11T08:31:15+00:00 2c2dc89cc5d68ca161d50011cdcbf8aa830b9498 s/matach/match No functional changes Signed-off-by: Felipe Balbi <balbi@ti.com> 
s/matach/match

No functional changes

Signed-off-by: Felipe Balbi <balbi@ti.com>
usb: dwc3: core: don't forget to free coherent memory 2013-03-04T07:33:22+00:00 Felipe Balbi balbi@ti.com 2013-02-08T13:14:16+00:00 d9b4330adec006c2e8907bdcacd9dcc0e8874d18 commit 3921426 (usb: dwc3: core: move event buffer allocation out of dwc3_core_init()) introduced a memory leak of the coherent memory we use as event buffers on dwc3 driver. If the driver is compiled as a dynamically loadable module and use constantly loads and unloads the driver, we will continue to leak the coherent memory allocated during ->probe() because dwc3_free_event_buffers() is never called during ->remove(). Cc: <stable@vger.kernel.org> # v3.7 v3.8 Signed-off-by: Felipe Balbi <balbi@ti.com> 
commit 3921426 (usb: dwc3: core: move
event buffer allocation out of
dwc3_core_init()) introduced a memory leak
of the coherent memory we use as event
buffers on dwc3 driver.

If the driver is compiled as a dynamically
loadable module and use constantly loads
and unloads the driver, we will continue
to leak the coherent memory allocated during
->probe() because dwc3_free_event_buffers()
is never called during ->remove().

Cc: <stable@vger.kernel.org> # v3.7 v3.8
Signed-off-by: Felipe Balbi <balbi@ti.com>
drivers/usb: add missing GENERIC_HARDIRQS dependencies 2013-02-08T20:16:12+00:00 Heiko Carstens heiko.carstens@de.ibm.com 2013-02-06T16:24:01+00:00 5273afe359f700ac28bf8e9d63d733dbe0483e62 Add a couple of missing GENERIC_HARDIRQS dependencies to fix link errors like below on s390: ERROR: "devm_request_threaded_irq" [drivers/usb/gadget/mv_udc.ko] undefined! Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
Add a couple of missing GENERIC_HARDIRQS dependencies to fix link
errors like below on s390:

ERROR: "devm_request_threaded_irq" [drivers/usb/gadget/mv_udc.ko] undefined!

Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Merge 3.8-rc5 into usb-next 2013-01-25T20:41:02+00:00 Greg Kroah-Hartman gregkh@linuxfoundation.org 2013-01-25T20:41:02+00:00 67635d397a643514fdfa859f611b86bd3ad8958d This fixes up a conflict with drivers/usb/serial/io_ti.c that came up in linux-next. Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
This fixes up a conflict with drivers/usb/serial/io_ti.c that came up in
linux-next.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Merge tag 'xceiv-for-v3.9' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next 2013-01-25T17:09:46+00:00 Greg Kroah-Hartman gregkh@linuxfoundation.org 2013-01-25T17:09:46+00:00 4811f53fada7f2c6616229cc410e79362818a613 Felipe writes: usb: xceiv: patches for v3.9 merge window Two new PHY drivers coming here: one for Samsung, one for OMAP. Both architectures are adding USB3 support to mainline kernel. The PHY layer now allows us to have mulitple PHYs of the same type, which is necessary for platforms which provide more than one USB peripheral port. There's also a few cleanups here: removal of __dev* annotations, conversion of a cast to to_delayed_work(), and mxs-phy learns about ->set_suspend. 
Felipe writes:
	usb: xceiv: patches for v3.9 merge window

	Two new PHY drivers coming here: one for Samsung,
	one for OMAP. Both architectures are adding USB3
	support to mainline kernel.

	The PHY layer now allows us to have mulitple PHYs
	of the same type, which is necessary for platforms
	which provide more than one USB peripheral port.

	There's also a few cleanups here: removal of __dev*
	annotations, conversion of a cast to to_delayed_work(),
	and mxs-phy learns about ->set_suspend.
usb: dwc3: host: Change platform device ID for xhci-hcd to AUTO 2013-01-25T11:19:52+00:00 Vivek Gautam gautam.vivek@samsung.com 2013-01-25T11:22:02+00:00 52758bcb7c12bede2a81849dee13f1edcd44e1c1 Multiple dwc3 controllers will try to allocate multiple xhci-hcd interfaces. Changing platform device IDs from NONE to AUTO to support such cases. Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com> Signed-off-by: Felipe Balbi <balbi@ti.com> 
Multiple dwc3 controllers will try to allocate multiple xhci-hcd
interfaces.
Changing platform device IDs from NONE to AUTO to support
such cases.

Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
usb: dwc3: exynos/omap: Change platform device IDs for no_op_xceive to AUTO 2013-01-25T11:19:50+00:00 Vivek Gautam gautam.vivek@samsung.com 2013-01-25T11:22:01+00:00 b0e45ddb96d5a972a8b76354f036b90549ae85b3 Multiple dwc3 probe calls try to allocate no_op_xceive platform device. Having static IDs for these will throw sysfs error -EEXIST. Changing these static platform device IDs to AUTO to enable multiple dwc3 controller support on a SoC. Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com> Signed-off-by: Felipe Balbi <balbi@ti.com> 
Multiple dwc3 probe calls try to allocate no_op_xceive platform
device. Having static IDs for these will throw sysfs error -EEXIST.
Changing these static platform device IDs to AUTO to enable
multiple dwc3 controller support on a SoC.

Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>