- 30 Jan, 2015 13 commits
-
-
Robert Jarzmik authored
All the gpios, ie. reset-gpios and vbus-detect-gpio, should be optional and not prevent the driver from working. Fix the regression in the behavior introduced by commit "usb: phy: generic: migrate to gpio_desc". Signed-off-by:
Robert Jarzmik <robert.jarzmik@free.fr> Tested-by:
Fabio Estevam <fabio.estevam@freescale.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Gregory Herrero authored
USB reset interrupt is no more used to reset the controller. Thus, reset the controller in pullup callback as described by Synopsys programming guide. Otherwise enumeration sometimes fails when usb configuration is switched without physical disconnection. Tested-by:
Robert Baldyga <r.baldyga@samsung.com> Acked-by:
John Youn <johnyoun@synopsys.com> Signed-off-by:
Gregory Herrero <gregory.herrero@intel.com> Signed-off-by:
-
Mian Yousaf Kaukab authored
Defines are more readable and searchable than constants. Tested-by:
Mian Yousaf Kaukab <yousaf.kaukab@intel.com> Signed-off-by:
-
Mian Yousaf Kaukab authored
hsotg->phyif is set in dwc2_gadget_init according to phy interface width. Use it for configuration instead of hardcoded value. Moreover, set USB turnaround time according to phy width. Tested-by:
-
Mian Yousaf Kaukab authored
Print debug message according to zlp direction. Always saying "Sending" is misleading. Tested-by:
-
Gregory Herrero authored
Pullup doesn't need to be enabled during usb reset since it is already enabled. This leads to shorter chirp-k duration if done during usb reset. Tested-by:
-
Gregory Herrero authored
Add a flag to request physical reset of the controller when s3c_hsotg_core_init_disconnected is called. During the usb reset, controller must not be fully reconfigured and resetted. Else this leads to shorter chirp-k duration during enumeration. Tested-by:
-
Mian Yousaf Kaukab authored
When using DMA, dwc2 requires buffers to be 4 bytes aligned. Use bounce buffers if they are not. Tested-by:
-
Mian Yousaf Kaukab authored
Remove dead code as well. Tested-by:
-
Gregory Herrero authored
s3c_hsotg_process_req_feature comments was not correct Tested-by:
-
Gregory Herrero authored
Handle SET_FEATURE TEST_MODE request sent by the host. Slightly rework FEATURE request handling to allow parsing other request types than Endpoint. Also add a debugfs to change test mode value from user space. Tested-by:
-
Gregory Herrero authored
When clearing HALT on an endpoint, req->complete of in progress requests must be called with locks off. New request should only be started if there is not already a pending request on the endpoint. Tested-by:
-
Gregory Herrero authored
When a remote wakeup happens during bus_suspend, hcd needs to resume its root hub. Acked-by:
-
- 29 Jan, 2015 22 commits
-
-
Arnd Bergmann authored
The omap musb front-end calls into the phy driver directly instead of using a generic phy interface, which causes a link error when the specific driver is not built-in: drivers/built-in.o: In function `omap2430_musb_disable': usb/musb/omap2430.c:480: undefined reference to `omap_control_usb_set_mode' drivers/built-in.o: In function `omap2430_musb_enable': usb/musb/omap2430.c:466: undefined reference to `omap_control_usb_set_mode' usb/musb/omap2430.c:447: undefined reference to `omap_control_usb_set_mode' drivers/built-in.o: In function `omap_musb_set_mailbox': usb/musb/omap2430.c:273: undefined reference to `omap_control_usb_set_mode' usb/musb/omap2430.c:304: undefined reference to `omap_control_usb_set_mode' drivers/built-in.o:(.debug_addr+0xbd9e0): more undefined references to `omap_control_usb_set_mode' follow This adds an explicit dependency. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Fixes: ca784be3 ("usb: start using the control module driver") Cc: <stable@vger.kernel.org> # v3.9+ Signed-off-by:
-
Arnd Bergmann authored
Multiple musb glue drivers depend on the generic usb phy support, but fail to list it as a dependency in Kconfig. This results in build erros like: drivers/built-in.o: In function `am35x_remove': :(.text+0xadacc): undefined reference to `usb_phy_generic_unregister' drivers/built-in.o: In function `am35x_probe': :(.text+0xae1c8): undefined reference to `usb_phy_generic_register' :(.text+0xae244): undefined reference to `usb_phy_generic_unregister' drivers/built-in.o: In function `jz4740_remove': :(.text+0xaf648): undefined reference to `usb_phy_generic_unregister' drivers/built-in.o: In function `jz4740_musb_init': :(.text+0xaf694): undefined reference to `usb_phy_generic_register' This adds the ones that are missing. Signed-off-by:
-
Peter Chen authored
The user can read it through sys entry. Signed-off-by:
Peter Chen <peter.chen@freescale.com> Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
fsl udc core assumes itself always self powered, so set is_selfpowered is 1. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Set value for common is_selfpowered. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
Delete private selfpowered variable, and use common one. Signed-off-by:
-
Peter Chen authored
The gadget power property will be used at get_status request. Signed-off-by:
-
Peter Chen authored
Whether the gadget is selfpowerwed or not can be determined by composite core, so we can use a common entry to indicate if the self-powered is supported by gadget, and the related private variable at individual udc driver can be deleted. Signed-off-by:
-
Felipe Balbi authored
commit 8e74475b (usb: dwc3: gadget: use udc-core's reset notifier) added support for the new UDC core's reset notifier to dwc3 but while at it, it removed a spin_lock() from dwc3_reset_gadget() which might cause an unbalanced spin_unlock() further down the line Fixes: 8e74475b (usb: dwc3: gadget: use udc-core's reset notifier) Cc: <stable@vger.kernel.org> # v3.19 Signed-off-by:
-
- 27 Jan, 2015 5 commits
-
-
Felipe Balbi authored
By moving all dev_vdbg() to tracepoints, we can finally get rid of dev_vdbg() usage from dwc3. Signed-off-by: -
Felipe Balbi authored
Sometimes we want to just print a formatted string without passing any extra data. The following will be used for removing reliance on dev_vdbg() from dwc3. Signed-off-by: -
Felipe Balbi authored
if an unknown IRQ event is triggered, that means the HW is really misbehaving. Instead of printing a debug message, let's WARN() so users report when that happens. Signed-off-by: -
Felipe Balbi authored
We already have both ret and dwc defined in this same function. Signed-off-by: -
Andrzej Pietrasiewicz authored
The purpose of the functions and their parametrs might not be obvious to the reader, so explain it. Signed-off-by:
Andrzej Pietrasiewicz <andrzej.p@samsung.com> Signed-off-by:
-
