linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/83xx: Add power management support for MPC837x boards
Date: Fri, 20 Feb 2009 20:37:17 +0300	[thread overview]
Message-ID: <20090220173717.GA7852@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <499EE8DD.2030709@freescale.com>

On Fri, Feb 20, 2009 at 11:31:09AM -0600, Scott Wood wrote:
> Anton Vorontsov wrote:
>> diff --git a/arch/powerpc/boot/dts/mpc8377_mds.dts b/arch/powerpc/boot/dts/mpc8377_mds.dts
>> index 3e3ec8f..c54b90d 100644
>> --- a/arch/powerpc/boot/dts/mpc8377_mds.dts
>> +++ b/arch/powerpc/boot/dts/mpc8377_mds.dts
>> @@ -137,6 +137,7 @@
>>  			reg = <0x3000 0x100>;
>>  			interrupts = <14 0x8>;
>>  			interrupt-parent = <&ipic>;
>> +			sleep = <&pmc 0x0c000000>;
>>  			dfsrr;
>
> [snip]
>
>> @@ -318,6 +325,7 @@
>>  			reg = <0x2e000 0x1000>;
>>  			interrupts = <42 0x8>;
>>  			interrupt-parent = <&ipic>;
>> +			sleep = <&pmc 0x0c000000>;
>
> You have two different nodes with the same bits referenced.

Yes, I2C1 and eSDHC are using the same clock source.

> These nodes
> cannot be put to sleep independently, and as such need to be under a
> common sleep-nexus node.

Ah, that's what the sleep-nexus nodes are for... ;-)

Thank you Scott, I'll add the sleep-nexus nodes.

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

      reply	other threads:[~2009-02-20 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 17:12 [PATCH] powerpc/83xx: Add power management support for MPC837x boards Anton Vorontsov
2009-02-20 17:31 ` Scott Wood
2009-02-20 17:37   ` Anton Vorontsov [this message]

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=20090220173717.GA7852@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).