On Fri, Dec 17, 2010 at 11:14:50AM +0000, Tomasz Mloduchowski wrote:
I really appreciate your help, this sort of a bug that really stunned me.
I've noticed that the variable storing the error code is set to NULL
right before printing it out :(, so I corrected this mistake.
[ 2.065216] ehci-omap ehci-omap.0: failed to get ehci port1
regulator --> -19
Thanks for that :-)
Error -19 is -ENODEV, so it means there really isn't a regulator.
Maybe you can more debug to ehci_reset() function ?!?
I also switched to pastebin, with the new, more meaningful dmesg:
http://pastebin.com/86kfLT2G
I'll look at it and get back to you. But try to figure out exactly where
ehci decides to bounce the port to companion ohci and start adding
printks or dev_info to that. A good start is ehci_reset(), something
like below might help:
diff --git a/drivers/usb/host/ehci-dbg.c b/drivers/usb/host/ehci-dbg.c
index 6e25996..7fdaecf 100644
--- a/drivers/usb/host/ehci-dbg.c
+++ b/drivers/usb/host/ehci-dbg.c
@@ -330,7 +330,7 @@ dbg_port_buf (char *buf, unsigned len, const char *label, int port, u32 status)
#define dbg_cmd(ehci, label, command) { \
char _buf [80]; \
dbg_command_buf (_buf, sizeof _buf, label, command); \
- ehci_dbg (ehci, "%s\n", _buf); \
+ ehci_info (ehci, "%s\n", _buf); \
}
#define dbg_port(ehci, label, port, status) { \
a lot already.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
