From: David Brownell <david-b@pacbell.net>
To: linux-omap-open-source@linux.omap.com
Subject: Re: [ERROR]: -ENODEV Error!
Date: Mon, 6 Nov 2006 13:44:39 -0800 [thread overview]
Message-ID: <200611061344.40177.david-b@pacbell.net> (raw)
In-Reply-To: <454F8488.6010806@nokia.com>
On Monday 06 November 2006 10:52 am, Felipe Balbi wrote:
> int usb_gadget_register_driver (struct usb_gadget_driver *driver)
> {
> int status = -ENODEV;
> struct omap_ep *ep;
> unsigned long flags;
>
> /* basic sanity tests */
> if (!udc) <---- THIS IS GIVING ME THE ERROR...
Then your board setup is probably wrong, so that probe() didn't get
called because there was no USB peripheral controller. Or probe()
failed for some reason.
This realy _is_ a fatal error...
> return -ENODEV;
> if (!driver
> // FIXME if otg, check: driver->is_otg
> || driver->speed < USB_SPEED_FULL
> || !driver->bind
> || !driver->unbind
> || !driver->setup) <------ THIS GAVE ME
> ANOTHER BUG!!! :-P
Also a fatal error. Gadget drivers **MUST** handle control messages, e.g.
so they will send device descriptors.
- Dave
prev parent reply other threads:[~2006-11-06 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 18:52 [ERROR]: -ENODEV Error! Felipe Balbi
2006-11-06 21:44 ` David Brownell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611061344.40177.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox