public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/5] extra module resets to ensure full-chip idle
Date: Thu, 27 Nov 2008 06:04:18 +0100	[thread overview]
Message-ID: <492E2A52.4030200@googlemail.com> (raw)
In-Reply-To: <1227744349-12118-1-git-send-email-khilman@deeprootsystems.com>

Kevin Hilman wrote:
> Various bootloaders have been known to leave modules in a state
> which prevents full-chip retention.  

Does it make sense to check if

[PATCH 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot
[PATCH 2/5] OMAP3: PM: Force IVA2 into idle during bootup

can be done in U-Boot, too? If yes, I would have a look to it.

Regards

Dirk

> This series forces
> MMC, IVA2 and D2D/modem into known reset/idle states so that
> the OMAP3 can hit full-chip idle.
> 
> Tested on OMAP3 Beagle, and custom OMAP3 hardware.
> 
> NOTE: this is similar to the set I posted for the PM branch
>       but this series is rebased onto linux-omap and includes
>       the MMC reset.
> 
> Kevin Hilman (5):
>   OMAP3: PM: HSMMC: force MMC module reset on boot
>   OMAP3: PM: Force IVA2 into idle during bootup
>   OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init
>   OMAP3: PM: D2D clockdomain supports SW supervised transitions
>   OMAP3: PM: Ensure modem is reset during PRCM init
> 
>  arch/arm/mach-omap2/clock34xx.h           |   37 +++++++++++++-
>  arch/arm/mach-omap2/clockdomains.h        |    2 +-
>  arch/arm/mach-omap2/cm-regbits-34xx.h     |   14 +++++
>  arch/arm/mach-omap2/devices.c             |   76 +++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/pm34xx.c              |   65 ++++++++++++++++++++++++-
>  arch/arm/plat-omap/include/mach/control.h |    5 ++
>  6 files changed, 195 insertions(+), 4 deletions(-)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  parent reply	other threads:[~2008-11-27  5:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  0:05 [PATCH 0/5] extra module resets to ensure full-chip idle Kevin Hilman
2008-11-27  0:05 ` [PATCH 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot Kevin Hilman
2008-11-27  0:05   ` [PATCH 2/5] OMAP3: PM: Force IVA2 into idle during bootup Kevin Hilman
2008-11-27  0:05     ` [PATCH 3/5] OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init Kevin Hilman
2008-11-27  0:05       ` [PATCH 4/5] OMAP3: PM: D2D clockdomain supports SW supervised transitions Kevin Hilman
2008-11-27  0:05         ` [PATCH 5/5] OMAP3: PM: Ensure modem is reset during PRCM init Kevin Hilman
2008-11-27  0:25   ` [PATCH 1/5] OMAP3: PM: HSMMC: force MMC module reset on boot Tony Lindgren
2008-11-27  5:04 ` Dirk Behme [this message]
2008-11-27  5:14   ` [PATCH 0/5] extra module resets to ensure full-chip idle Kevin Hilman
2008-11-27  9:02 ` Koen Kooi
2008-11-30  5:10   ` Kevin Hilman
2008-12-01  7:42     ` 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=492E2A52.4030200@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.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