Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: > Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: > >> Juha Kuikka <juha.kuikka@xxxxxxxxx> writes: >> >>> On Tue, Oct 6, 2009 at 4:16 PM, Kevin Hilman >>> <khilman@xxxxxxxxxxxxxxxxxxx> wrote: >>>> >>>> Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: >>>> >>>> > Hello, >>>> > >>>> > I've rebased/updated the PM branch based on current linux-omap master >>>> > branch (2.6.32-rc1 based.) >>>> > >>>> > I've also updated the OMAP Power Management wiki, and the 'Current >>>> > version' section highlights the changes, supported platforms as well >>>> > as the features that have made it into mainline. >>>> > >>>> > http://elinux.org/OMAP_Power_Management#Current_version >>>> > >>>> >>>> FYI... I just rebased the PM branch onto current omap/master. >>>> >>>> Some important user-visible changes: The /sys/power/* options are >>>> moving into debugfs. For mainline, these primarily debug options need >>>> to move to debugfs so I've moved them there. So, if you're missing >>>> some flag under /sys/power, it's now under /debug/pm_debug. >>>> >>>> I've updated the 'Using the PM branch' seciont of PM wiki[1] with >>>> the new filenames. >>>> >>>> Kevin >>>> >>>> [1] http://elinux.org/OMAP_Power_Management >>>> -- >>>> 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 >>> >>> Hi, >> >> Hi Juha, >> >>> I build and tried this latest on Beagleboard (C2). Booting from MMC >>> using ramdisk image. I changed the LL console to the 3rd UART. >>> >>> The issue I have is that after the system boots up it works for as >>> long as I keep actively using it but if I leave it idle for a short >>> time (~5s) it stops responding. I have tried waking it up using both >>> UART and "USER" button on the board. This is with the default PM >>> configuration. >> >> Thanks for testing, and reporting your problem. I have noticed >> exactly the same problem and am still investigating it. >> >>> If I put the board into suspend (retention) it wakes up without any issues. >>> >>> Also, if I enable "/debug/pm_debug/sleep_while_idle" board wakes up >>> without issues. Well the first couple characers on the console seem to >>> go missing but I guess without CTS/RTS that is expected? >> >> Yes, the loss of the first character is expected. >> >>> Any pointers would be appreciated. >> >> I also noticed that it works when 'sleep_while_idle' is enabled, and >> this has led me to suspect a bug in that serial timout path, but I >> have yet to debug further. > > FYI... > > I haven't figured out exactly why yet, but this patch gets things > working again. > > Basically, I'm just leaving smart-idle disabled all the time. > I've discovered that this is only needed when using the older u-boot binary I was downloading from beagleboard.org. I've had lots of PM headaches when using this u-boot and I had forgotten that I had (re)flashed with it. If I build and use a u-boot from the u-boot-ti repo[1], I don't have this problem anymore. I don't really have the time or motiviation to debug that older u-boot, so my recommendation is to use the latest one from the TI repo below. Thanks, Kevin [1] git://git.denx.de/u-boot-ti.git -- 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
