Re: 'ci_hdrc.0: failed to start' when using gadgetfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 27 Sep 2013, Marek Vasut wrote:

> Dear Fabio Estevam,
> 
> > Hi,
> > 
> > I am using mx53 (which uses the chipidea driver) and it works fine with
> > g_ether.
> > 
> > Now, I need to test gadgetfs and this is what I get:
> > 
> > $ modprobe gadgetfs
> > gadgetfs: USB Gadget filesystem, version 24 Aug 2004
> > 
> > $ mkdir  /dev/gadget
> > $ mount -t gadgetfs none /dev/gadget
> > nop ci_hdrc.0: failed to start (null): -120
> > 
> > This error message comes from:
> > 
> > ret = driver->bind(udc->gadget, driver);
> > 
> > inside udc_bind_to_driver() from udc_core.c
> > 
> > Any idea as to why driver->bind fails?
> > 
> > I will start debugging it, but would appreciate any suggestions.
> 
> gadgetfs_probe() returns -EISNAM unconditionally. That's rather strange.

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.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux