Hi, > > So, a base load of 3.8 W seems to be caused by any connected usb device > > preventing C3 and some 250 ms polling done by uhci_hcd, plus a bit for > > the device itself. According to > > http://www.mail-archive.com/linux-usb-users@xxxxxxxxxxxxxxxxxxxxx/msg19354.html > > (why aren't there any message IDs on any of those archive sites, BTW?) > > that's the expected behaviour. > > Presumably power-management changes have a time granuarity i.e. if you > make the CPU busy for one moment, it would stay in the higher-power > state for a while before dropping down? That's the standard thing to > do for prevent the power state being changed too often (and have bad > effects of some sort)? Well, yeah, but: There are "only" some 1050 wakeups per second going on, 1000 of which are the timer tick, despite NO_HZ. And all of them in total seem to be using < 1 % of the CPU. Given that /proc/acpi/processor/CPU0/power lists a latency of 65 µs for C3, I don't quite see how that fits together. Florian -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
