From: Tero Kristo <t-kristo@ti.com>
To: linux-omap@vger.kernel.org, khilman@ti.com, paul@pwsan.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/4] ARM: OMAP4: core retention support
Date: Wed, 29 Feb 2012 17:25:02 +0200 [thread overview]
Message-ID: <1330529106-10423-1-git-send-email-t-kristo@ti.com> (raw)
Hi,
Changes compared to previous version:
- split out the io_chain set as a separate set
- marked patch 3 as TEMP, this is only needed until Paul's pwrdm fixes
get merged (http://marc.info/?l=linux-omap&m=133040749621183&w=2)
Depends on the io_chain set to provide wakeup capability from
retention.
Tested with omap4430 blaze : suspend / resume works okay.
-Tero
next reply other threads:[~2012-02-29 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 15:25 Tero Kristo [this message]
2012-02-29 15:25 ` [PATCHv3 1/4] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-03-06 0:33 ` Kevin Hilman
2012-03-06 8:31 ` Tero Kristo
2012-03-06 8:43 ` Rajendra Nayak
2012-03-06 8:54 ` Tero Kristo
2012-03-06 8:59 ` Rajendra Nayak
2012-03-06 9:23 ` Tero Kristo
2012-02-29 15:25 ` [PATCHv3 2/4] ARM: OMAP4: prm: fix interrupt register offsets Tero Kristo
2012-02-29 16:51 ` Paul Walmsley
2012-02-29 15:25 ` [PATCHv3 3/4] TEMP: ARM: OMAP4: hwmod_data: Do not get DSP out of reset at boot time Tero Kristo
2012-02-29 15:25 ` [PATCHv3 4/4] ARM: OMAP3+: add prcm chain interrupts to the interrupt list Tero Kristo
2012-03-01 7:01 ` Rajendra Nayak
2012-03-01 8:23 ` Tero Kristo
2012-03-01 9:46 ` Russell King - ARM Linux
2012-03-01 10:03 ` Tero Kristo
2012-02-29 15:34 ` [PATCHv3 0/4] ARM: OMAP4: core retention support Shilimkar, Santosh
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=1330529106-10423-1-git-send-email-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).