On Saturday 22 January 2011 21:38:47 Richard Schütz wrote: > I noticed that from kernel 2.6.37 on (i've tested 2.6.38-rc2, too) ath9k > prevents my CPU (Intel Atom N450) from entering the C4 power state. It > only goes down to C2 (there's no C3) instead. In 2.6.36(.3) everything > is still fine. The CPU will only go down to C4 with 2.6.37 when the > wireless interface is brought down. "ath9k: Fix a DMA latency issue for Intel Pinetrail platforms." http://www.spinics.net/lists/linux-wireless/msg58264.html the pm_qos value will be configurable with 2.6.38: "ath9k: Make PM-QOS value as user configurable" http://www.spinics.net/lists/linux-wireless/msg61259.html "This will help our customers to configure the pm-qos value according to the effect in throughput due to the DMA latency problem which was observed in Intel Pinetrail platforms." -- 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