public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/4 v2]powerpc/fsl-booke: Add support for T2080/T2081 SoC
Date: Fri, 17 Jan 2014 16:27:22 -0600	[thread overview]
Message-ID: <1389997642.24905.284.camel@snotra.buserror.net> (raw)
In-Reply-To: <1389866562-6235-1-git-send-email-Shengzhou.Liu@freescale.com>

On Thu, 2014-01-16 at 18:02 +0800, Shengzhou Liu wrote:
> +	cpc: l3-cache-controller@10000 {
> +		compatible = "cache";
> +		reg = <0x10000 0x1000
> +		       0x11000 0x1000
> +		       0x12000 0x1000>;
> +		interrupts = <16 2 1 27
> +			      16 2 1 26
> +			      16 2 1 25>;
> +	};

Where's the specific compatible for this node?

> +       corenet-cf@18000 {
> +               compatible = "fsl,corenet2-cf";
> +               reg = <0x18000 0x1000>;
> +               interrupts = <16 2 1 31>;
> +               fsl,ccf-num-csdids = <32>;
> +               fsl,ccf-num-snoopids = <32>;
> +       };

"fsl,corenet2-cf" doesn't appear in any other device tree nor in any
binding.

> +	clockgen: global-utilities@e1000 {
> +		compatible = "fsl,qoriq-clockgen-2.0", "fixed-clock";
> +		reg = <0xe1000 0x1000>;
> +		clock-output-names = "sysclk";
> +		#clock-cells = <0>;

Please update this according to v9 of the clock binding:
In particular, sysclk goes in its own node, and compatible strings have
changed.

> +	rcpm: global-utilities@e2000 {
> +		compatible = "fsl,qoriq-rcpm-2.0";
> +		reg = <0xe2000 0x1000>;
> +	};

compatible = "fsl,t2080-rcpm-2.0", "fsl,qoriq-rcpm-2.0";

-Scott

      reply	other threads:[~2014-01-17 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 10:02 [PATCH 3/4 v2]powerpc/fsl-booke: Add support for T2080/T2081 SoC Shengzhou Liu
2014-01-17 22:27 ` Scott Wood [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=1389997642.24905.284.camel@snotra.buserror.net \
    --to=scottwood@freescale.com \
    --cc=Shengzhou.Liu@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