Hi Sanjeev, > > 1). What omap3430 board(s) are being using to validate the pm > > branch functionality? > > [sp] I believe most common are omap3evm and beagle.
Do you know if we are doing any validation on the SDP3430 or Zoom boards? Using defconfig for the SDP3430 the kernel failed to boot. I found that this was due to the MUSB driver and SmartReflex. Disabling these allows it to boot. > > 2). Is there a list of pm features are currently > > supported/functional for omap3430? For example, cpuidle, > > cpufreq, retention, off-mode, smart-reflex, suspend/restore, etc. > > [sp] All of above - though all drivers may not support power > management. Hence you may see some failures scenarios > esp. with off mode. Off mode does not appear to be working currently on the SDP. It hangs when enabled. Is off-mode stable on any of the boards? > > 3). Are there any userspace tools (such as powertop) that are > > recommended for monitoring power states? > > [sp] You can definitely use powertop. Is this what everyone is using or is there any other diagnostics available through the proc or sys file-systems? Powertop is fine but I am curious how people are validating which c-states are being entered. Cheers Jon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
