netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mike@compulab.co.il
To: Steve.Glendinning@smsc.com
Cc: netdev@vger.kernel.org,
	linux-arm-kernel-bounces@lists.infradead.org,
	LAKML <linux-arm-kernel@lists.infradead.org>,
	Daniel Mack <daniel@caiaq.de>,
	Ian.Saturley@smsc.com
Subject: Re: smsc911x suspend/resume
Date: Sun, 14 Feb 2010 11:01:43 +0200	[thread overview]
Message-ID: <20100214090143.GA23498@gentoodev.compulab.local> (raw)
In-Reply-To: <OFB9598254.A94CFB16-ON802576C5.004BB8B6-802576C7.00655296@smsc.com>

On Thu, Feb 11, 2010 at 06:26:32PM +0000, Steve.Glendinning@smsc.com wrote:
> > Hmm, be careful about switching off power supplies that aren't supposed
> > to be switched off while others are still powered. You can easily
> > destroy hardware with that. Depending on how things are wired up
> > internally, voltages can leak from one unit block to the other. Maybe
> > Steve can can give a statement from official SMSC source about whether
> > it is safe to switch off VDD33A in this case.
> 
> I've checked with the chip architects, no power planes should be 
> externally
> switched off in any suspend mode.

The question if they *can* be switched off. With the hardware I have,
most of 3.3V supplies are enabled/disabled with the same control. So, to
have maximal power saving in the system, I just pull this control to
disable 3.3V supplies, VDD33A among them. If smsc9220 can tolerate
switching VDD33A during suspend, I can send a patch that allows proper
wake-up with such conditions.

> Steve

  reply	other threads:[~2010-02-14  9:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  9:42 smsc911x suspend/resume Mike Rapoport
2010-02-08 10:11 ` Daniel Mack
2010-02-08 11:30   ` Mike Rapoport
2010-02-08 11:46     ` Daniel Mack
2010-02-08 14:42       ` Mike Rapoport
2010-02-08 14:49         ` Daniel Mack
2010-02-08 15:10           ` Mike Rapoport
2010-02-11 18:26           ` Steve.Glendinning
2010-02-14  9:01             ` mike [this message]
2010-02-08 11:46     ` Steve.Glendinning
2010-02-08 11:53       ` Daniel Mack
2010-02-08 12:27         ` Steve.Glendinning
2010-02-08 13:55       ` Mike Rapoport

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=20100214090143.GA23498@gentoodev.compulab.local \
    --to=mike@compulab.co.il \
    --cc=Ian.Saturley@smsc.com \
    --cc=Steve.Glendinning@smsc.com \
    --cc=daniel@caiaq.de \
    --cc=linux-arm-kernel-bounces@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).