public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Percival <matthew@capgo.com>
To: linux-pm@lists.osdl.org
Subject: RE: Powering down a device...
Date: Mon, 21 Nov 2005 12:26:13 +1100	[thread overview]
Message-ID: <1132536373.8816.34.camel@localhost.localdomain> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A5030D5E61@dlee02.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

G'Day,

	Thanks for your reply.  I have tried your suggestions out, but have not
been able to conserve any additional power.

> For device sleeps you just do an 'echo mem > /sys/power/state'.  Pm.c
> will map which sleep and wake this takes you to.

	I just tried comparing `standby' with `mem', and there was no
difference in vmain --- or anywhere else for that matter, though I was
no expecting to see any change elsewhere.

> Each individual device will also have a power/state file in the sysfs
> directory structure.  You can echo a device power state down to the
> driver and it will react how if it knows how to enter that state.

	I tried `standby', `mem' and `disc'
with /sys/devices/platform/smc91x/power/state and saw no change; there
was nothing printed on the terminal either. I guess it must not be
implemented with this driver at the moment, which I guess is why there
is no change when I put the whole system to sleep (please correct me if
my assumptions are wrong).  If it is nothing too difficult to add to the
driver, would you be able to direct me to where I may find out how to do
this?

> Also, in sleeps where you want a good effect, you will need to configure
> the external pins to the optimal sleep state.  Any floating inputs will
> consume a lot of power.... how you drive the pin states really depends
> on what it is connected to.

	That sounds like a rather good tip, thanks!

	-- Matthew


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



       reply	other threads:[~2005-11-21  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EA12F909C0431D458B9D18A176BEE4A5030D5E61@dlee02.ent.ti.com>
2005-11-21  1:26 ` Matthew Percival [this message]
2005-11-21 22:26   ` Powering down a device Geoff Levand
2005-11-22 17:15   ` Patrick Mochel
2005-11-20 22:44 Matthew Percival

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=1132536373.8816.34.camel@localhost.localdomain \
    --to=matthew@capgo.com \
    --cc=linux-pm@lists.osdl.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