From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 2/8] ARM: OMAP4: PM: add errata support
Date: Wed, 7 Nov 2012 12:11:33 +0200 [thread overview]
Message-ID: <1352283093.2406.2.camel@sokoban> (raw)
In-Reply-To: <87d2zq761g.fsf@deeprootsystems.com>
On Tue, 2012-11-06 at 13:52 -0800, Kevin Hilman wrote:
> Kevin Hilman <khilman@deeprootsystems.com> writes:
>
> > Tero Kristo <t-kristo@ti.com> writes:
> >
> >> Added similar PM errata flag support as omap3 has. This should be used
> >> in similar manner, set the flags during init time, and check the flag
> >> values during runtime.
> >>
> >> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> >
> > These allow basic suspend/resume to work on 4460/Panda-ES, so I'm going
> > to queue these up as fixes.
> >
> > However, since they're not technically regressions, it may be too late
> > to get them in for v3.7, but they'll be in for v3.8 for sure.
>
> To be more specific, I'm planning on queuing patches 2, 3 and 6 as fixes
> for v3.8 (branch: for_3.8/fixes/pm).
>
> Paul has already queued patch 1, so that leaves patches 4, 5, 7 & 8.
>
> I think we can get this series in for v3.8 if we drop the functional
> pwrst dependency. To test, I dropped patches 5 & 7, and tested on
> 4430/Panda and 4460/Panda-ES (with latest mainline u-boot) and CORE
> is hitting retention just fine in suspend.
>
> If you can respin patch 8 based on the feedback from Felipe, I'll queue
> up patches 4 & 8 for v3.8 as well, then we'll at least have CORE
> retention in suspend in mainline. Then, the rest can be done when
> functional pwrsts are ready.
Yea, I can do that on Friday once I get back home, I am travelling
currently.
>
> Kevin
>
> P.S. do you have any patches to add any OMAP4 CPUidle support for CORE
> retention?
No, cpuidle core ret should work with this set already. Not sure what
happens without the func pwrst patches, I have not tested with that
setup lately. I can try this out on Friday as well.
-Tero
next prev parent reply other threads:[~2012-11-07 10:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:20 [PATCHv9 0/8] ARM: OMAP4: core retention support Tero Kristo
2012-10-18 9:20 ` [PATCHv9 1/8] ARM: OMAP: hwmod: Add support for per hwmod/module context lost count Tero Kristo
2012-10-27 3:00 ` Paul Walmsley
2012-11-21 23:05 ` Paul Walmsley
2012-10-18 9:20 ` [PATCHv9 2/8] ARM: OMAP4: PM: add errata support Tero Kristo
2012-11-05 22:36 ` Kevin Hilman
2012-11-06 21:52 ` Kevin Hilman
2012-11-07 10:11 ` Tero Kristo [this message]
2012-10-18 9:20 ` [PATCHv9 3/8] ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change Tero Kristo
2012-10-18 9:20 ` [PATCHv9 4/8] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-10-18 9:20 ` [PATCHv9 5/8] ARM: OMAP4: PM: put all domains to OSWR during suspend Tero Kristo
2012-10-18 9:20 ` [PATCHv9 6/8] ARM: OMAP4: retrigger localtimers after re-enabling gic Tero Kristo
2012-10-27 2:51 ` Paul Walmsley
2012-11-05 22:25 ` Kevin Hilman
2012-11-06 9:15 ` Tero Kristo
2012-10-18 9:20 ` [PATCHv9 7/8] ARM: OMAP: PM: update target fpwrst to what pwrdm can reach Tero Kristo
2012-10-18 9:20 ` [PATCHv9 8/8] ARM: OMAP4: USB: power down MUSB PHY if not used Tero Kristo
2012-10-18 10:33 ` Felipe Balbi
2012-10-18 12:18 ` Tero Kristo
2012-10-18 13:53 ` Felipe Balbi
2012-10-18 14:39 ` Tero Kristo
2012-10-18 14:41 ` Felipe Balbi
2012-10-22 8:54 ` kishon
2012-10-22 9:07 ` Felipe Balbi
2012-10-22 9:25 ` kishon
2012-10-27 2:52 ` Paul Walmsley
2012-10-27 3:02 ` [PATCHv9 0/8] ARM: OMAP4: core retention support Paul Walmsley
2012-11-05 22:23 ` Kevin Hilman
2012-11-06 9:18 ` Tero Kristo
2012-11-06 21:19 ` Kevin Hilman
2012-11-07 10:17 ` Tero Kristo
2012-11-12 14:41 ` Tero Kristo
2012-11-13 19:18 ` Kevin Hilman
2012-11-07 18:35 ` Paul Walmsley
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=1352283093.2406.2.camel@sokoban \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).