From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] powerpc/83xx: Add power management support for MPC837x boards
Date: Tue, 3 Mar 2009 21:34:07 +0300 [thread overview]
Message-ID: <20090303183407.GA27678@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090303175746.GC8692@ld0162-tx32.am.freescale.net>
On Tue, Mar 03, 2009 at 11:57:46AM -0600, Scott Wood wrote:
> On Tue, Mar 03, 2009 at 07:02:01PM +0300, Anton Vorontsov wrote:
> > mdio@24520 {
> > @@ -226,6 +244,8 @@
> > interrupt-parent = <&ipic>;
> > tbi-handle = <&tbi0>;
> > phy-handle = <&phy2>;
> > + sleep = <&pmc 0xc0000000>;
> > + fsl,magic-packet;
> > };
>
> Note that this makes it look to the kernel like enet0 can be put to sleep
> without putting the mdio (which is shared with enet1) to sleep. This is
> why I moved mdio under the ethernet node on 8313erdb.
And that isn't absolutely correct either, since enet1 depends on
net0... If enet0's mdio goes into sleep mode before enet1, then
enet1 will fail to send power-down command to its PHY...
So the better solution would be
sleep-nexus {
sleep = <enet0-sccr>;
enet0 {
mdio {
};
};
enet1 {
sleep = <enet1-sccr>;
};
};
..which isn't 100% correct either, but will work (because we use
a separate driver for the Gianfar MDIO).
What do you think?
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-03-03 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 16:02 [PATCH v2] powerpc/83xx: Add power management support for MPC837x boards Anton Vorontsov
2009-03-03 17:57 ` Scott Wood
2009-03-03 18:34 ` Anton Vorontsov [this message]
2009-03-03 18:39 ` Scott Wood
2009-03-03 19:38 ` [PATCH RFC] powerpc/83xx: Move gianfar mdio nodes under the ethernet nodes Anton Vorontsov
2009-03-04 3:10 ` Li Yang
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=20090303183407.GA27678@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).