Hi Alan,
On Fri, Sep 27, 2013 at 12:44 PM, Alan Stern <[email protected]> wrote:
> It is a temporary measure, used only when the file system is set up
> initially. The real bind routine is gadgetfs_bind(), which gets called
> when userspace configures the gadget.
>
> In short, this is how it is intended to work. It isn't a bug.
Thanks for your explanation.
Should we change this message to dev_dbg?
--- a/drivers/usb/gadget/udc-core.c
+++ b/drivers/usb/gadget/udc-core.c
@@ -356,7 +356,7 @@ static int udc_bind_to_driver(struct usb_udc *udc,
struct usb_gadget_driver *dri
kobject_uevent(&udc->dev.kobj, KOBJ_CHANGE);
return 0;
err1:
- dev_err(&udc->dev, "failed to start %s: %d\n",
+ dev_dbg(&udc->dev, "failed to start %s: %d\n",
udc->driver->function, ret);
udc->driver = NULL;
udc->dev.driver = NULL;
Thanks,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
