[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAALAos_O_dpN8o0C4cUOGmP+UfRSHWep2P-j0ueMP3o7hZcgmQ@mail.gmail.com>
Date: Mon, 15 May 2017 10:39:54 +0530
From: Anup Patel <anup.patel@...adcom.com>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Michael Turquette <mturquette@...libre.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>, Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
Jon Mason <jonmason@...adcom.com>,
Oza Pawandeep <oza@...adcom.com>,
Srinath Mannam <srinath.mannam@...adcom.com>,
Pramod Kumar <pramod.kumar@...adcom.com>,
Sandeep Tripathy <sandeep.tripathy@...adcom.com>,
Device Tree <devicetree@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-clk@...r.kernel.org,
Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
Scott Branden <scott.branden@...adcom.com>
Subject: Re: [PATCH 04/11] arm64: dts: Initial DTS files for Broadcom Stingray SOC
On Mon, May 8, 2017 at 5:00 AM, Florian Fainelli <f.fainelli@...il.com> wrote:
> 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@...adcom.com>
>> Signed-off-by: Scott Branden <scott.branden@...adcom.com>
>> Reviewed-by: Ray Jui <rjui@...adcom.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.
Sure, I will do this.
Regards,
Anup
Powered by blists - more mailing lists