linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "John Williams" <jwilliams@itee.uq.edu.au>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: suspend/resume (Xilinx V4)
Date: Thu, 2 Aug 2007 18:53:04 -0600	[thread overview]
Message-ID: <fa686aa40708021753p45390d10o3faeaa955356b842@mail.gmail.com> (raw)
In-Reply-To: <46B26E97.3040706@itee.uq.edu.au>

On 8/2/07, John Williams <jwilliams@itee.uq.edu.au> wrote:
> Hi,
>
> Any comments on the status/feasibility of suspend/resume for LinuxPPC on
> Xilinx devices?

Pretty much non-existant as far as status goes.  Feasibility depends
entirely on what power management features the Xilinx silicon
supports.  I haven't looked into whether or not the 405 core can be
put into sleep states.

>
> The only suspend-related traffic I see here in the last 12 months is for
> the lite5200b board.
>
> Any guesstimates of level of difficulty for such a task on Xilinx
> PPC405?  The core lite5200b patchset didn't look too hairy (just a
> modest bit of ASM :), but there would also be Xilinx device driver hooks
> to consider.

I suspect the driver code will be where most of the effort lies.

> Also, are there kernel revision dependencies here?  Project is currently
> on an MVL 2.6.10 tree - but have seen mention of 2.6.17 (?) being
> earliest with PPC suspend/resume capability.

Suspend support for ppc has existed for a long time, but there aren't
many embedded ppc boards which support it (5200 being a notable
example).

Personally, I'm keeping up to date with mainline (2.6.22+) on my Virtex tree.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

      reply	other threads:[~2007-08-03  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 23:53 suspend/resume (Xilinx V4) John Williams
2007-08-03  0:53 ` Grant Likely [this message]

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=fa686aa40708021753p45390d10o3faeaa955356b842@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jwilliams@itee.uq.edu.au \
    --cc=linuxppc-embedded@ozlabs.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).