NeilBrown <neilb@xxxxxxx> writes: > On Thu, 19 Jan 2012 16:22:37 -0800 Kevin Hilman <khilman@xxxxxx> wrote: > >> NeilBrown <neilb@xxxxxxx> writes: >> >> > On Thu, 19 Jan 2012 11:37:39 -0800 Kevin Hilman <khilman@xxxxxx> wrote: >> > >> >> "Joe Woodward" <jw@xxxxxxxxxxxxxx> writes: >> >> [...] >> At least this part is expected. >> >> In the kernel you're using the UART clocks are enabled/disabled during >> the idle path depending on the low-power state being targetted, so would >> expect to see lots of UART clock gating going on. > > Even though uarts 1,2,4 aren't even in use? Yes. Our UART idle management before v3.3 was, um... a disaster. > Maybe this is fixed in 3.3? As of v3.3, the UARTs are managed independently using runtime PM autosupend, so only UART that are in use should be coming on and back off again. However, as Paul has recently posted some UART fixes, you'll see that we have a few kinks to work out in the UART driver as well. Kevin -- 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
