This patch (as1599) fixes dummy-hcd to make it update the appropriate
driver pointer when a new gadget driver is bound or unbound. Without
this change, the gadget driver's name doesn't appear in dev_printk
output.
Signed-off-by: Alan Stern <st...@rowland.harvard.edu>
---
This is unrelated to the new ->reset callback stuff. I just noticed
this issue while testing and decided to fix it. Therefore this patch
should go into your regular gadget-next branch instead of the "reset"
branch.
drivers/usb/gadget/dummy_hcd.c | 2 ++
1 file changed, 2 insertions(+)
Index: usb-3.5/drivers/usb/gadget/dummy_hcd.c
===================================================================
--- usb-3.5.orig/drivers/usb/gadget/dummy_hcd.c
+++ usb-3.5/drivers/usb/gadget/dummy_hcd.c
@@ -909,6 +909,7 @@ static int dummy_udc_start(struct usb_ga
dum->devstatus = 0;
dum->driver = driver;
+ dum->gadget.dev.driver = &driver->driver;
dev_dbg(udc_dev(dum), "binding gadget driver '%s'\n",
driver->driver.name);
return 0;
@@ -923,6 +924,7 @@ static int dummy_udc_stop(struct usb_gad
dev_dbg(udc_dev(dum), "unregister gadget driver '%s'\n",
driver->driver.name);
+ dum->gadget.dev.driver = NULL;
dum->driver = NULL;
return 0;
--
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/majordomo-info.html
