public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH][RFC] sh: suspend interpreter V1
Date: Fri, 17 Apr 2009 21:38:30 +0000	[thread overview]
Message-ID: <20090417213830.GG9111@game.jcrosoft.org> (raw)
In-Reply-To: <20090323091739.25647.6773.sendpatchset@rx1.opensource.se>

On 19:39 Fri 17 Apr     , Magnus Damm wrote:
> Hi Francesco,
> 
> On Fri, Apr 17, 2009 at 3:44 PM, Francesco VIRLINZI
> <francesco.virlinzi@st.com> wrote:
> > I just completed something similar on our ST40 (with PMB enabled).
> > We put the DRAM in self refresh an after that we totally turn-off the SOC
> > removing the power.
> > An external little micro has to detect the wakeup event and has to turn-on
> > the SOC.
> > The bootloader "understands" linux is frozen in memory and jump directly on
> > linux.
> >
> > Internally we call that "hibernation on memory" and clearly it needs update
> > in both linux/bootloader...
> > But from the device driver point of view this is a normal hibernation while
> > for the main core this is a special 'boot'.
> 
> Sounds a bit similar to U-standby mode on SuperH Mobile.
> 
> > Currently as major change I did are in the TMU/PMB and some asm code to
> > manage the "reboot".
> >
> > Do you think there is something shareable?
> 
> For boot loader, do you use upstream U-boot? That would be interesting to see.
no old u-boot version 1.3.1 with a diferrent implemntation as the actual SH4
Mainline support

Actually it will be nice to have it, I've this exact hardware design and wish
to do it we on a 7105.

Francesco do you have any patch or tree were we can take a look on it?

Best Regards,
J.

  parent reply	other threads:[~2009-04-17 21:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  9:17 [PATCH][RFC] sh: suspend interpreter V1 Magnus Damm
2009-03-23 15:35 ` Francesco VIRLINZI
2009-03-24  7:00 ` Francesco VIRLINZI
2009-03-24 11:08 ` Magnus Damm
2009-03-24 13:41 ` Francesco VIRLINZI
2009-03-25 10:10 ` Magnus Damm
2009-03-25 14:46 ` takasi-y
2009-03-30  2:45 ` Magnus Damm
2009-03-30  7:02 ` Francesco VIRLINZI
2009-03-31  8:42 ` Paul Mundt
2009-04-15 11:15 ` Magnus Damm
2009-04-15 11:23 ` Paul Mundt
2009-04-16 14:15 ` Francesco VIRLINZI
2009-04-16 14:22 ` Francesco VIRLINZI
2009-04-17  2:07 ` Magnus Damm
2009-04-17  6:44 ` Francesco VIRLINZI
2009-04-17 10:39 ` Magnus Damm
2009-04-17 12:00 ` Francesco VIRLINZI
2009-04-17 21:38 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-04-20 10:26 ` Magnus Damm
2009-04-20 12:27 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 12:33 ` Francesco VIRLINZI
2009-04-20 12:55 ` Francesco VIRLINZI
2009-04-20 13:03 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 13:15 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 13:30 ` Michael Trimarchi
2009-04-21  7:17 ` Francesco VIRLINZI

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=20090417213830.GG9111@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=linux-sh@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