linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Implementing PowerManagment for a ppc target
Date: Wed, 01 Dec 2004 09:53:44 +1100	[thread overview]
Message-ID: <1101855224.5174.17.camel@gaston> (raw)
In-Reply-To: <41ACE8B0.8090307@246tNt.com>

On Tue, 2004-11-30 at 22:40 +0100, Sylvain Munaut wrote:
> Hi,
> 
> I'm trying to implement Deep Sleep support for a ppc platform based on 
> 5200 and I have some questions :
> 
>  - How should I "integrate" it to linux, what the proper way ? I've been 
> trying #defining CONFIG_PM and
>    using the set_pm_ops operation but my call backs never get called 
> when doing a echo standby > /sys/power/state
> 
> It justs says :
> 
> $ echo standby > 
> /sys/power/state                                                                     
> 
> Stopping tasks: 
> ===                                                                                   

Looks like a kernel thread isn't properly stopping ... note that on
pmac, I don't call that PM core, I do my own salad which does not
involve stopping tasks...

>  stopping tasks failed (2 tasks 
> remaining)                                                           
> Restarting tasks...<6> Strange, init not 
> stopped                                                     
>  Strange, sh not 
> stopped                                                                              
> 
>  done                                                                                                 
> 
> Stopping tasks: 
> ===                                                                                   
> 
>  stopping tasks failed (2 tasks 
> remaining)                                                           
> Restarting tasks...<6> Strange, init not 
> stopped                                                     
>  Strange, sh not 
> stopped                                                                              
> 
>  done                 
> 
> I've been trying to look at Documentation/ and the sources but still I'm 
> not sure ...
> 
> 
>  - How can I ensure that one of my function runs out of I Cache ? Some 
> pieces of assembler needs to not
>    acces memory when the last 'orders' are sent. Does just keeping it 
> small and aligned enough ?

Can you explain more precisely why and what are your precise
requirements ? (You can catch me on irc eventually) 
 
> 
> Thanks,
> 
>     Sylvain Munaut
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>

  reply	other threads:[~2004-11-30 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 21:40 Implementing PowerManagment for a ppc target Sylvain Munaut
2004-11-30 22:53 ` Benjamin Herrenschmidt [this message]
2004-11-30 23:35 ` Hollis Blanchard

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=1101855224.5174.17.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tnt@246tNt.com \
    /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).