Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/6] ARM: dts: Add SoC level device tree support for LS1021A
Date: Tue, 09 Sep 2014 13:50:09 +0200	[thread overview]
Message-ID: <4286278.g3iXMFknkK@wuerfel> (raw)
In-Reply-To: <1410253952-15631-2-git-send-email-jingchang.lu@freescale.com>

On Tuesday 09 September 2014 17:12:27 Jingchang Lu wrote:

> +		dcfg: dcfg at 1ee0000 {
> +			compatible = "fsl,ls1021a-dcfg";
> +			reg = <0x0 0x1ee0000 0x0 0x10000>;
> +		};
> +		scfg: scfg at 1570000 {
> +			compatible = "fsl,ls1021a-scfg";
> +			reg = <0x0 0x1570000 0x0 0x10000>;
> +		};

Should these be marked as 'compatible = "syscon"' as well?

> +	dcsr {
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		compatible = "fsl,dcsr", "simple-bus";
> +
> +		ranges = <0x0 0x0 0x20000000 0x1000000>;
> +
> +		dcsr-epu at 0 {
> +			compatible = "fsl,ls1021a-dcsr-epu";
> +			reg = <0x0 0x10000>;
> +		};

The binding document only specifies a generic "fsl,dcsr-epu", not
"fsl,ls1021a-dcsr-epu". It also mandates that "interrupts"
must be present and contain three interrupt lines.

Please fix either the DT or the binding, so they match.	

> +		dcsr-gdi at 100000 {
> +			compatible = "fsl,ls1021a-dcsr-gdi";
> +			reg = <0x100000 0x10000>;
> +		};
> +
> +		dcsr-dddi at 120000 {
> +			compatible = "fsl,ls1021a-dcsr-dddi";
> +			reg = <0x120000 0x10000>;
> +		};
> +
> +		dcsr-dcfg at 220000 {
> +			compatible = "fsl,ls1021a-dcsr-dcfg";
> +			reg = <0x220000 0x1000>;
> +		};
> +
> +		dcsr-clock at 221000 {
> +			compatible = "fsl,ls1021a-dcsr-clock";
> +			reg = <0x221000 0x1000>;
> +		};

None of these are part of the dcsr.txt binding.

> +		dcsr-rcpm at 222000 {
> +			compatible = "fsl,ls1021a-dcsr-rcpm";
> +			reg = <0x222000 0x1000 0x223000 0x1000>;
> +		};

Missing generic fsl,dcsr-rcpm compatible value again.

> +		dcsr-ccp at 225000 {
> +			compatible = "fsl,ls1021a-dcsr-ccp";
> +			reg = <0x225000 0x1000>;
> +		};

I'm not checking any devices below this one, I assume they are mostly
incomplete, so please go through the whole list and make sure they
all match the documentation.
I can't really find any code using the dcsr in Linux. Is there
an out of tree driver that you plan to submit?

	Arnd

  reply	other threads:[~2014-09-09 11:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  9:12 [PATCHv3 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 1/6] ARM: dts: Add SoC level device tree support for LS1021A Jingchang Lu
2014-09-09 11:50   ` Arnd Bergmann [this message]
2014-09-11  8:21     ` Jingchang Lu
2014-09-09 11:53   ` Arnd Bergmann
2014-09-11  8:21     ` Jingchang Lu
2014-09-11 10:36       ` Arnd Bergmann
2014-09-11 11:12         ` Sascha Hauer
2014-09-12  9:59           ` Jingchang Lu
2014-09-11  8:41   ` suresh.gupta at freescale.com
2014-09-11  8:58     ` Jingchang Lu
2014-09-11 10:10   ` nikhil.badola at freescale.com
2014-09-12  1:46     ` Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 2/6] ARM: dts: Add initial LS1021A QDS board dts support Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 3/6] ARM: dts: Add initial LS1021A TWR " Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 4/6] dt-bindings: arm: add Freescale LS1021A SoC device tree binding Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 5/6] ARM: imx: Add initial support for Freescale LS1021A Jingchang Lu
2014-09-09 11:41   ` Arnd Bergmann
2014-09-10  3:31     ` Jingchang Lu
2014-09-10  7:42       ` Arnd Bergmann
2014-09-11  9:53         ` Jingchang Lu
2014-09-11 10:44           ` Arnd Bergmann
2014-09-12  3:17             ` Jingchang Lu
2014-09-11 10:05         ` Jingchang Lu
2014-09-09  9:12 ` [PATCHv3 6/6] ARM: imx: Add Freescale LS1021A SMP support Jingchang Lu
  -- strict thread matches above, loose matches on Subject: below --
2014-09-09  8:39 [PATCHv3 1/6] ARM: dts: Add SoC level device tree support for LS1021A Jingchang Lu

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=4286278.g3iXMFknkK@wuerfel \
    --to=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox