On Thursday 28 August 2008 18:21:09 Greg KH wrote:Actually this is a good point. The USB spec mentions that the device should suspend when a constant idle state is detected for more than 3.0ms. I either have not seen that happening before or I missed something when writing my firmware. I'll keep an eye on my USB analyzer though :-) Although it's a good thing to keep to the spec, I also believe that in the case of a test and measurement device suspending the device may be an unwanted behaviour but perhaps I do misinterpret this part of the spec here. Anyway, this is no issue for self-powered devices, which is probably the majority in this class because most test & measurement devices need a good power supply and USB just isn't fit for that unless you're able to make a clean power from that (which is possible of course). Our device is both USB and self powered, but when in USB powered mode it will only suspend when the host goes in sleep mode. To be honest I would put suspend mode far down on the priority list :-) regards, Marcel --
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Willy Tarreau | Re: Linux 2.6.21 |
| Jan Kundrát | kswapd high CPU usage with no swap |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] tcp: splice as many packets as possible at once |
