Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751160AbdFBGc3 (ORCPT ); Fri, 2 Jun 2017 02:32:29 -0400 Received: from mail-ua0-f173.google.com ([209.85.217.173]:35712 "EHLO mail-ua0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750826AbdFBGc1 (ORCPT ); Fri, 2 Jun 2017 02:32:27 -0400 MIME-Version: 1.0 In-Reply-To: References: <1495790704-2438-1-git-send-email-anup.patel@broadcom.com> <1495790704-2438-5-git-send-email-anup.patel@broadcom.com> From: Anup Patel Date: Fri, 2 Jun 2017 12:02:25 +0530 Message-ID: Subject: Re: [PATCH v5 04/11] arm64: dts: Initial DTS files for Broadcom Stingray SOC To: Florian Fainelli Cc: Rob Herring , Mark Rutland , Michael Turquette , Stephen Boyd , Catalin Marinas , Will Deacon , Ray Jui , Scott Branden , Jon Mason , Oza Pawandeep , Srinath Mannam , Pramod Kumar , Sandeep Tripathy , Device Tree , Linux Kernel , linux-clk , Linux ARM Kernel , BCM Kernel Feedback , Scott Branden Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1144 Lines: 36 On Fri, Jun 2, 2017 at 11:07 AM, Florian Fainelli wrote: > > > 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? Thanks for catching. I quickly update this and send revised patchset. Regards, Anup