All of lore.kernel.org
 help / color / mirror / Atom feed
From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: smsc911x suspend/resume
Date: Mon, 08 Feb 2010 13:30:42 +0200	[thread overview]
Message-ID: <4B6FF5E2.6060304@compulab.co.il> (raw)
In-Reply-To: <20100208101123.GW28972@buzzloop.caiaq.de>

Daniel Mack wrote:
> 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.

By AVDD you mean VDD33A?
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...


> 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
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Sincerely yours,
Mike.

WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <mike@compulab.co.il>
To: Daniel Mack <daniel@caiaq.de>
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, 08 Feb 2010 13:30:42 +0200	[thread overview]
Message-ID: <4B6FF5E2.6060304@compulab.co.il> (raw)
In-Reply-To: <20100208101123.GW28972@buzzloop.caiaq.de>

Daniel Mack wrote:
> 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.

By AVDD you mean VDD33A?
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...


> 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
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Sincerely yours,
Mike.

  reply	other threads:[~2010-02-08 11:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  9:42 smsc911x suspend/resume Mike Rapoport
2010-02-08  9:42 ` Mike Rapoport
2010-02-08 10:11 ` Daniel Mack
2010-02-08 10:11   ` Daniel Mack
2010-02-08 11:30   ` Mike Rapoport [this message]
2010-02-08 11:30     ` Mike Rapoport
2010-02-08 11:46     ` Daniel Mack
2010-02-08 11:46       ` Daniel Mack
2010-02-08 14:42       ` Mike Rapoport
2010-02-08 14:42         ` Mike Rapoport
2010-02-08 14:49         ` Daniel Mack
2010-02-08 14:49           ` Daniel Mack
2010-02-08 15:10           ` Mike Rapoport
2010-02-08 15:10             ` Mike Rapoport
2010-02-11 18:26           ` Steve.Glendinning at smsc.com
2010-02-11 18:26             ` Steve.Glendinning
2010-02-14  9:01             ` mike at compulab.co.il
2010-02-14  9:01               ` mike
2010-02-08 11:46     ` Steve.Glendinning at smsc.com
2010-02-08 11:46       ` Steve.Glendinning
2010-02-08 11:53       ` Daniel Mack
2010-02-08 11:53         ` Daniel Mack
2010-02-08 12:27         ` Steve.Glendinning at smsc.com
2010-02-08 12:27           ` Steve.Glendinning
2010-02-08 13:55       ` Mike Rapoport
2010-02-08 13:55         ` Mike Rapoport
  -- strict thread matches above, loose matches on Subject: below --
2015-03-06  9:16 Ran Shalit

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=4B6FF5E2.6060304@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.