mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Anup Patel <anup.patel@broadcom.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Jon Mason <jonmason@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Oza Pawandeep <oza.oza@broadcom.com>,
	Srinath Mannam <srinath.mannam@broadcom.com>,
	Pramod Kumar <pramod.kumar@broadcom.com>,
	Sandeep Tripathy <sandeep.tripathy@broadcom.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	Scott Branden <scott.branden@broadcom.com>
Subject: Re: [PATCH v5 04/11] arm64: dts: Initial DTS files for Broadcom Stingray SOC
Date: Thu, 1 Jun 2017 22:37:47 -0700	[thread overview]
Message-ID: <abeca9ac-487c-b6dc-1397-4134b0442909@gmail.com> (raw)
In-Reply-To: <1495790704-2438-5-git-send-email-anup.patel@broadcom.com>



On 05/26/2017 02:24 AM, Anup Patel wrote:
> The Broadcom Stingray SoC is a new member in Broadcom iProc
> SoC family.
> 
> This patch adds initial DTS files for Broadcom Stingray SoC
> and two of its reference boards (bcm958742k and bcm958742t).
> 
> We have lot of reference boards and large number of devices
> in Broadcom Stingray SoC so eventually we will have quite
> a few DTS files for Stingray. To tackle, we have added a
> separate directory for Stingray DTS files.

So I was going to apply this, but...


> +	scr {
> +		compatible = "simple-bus";
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		ranges = <0x0 0x0 0x61000000 0x05000000>;

So you corrected the ranges property here...

> +
> +		gic: interrupt-controller@63c00000 {

but you kept the original unit address here, which does not match the
reg property, could you fix that through your entire submission?

> +			compatible = "arm,gic-v3";
> +			#interrupt-cells = <3>;
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +			ranges;
> +			interrupt-controller;
> +			reg = <0x02c00000 0x010000>, /* GICD */
> +			      <0x02e00000 0x600000>; /* GICR */

> +	hsls {
> +		compatible = "simple-bus";
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		ranges = <0x0 0x0 0x68900000 0x17700000>;

Same here.

> +
> +		uart0: uart@68a00000 {
> +			device_type = "serial";
> +			compatible = "snps,dw-apb-uart";
> +			reg = <0x00100000 0x1000>;

and here and all other sub nodes
-- 
Florian

  reply	other threads:[~2017-06-02  5:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  9:24 [PATCH v5 00/11] Broadcom Stingray SOC Initial Support Anup Patel
2017-05-26  9:24 ` [PATCH v5 01/11] dt-bindings: bcm: Add Broadcom Stingray bindings document Anup Patel
2017-05-26  9:24 ` [PATCH v5 02/11] dt-bindings: clk: Extend binding doc for Stingray SOC Anup Patel
2017-05-26  9:24 ` [PATCH v5 03/11] clk: bcm: Add clocks " Anup Patel
2017-05-26  9:24 ` [PATCH v5 04/11] arm64: dts: Initial DTS files for Broadcom " Anup Patel
2017-06-02  5:37   ` Florian Fainelli [this message]
2017-06-02  6:32     ` Anup Patel
2017-05-26  9:24 ` [PATCH v5 05/11] arm64: dts: Add clock DT nodes for " Anup Patel
2017-05-26  9:24 ` [PATCH v5 06/11] arm64: dts: Add NAND " Anup Patel
2017-05-26  9:25 ` [PATCH v5 07/11] arm64: dts: Add pinctrl " Anup Patel
2017-05-26  9:25 ` [PATCH v5 08/11] arm64: dts: Add GPIO " Anup Patel
2017-05-26  9:25 ` [PATCH v5 09/11] arm64: dts: Add I2C DT nodes for Stingray SoC Anup Patel
2017-05-26  9:25 ` [PATCH v5 10/11] arm64: dts: Add PL022, PL330 and SP805 DT nodes for Stingray Anup Patel
2017-05-26  9:25 ` [PATCH v5 11/11] arm64: dts: Add PWM and SDHCI DT nodes for Stingray SOC Anup Patel

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=abeca9ac-487c-b6dc-1397-4134b0442909@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=anup.patel@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonmason@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=oza.oza@broadcom.com \
    --cc=pramod.kumar@broadcom.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sandeep.tripathy@broadcom.com \
    --cc=sboyd@codeaurora.org \
    --cc=sbranden@broadcom.com \
    --cc=scott.branden@broadcom.com \
    --cc=srinath.mannam@broadcom.com \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®