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 11:11:23 +0100 [thread overview]
Message-ID: <20100208101123.GW28972@buzzloop.caiaq.de> (raw)
In-Reply-To: <4B6FDC83.9090205@compulab.co.il>
On Mon, Feb 08, 2010 at 11:42:27AM +0200, Mike Rapoport wrote:
> I'm trying to make suspend/resume work on OMAP3-based system and I'm
> encountering issues with resume of SMSC 9220 chip.
> After resume the interface is unusable unless I do 'ifconfig eth0 down'
> and 'ifconfig eth0 up'.
> I would expect that 'ping <some host>' would work right after resume
> without need to bring the interface down and up, but probably I miss
> something.
> Any help would be appreciated.
What happens to your supply voltages when going to suspend? When I
implemented the code for the smsc driver, I could only test scenarios
where AVDD remains stable during suspend. So the driver might need some
tweaks if that assumption is not true in your case. The SMSC datasheet
is quite comprehensive about this topic IIRC.
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
next prev parent reply other threads:[~2010-02-08 10:11 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 [this message]
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
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=20100208101123.GW28972@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).