From: Daniel Mack <daniel@caiaq.de>
To: Steve.Glendinning@smsc.com
Cc: Mike Rapoport <mike@compulab.co.il>,
LAKML <linux-arm-kernel@lists.infradead.org>,
netdev@vger.kernel.org, Ian.Saturley@smsc.com,
Vlad.Lyalikov@smsc.com, davem@davemloft.net
Subject: Re: smsc911x suspend/resume
Date: Mon, 8 Feb 2010 12:53:16 +0100 [thread overview]
Message-ID: <20100208115316.GA28972@buzzloop.caiaq.de> (raw)
In-Reply-To: <OFE2B2FE18.A8D1D506-ON802576C4.003FCA39-802576C4.0040B683@smsc.com>
On Mon, Feb 08, 2010 at 11:46:39AM +0000, Steve.Glendinning@smsc.com wrote:
> > Anyway, I have all the supplies except VDDVARIO shut down...
> > And the datasheet is indeed comprehensively describes chip power states
> > but I haven't found there anything about supplies required to stay on
> > during suspend...
>
> I don't have the code in front of me (I'm travelling today) but IIRC
> the driver doesn't place the LAN9220 in a specific power saving state,
> so as far as the LAN9220 is concerned it's not actually suspended.
It does, I added that awhile back in b6907b0c7. But as I say, this is
currently hard-coded to D1, and if support for D2 is desired, we would
need to make that a platform data option.
> It's hard to do this in a "generic" way: some people expect their link
> to stay up during suspend, some want suspend to completely power down
> the ethernet chip, and some want to use one of several WoL modes.
>
> David: What's the "done thing" here for similar non-pci drivers?
> Obviously "doesn't work after suspend" isn't the intended behaviour, so
> there's definitely room for improvement!
>
> > > Also have a look at the Raumfeld device patches which use exactly this
> > > chip and which can suspend and resume just fine. You'll need to check
> > > out Eric's devel branch for that.
>
> Daniel: I haven't seen this, do you have a location for the git tree?
git://git.kernel.org/pub/scm/linux/kernel/git/ycmiao/pxa-linux-2.6.git
See the 'devel' branch. But there's actually nothing exciting in there,
it's just a simple platform support.
Daniel
next prev parent reply other threads:[~2010-02-08 11:53 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
2010-02-08 11:46 ` Steve.Glendinning
2010-02-08 11:53 ` Daniel Mack [this message]
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=20100208115316.GA28972@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=Ian.Saturley@smsc.com \
--cc=Steve.Glendinning@smsc.com \
--cc=Vlad.Lyalikov@smsc.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mike@compulab.co.il \
--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).