> -----Original Message----- > From: "Högander" Jouni [mailto:jouni.hogander@xxxxxxxxx] > Sent: Friday, July 04, 2008 3:02 PM > To: ext Rajendra Nayak > Cc: 'Peter 'p2' De Schrijver'; linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 00/11] OMAP3 CPUidle patches > > Let's continue this discussion in here to make sure that everybody > sees it. > > ext Högander Jouni <jouni.hogander@xxxxxxxxx> writes: > > > Hi Rajendra, > > > > "ext Rajendra Nayak" <rnayak@xxxxxx> writes: > > > >>> -----Original Message----- > >>> From: Peter 'p2' De Schrijver > [mailto:peter.de-schrijver@xxxxxxxxx] > >>> Sent: Wednesday, July 02, 2008 9:13 PM > >>> To: ext Rajendra Nayak > >>> Cc: linux-omap@xxxxxxxxxxxxxxx > >>> Subject: Re: [PATCH 00/11] OMAP3 CPUidle patches > >>> > >>> Hi Rajendra, > >>> > >>> > > >>> > Not sure, but you can try with my .config while I try > with yours. > >>> > I was doing some more testing today, and I saw a hang after > >>> a while of > >>> > idle activity with OFF being attempted multiple times. > >>> > Using lauterbach showed me it being stuck up in > >>> prcm_interrupt_handler trying > >>> > to clear MPU_IRQSTATUS. > >>> > Looks like in the PRCM interrupt handler somehow > >>> PM_WKST1_CORE is not cleared > >>> > (I see it set to 0x2000) and hence MPU_IRQSTATUS fails to clear. > >>> > > >>> > >>> Ok. I disabled OneNAND support and now I get off mode on > VDD2 as well. > >>> Consumption on VDD1 is 4uA and 32uA on VDD2. > Unfortunately after the > >>> first wakeup, off mode is never reached again. > >> > >> Do you see a hang? or OFF is never achieved? > >> Can you try with the latest fixes that I posted. > > > > As it seems to be hard to get similiar results with these patches, > > could you please send me your uImage? > > So Rajendra sent his uImage and it works quite ok what comes to off > mode on my sdp board. I still see problems with serial console (slow) > and on boot I need to generate manually interrupts to get it to > boot. Otherwise board hangs at this point: Yes, I noticed this as well. It takes quite long to bootup if you don't generate UART interrupts. After bootup once RET/OFF is hit, it takes a few hits to come out of it as IO wakeup is missing. > > eth0: link up > Sending DHCP requests ., OK > IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.2.101 > IP-Config: Complete: > device=eth0, addr=192.168.2.101, mask=255.255.255.0, > gw=192.168.2.1, > host=192.168.2.101, domain=ntc.nokia.com, nis-domain=(none), > bootserver=0.0.0.0, rootserver=172.22.146.197, rootpath= > Looking up port of RPC 100003/2 on 172.22.146.197 > Looking up port of RPC 100005/1 on 172.22.146.197 > VFS: Mounted root (nfs filesystem). > Freeing init memory: 108K > > Rajendra, are you still using .config file you sent to me? Are all the > changes in your tree available in l-o list. Yes, all the changes are part of the 11 patch set + 1 rework fixes patch I sent. To debug further, can you put a few prints in omap3_enter_idle and omap3_enter_idle_bm to see what states are selected by the menu gov. We will then know if CORE RET/OFF is attempted but not achieved due to some reason, or never attempted altogether. > > > > >> > >>> > >>> Cheers, > >>> > >>> Peter. > >>> > >> > >> -- > >> 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 > >> > >> > > > > -- > > Jouni Högander > > > > -- > > 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 > > > > > > -- > Jouni Högander > > -- 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
