From: Daniel Mack <daniel@caiaq.de>
To: Mike Rapoport <mike@compulab.co.il>
Cc: Steve Glendinning <steve.glendinning@smsc.com>,
netdev@vger.kernel.org,
LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: smsc911x suspend/resume
Date: Mon, 8 Feb 2010 15:49:51 +0100 [thread overview]
Message-ID: <20100208144951.GF28972@buzzloop.caiaq.de> (raw)
In-Reply-To: <4B7022D1.5030408@compulab.co.il>
On Mon, Feb 08, 2010 at 04:42:25PM +0200, Mike Rapoport wrote:
> Daniel Mack wrote:
> > In fact the datasheet doesn't really state that, and the chip seems
> > to expect the power domains to remain switched on during suspend, and
> > all power switching is done internally. Also the table in "7.4 Power
> > Consumption (Device and System Components)" describes it like that.
> >
> > So it all comes down to the question of how low-power you need to be,
> > and whether you need wake-on-lan or not. What's currently implemented is
> > D1, but adding support for D2 should be easy.
>
> I did some brute force save/restore of smsc9220 registers and it seems
> to wake up now.
> The question now is how to make it in a "generic" way ...
> Thanks for the help anyway :)
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.
Anyway, from what's written in the datasheet, I wouldn't dare just
blindly doing it.
Daniel
next prev parent reply other threads:[~2010-02-08 14:49 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 [this message]
2010-02-08 15:10 ` Mike Rapoport
2010-02-11 18:26 ` Steve.Glendinning
2010-02-14 9:01 ` mike
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=20100208144951.GF28972@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mike@compulab.co.il \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@smsc.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).