From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: linxz02@ovi.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [pm] keep Cortex M3 cores running while OMAP4 is suspended?
Date: Sun, 19 Jun 2011 11:29:24 +0530 [thread overview]
Message-ID: <4DFD903C.4020402@ti.com> (raw)
In-Reply-To: <882569.33615.qm@web121412.mail.ne1.yahoo.com>
On 6/19/2011 10:37 AM, linxz02@ovi.com wrote:
> Hi All,
>
> I was wondering whether it is possible to keep the Cortex M3 cores running while the OMAP processor is suspended.
>
> My testing environment was simple: I used Pandaboard (OMAP4430) and kernel 2.6.35. I wrote an M3 program to toggle one GPIO pin (which drives a LED). As long as the M3 program is running, the LED will blink.
>
> On the kernel side, I tried to change the suspend functions in arch/arm/mach-omap2/pm44xx.c. I set the states of core_pwrdm and l4per_pwrdm to ON, right before the system suspends. However, when the system was suspended (omap4_pm_suspend() was invoked), the LED stopped to blink. I think the M3 cores were powered off then.
>
> Did I miss anything? I'll really appreciate any input. Thanks!
>
Are you trying this on mainline. Mostly not.
And when you say OMAP suspend, whole SOC should go down to low power
state. If you keep M3 active then CORE PD can't go down and hence the
OMAP won't really suspend. Mostly MPUSS and some independent PD's only
will transition.
Your problem is the GPIO clocks are cut in late suspend code.
You can comment out the gpio_suspend code. Since you don't use
GPIO kernel driver, linux side has no idea that any one else
wants to use GPIO.
Hope this helps.
Regards
Santosh
prev parent reply other threads:[~2011-06-19 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 5:07 [pm] keep Cortex M3 cores running while OMAP4 is suspended? linxz02
2011-06-19 5:59 ` Santosh Shilimkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFD903C.4020402@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linxz02@ovi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox