> -----Original Message----- > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > Sent: Thursday, February 17, 2011 4:35 AM > To: Rajendra Nayak > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Subject: RE: [PATCH 00/11] OMAP2+: clock: add clockfw autoidle for iclks, OMAP2xxx > > On Wed, 16 Feb 2011, Rajendra Nayak wrote: > > > Boot-tested on 3430sdp/4430sdp, with CONFIG_PM and with !CONFIG_PM. > > suspend-offmode tested on 3430sdp and suspend-retmode on 4430sdp (with > > some out-of-tree patches) > > Thanks, will add Tested-by:s. > > > Dynamic idle testing on 3430sdp showed me some very jerky debug console > > the moment a 'echo 1 > /debug/pm_debug/sleep_while_idle' is done. This > > however seems to be the case even on 2.6.38-rc4 and not related to the > > current patch series. > > Does enabling CONFIG_OMAP2_DSS resolve the problem you're seeing? Maybe, will try it out. Thanks for the tip. > > > Will debug further, but seems to some 3430sdp specific issue, since you > > did not see it on Beagleboard and seems it is not seen on OMAP3 zoom's > > either. Just out of curiosity, what dynamic-idle state where you able to > > achieve on Beagle? > > Full chip off. I use omap2plus_defconfig, sometimes with CONFIG_OMAP2_DSS > depending on personal mood and what's being tested. I boot to a shell and > run the commands at the end of this message (some of which are probably > superfluous). Ok, thanks. > > > - Paul > > > echo 1 > /debug/pm_debug/sleep_while_idle > echo 1 > /debug/pm_debug/enable_off_mode > echo 5 > /sys/devices/platform/omap/omap_uart.0/sleep_timeout > echo 5 > /sys/devices/platform/omap/omap_uart.1/sleep_timeout > echo 5 > /sys/devices/platform/omap/omap_uart.2/sleep_timeout > echo enabled > /sys/devices/platform/omap/omap_uart.0/tty/ttyO0/power/wakeup > echo enabled > /sys/devices/platform/omap/omap_uart.1/tty/ttyO1/power/wakeup > echo enabled > /sys/devices/platform/omap/omap_uart.2/tty/ttyO2/power/wakeup > -- 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
