> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Ashwin Bihari > Sent: Monday, April 27, 2009 9:20 PM > To: linux-omap@xxxxxxxxxxxxxxx Mailing List > Subject: OMAP35x GP TIMER as a wakeup trigger > > Greetings, > > I need to implement a timer as a wake up trigger while my custom board > is in the suspended state. I read in the TRM that all of the GPTIMERs > have the capability of generating a wake up interrupt. I'm using the > 2.6.28-rc8 PM Kernel which contains the patch to enable all the > GPTIMERS as wake up sources. Are you refering to the "suspend" state coming from: echo mem > /sys/power/state OR One of the idle states C0-C6? To understand the wakeup sequence from suspend; take a look at: arch/arm/mach-omap2/serial.c ...esp the IOPAD configuration. You will have to do something similar. ~sanjeev > > Could someone familiar with this scheme quickly elaborate all the > steps that I need to go through to get the system to come out of > suspend purely on the timer? Is it is just enough to setup the timer > correctly, enable the interrupt in the appropriate register and assume > that the PM layer will get the interrupt and do the right thing, or is > there more that I have to do? > > Also, as as additional thing, if the PM layer handles the interrupt > and begins the wake-up process, if I could know where that > specifically happens, that'd be great since I need to know that the > wake-up process is being triggered by the GPTIMER as opposed to the > other wakeup triggers and deal with that differently. > > Regards > -- Ashwin > -- > 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 > > -- 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
