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>
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>,
	Oza Pawandeep <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 04/11] arm64: dts: Initial DTS files for Broadcom Stingray SOC
Date: Sun, 7 May 2017 16:30:29 -0700	[thread overview]
Message-ID: <38356358-cfd1-9a29-2b53-80ed495573c6@gmail.com> (raw)
In-Reply-To: <1494071686-19098-5-git-send-email-anup.patel@broadcom.com>

Le 05/06/17 à 04:54, Anup Patel a écrit :
> 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.
> 
> Signed-off-by: Anup Patel <anup.patel@broadcom.com>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
> Reviewed-by: Ray Jui <rjui@broadcom.com>
> ---

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

Sorry for missing that during the internal review, the ranges property
here should include the 6300_0000 offset such that everything else under
the "scr" node is relative to that base address. This makes it a lot
easier to understand the different physical addresses involved and the
bus topology.
-- 
Florian

  reply	other threads:[~2017-05-07 23:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 11:54 [PATCH 00/11] Broadcom Stingray SOC Initial Support Anup Patel
2017-05-06 11:54 ` [PATCH 01/11] dt-bindings: bcm: Add Broadcom Stingray bindings document Anup Patel
2017-05-12 15:18   ` Rob Herring
2017-05-06 11:54 ` [PATCH 02/11] dt-bindings: clk: Extend binding doc for Stingray SOC Anup Patel
2017-05-12 15:21   ` Rob Herring
2017-05-15  5:07     ` Anup Patel
2017-05-06 11:54 ` [PATCH 03/11] clk: bcm: Add clocks " Anup Patel
2017-05-19  1:37   ` Stephen Boyd
2017-05-22 11:53     ` Sandeep Tripathy
2017-05-06 11:54 ` [PATCH 04/11] arm64: dts: Initial DTS files for Broadcom " Anup Patel
2017-05-07 23:30   ` Florian Fainelli [this message]
2017-05-15  5:09     ` Anup Patel
2017-05-08 20:32   ` Scott Branden
2017-05-15  5:11     ` Anup Patel
2017-05-06 11:54 ` [PATCH 05/11] arm64: dts: Add clock DT nodes for " Anup Patel
2017-05-06 11:54 ` [PATCH 06/11] arm64: dts: Add NAND " Anup Patel
2017-05-06 11:54 ` [PATCH 07/11] arm64: dts: Add pinctrl " Anup Patel
2017-05-06 11:54 ` [PATCH 08/11] arm64: dts: Add GPIO " Anup Patel
2017-05-06 11:54 ` [PATCH 09/11] arm64: dts: Add I2C DT nodes for Stingray SoC Anup Patel
2017-05-06 11:54 ` [PATCH 10/11] arm64: dts: Add PL022, PL330 and SP805 DT nodes for Stingray Anup Patel
2017-05-06 11:54 ` [PATCH 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=38356358-cfd1-9a29-2b53-80ed495573c6@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@broadcom.com \
    --cc=pramod.kumar@broadcom.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sandeep.tripathy@broadcom.com \
    --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

Powered by JetHome