linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Zhao Chenhui <chenhui.zhao@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 4/4] fsl_pmc: update device bindings
Date: Thu, 22 Dec 2011 12:11:33 -0600	[thread overview]
Message-ID: <4EF372D5.3010404@freescale.com> (raw)
In-Reply-To: <1324554214-19502-4-git-send-email-chenhui.zhao@freescale.com>

On 12/22/2011 05:43 AM, Zhao Chenhui wrote:
>    Compatibility does not include bit assignments in SCCR/PMCDR/DEVDISR; these
> -  bit assignments are indicated via the sleep specifier in each device's
> -  sleep property.
> +  bit assignments are indicated via the clock nodes.  Device which has a
> +  controllable clock source should have a "clk-handle" property pointing
> +  to the clock node.

fsl,pmc-handle

>  - reg: For devices compatible with "fsl,mpc8349-pmc", the first resource
>    is the PMC block, and the second resource is the Clock Configuration
>    block.
>  
> -  For devices compatible with "fsl,mpc8548-pmc", the first resource
> -  is a 32-byte block beginning with DEVDISR.
> +  For devices compatible with "fsl,mpc8548-pmc", the second resource
> +  is a 32-byte block beginning with DEVDISR if supported.

What's going on here?

-Scott

  reply	other threads:[~2011-12-22 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22 11:43 [PATCH v3 1/4] powerpc/85xx: add HOTPLUG_CPU support Zhao Chenhui
2011-12-22 11:43 ` [PATCH v3 2/4] powerpc/85xx: add sleep and deep sleep support Zhao Chenhui
2011-12-22 11:43 ` [PATCH v3 3/4] fsl_pmc: Add API to enable device as wakeup event source Zhao Chenhui
2011-12-22 11:43 ` [PATCH v3 4/4] fsl_pmc: update device bindings Zhao Chenhui
2011-12-22 18:11   ` Scott Wood [this message]
2011-12-22 18:12   ` Scott Wood

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=4EF372D5.3010404@freescale.com \
    --to=scottwood@freescale.com \
    --cc=chenhui.zhao@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.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 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).