From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: smsc911x suspend/resume
Date: Mon, 08 Feb 2010 16:42:25 +0200 [thread overview]
Message-ID: <4B7022D1.5030408@compulab.co.il> (raw)
In-Reply-To: <20100208114638.GO9007@buzzloop.caiaq.de>
Daniel Mack wrote:
> On Mon, Feb 08, 2010 at 01:30:42PM +0200, Mike Rapoport wrote:
>> Daniel Mack wrote:
>>> 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?
>
> Yes.
>
>> 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...
>
> 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 :)
> Daniel
--
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 16:42:25 +0200 [thread overview]
Message-ID: <4B7022D1.5030408@compulab.co.il> (raw)
In-Reply-To: <20100208114638.GO9007@buzzloop.caiaq.de>
Daniel Mack wrote:
> On Mon, Feb 08, 2010 at 01:30:42PM +0200, Mike Rapoport wrote:
>> Daniel Mack wrote:
>>> 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?
>
> Yes.
>
>> 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...
>
> 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 :)
> Daniel
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-02-08 14:42 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
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 [this message]
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=4B7022D1.5030408@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.