From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 5/6] ARM: OMAP4: hwmod_data: Do not get DSP out of reset at boot time
Date: Tue, 28 Feb 2012 17:05:28 +0200 [thread overview]
Message-ID: <1330441528.2116.46.camel@sokoban> (raw)
In-Reply-To: <alpine.DEB.2.00.1202280330140.11716@utopia.booyaka.com>
On Tue, 2012-02-28 at 03:31 -0700, Paul Walmsley wrote:
> Hi
>
> On Fri, 24 Feb 2012, Tero Kristo wrote:
>
> > From: Rajendra Nayak <rnayak@ti.com>
> >
> > With no driver handling DSP, if brought out of reset, it stays
> > active and does not assert standby. This leads to IVAHD powerdomain not
> > transitioning and hence preventing chip retention.
> >
> > Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> > Signed-off-by: Tero Kristo <t-kristo@ti.com>
>
> Please test this series:
>
> http://marc.info/?l=linux-omap&m=133040749621183&w=2
>
> in lieu of this patch.
>
>
> - Paul
Just tried the CSWR set on top of your branch with this patch reverted
and it works nicely. I'll drop this patch out from the next version.
-Tero
next prev parent reply other threads:[~2012-02-28 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 15:15 [PATCHv2 0/6] ARM: OMAP4 core retention support Tero Kristo
2012-02-24 15:15 ` [PATCHv2 1/6] ARM: OMAP4: suspend: Program all domains to retention Tero Kristo
2012-02-24 15:15 ` [PATCHv2 2/6] ARM: OMAP4 PM: Add IO Daisychain support Tero Kristo
2012-02-28 10:33 ` Paul Walmsley
2012-02-24 15:15 ` [PATCHv2 3/6] ARM: OMAP3PLUS PM: Add IO Daisychain support via hwmod mux Tero Kristo
2012-02-24 15:15 ` [PATCHv2 4/6] ARM: OMAP4: prm: fix interrupt register offsets Tero Kristo
2012-02-24 15:15 ` [PATCHv2 5/6] ARM: OMAP4: hwmod_data: Do not get DSP out of reset at boot time Tero Kristo
2012-02-28 10:31 ` Paul Walmsley
2012-02-28 15:05 ` Tero Kristo [this message]
2012-02-29 16:46 ` Paul Walmsley
2012-02-24 15:15 ` [PATCHv2 6/6] ARM: OMAP3+: add prcm chain interrupts to the interrupt list Tero Kristo
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=1330441528.2116.46.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).