RE: OMAP35x GP TIMER as a wakeup trigger

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ashwin,
              Please see below:
>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?
[Romit] Already this is being done during the CPU Idle path. Yes you need to program the GPT 1 into oneshot mode with expiry time as appropriate. Also set the CM_CLKSEL_WKUP.CLKSEL_GPT1 to sys_32K clock. 
PM_MPUGRPSEL_WKUP.GRPSEL_GPT1, PM_WKEN_WKUP.EN_GPT1 should be set.

>
>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.

 [Romit] prcm_interrupt_handler. Look for PM_WKST_WKUP.

Thanks,
-Romit

--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux