Why usb's remote wakeup relys on CONFIG_USB_SUSPEND

2013-04-16 Thread linux fddl
I am a new fish of linux usb host driver developper. Recently, when developping the host's PM function, I found that usb's remote wakeup relys on CONFIG_USB_SUSPEND. I do not know why we need such a restriction. Is it means if a usb host driver without the implementation of runtime suspend also ca

usb: ralink: Is it right that usb_hcd_link_urb_to_ep() returns -EPERM?

2013-04-23 Thread linux fddl
Recently, I test my usb host driver(not ehci or any widely used usb host) with a Ralink's wifi device(use a linux-3.0.39 kernel). But, if transferring data through FTP for a long time, I found that usb_hcd_link_urb_to_ep() (It is called by hcd's urb_enqueue function) returns -EPERM sometimes. Aft

why we need a msleep(5) in ehci_bus_suspend/resume

2013-05-12 Thread linux fddl
Hi, From the ehci-hub.c, I find that ehci_bus_suspend/resume have some code like this: if (time_before(jiffies, ehci->netx_statechange)) msleep(5); ... ehci->next_statechange = jiffies + msec_to_jiffies(10); and if (time_before(jiffies, ehci->netx_statechange)) msleep(5); ... ehci->ne

usb: why we need a msleep(5) in ehci_bus_suspend/resume

2013-05-13 Thread linux fddl
Hi, From the ehci-hub.c, I find that ehci_bus_suspend/resume have some code like this: if (time_before(jiffies, ehci->netx_statechange)) msleep(5); ... ehci->next_statechange = jiffies + msec_to_jiffies(10); and if (time_before(jiffies, ehci->netx_statechange)) msleep(5); ... ehci->ne

usb:is that a bug?

2013-05-16 Thread linux fddl
Hi, When I used mass_storage as a gadget(use a linux-3.0.77 kernel), After the following operations: 1.Turn my board into hibernation. 2.Plug the usb into host before resume. 3.Resume my board. I saw some dump message like this, after some digging, I think the other devices' retore time is too l

usb:is that a bug?

2013-05-19 Thread linux fddl
Hi, When I used mass_storage as a gadget(use a linux-3.0.77 kernel), After the following operations: 1.Turn my board into hibernation. 2.Plug the usb into host before resume. 3.Resume my board. I saw some dump message like this, after some digging, I think the other devices' retore time is too l