Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752862AbaAGPpM (ORCPT ); Tue, 7 Jan 2014 10:45:12 -0500 Received: from moutng.kundenserver.de ([212.227.17.9]:50707 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751198AbaAGPpG (ORCPT ); Tue, 7 Jan 2014 10:45:06 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Tanmay Inamdar , devicetree@vger.kernel.org, Jon Masters , linux-doc@vger.kernel.org, Catalin Marinas , patches , "linux-kernel@vger.kernel.org" , Grant Likely , Rob Landley , linux-pci@vger.kernel.org, Bjorn Helgaas Subject: Re: [RFC PATCH 3/3] dt-bindings: pci: xgene pcie device tree bindings Date: Tue, 07 Jan 2014 16:44:30 +0100 Message-ID: <4687115.Uo6IImEscY@wuerfel> User-Agent: KMail/4.11 rc1 (Linux/3.10.0-5-generic; KDE/4.11.2; x86_64; ; ) In-Reply-To: <201401071635.02006.arnd@arndb.de> References: <1387785725-24262-1-git-send-email-tinamdar@apm.com> <201401071635.02006.arnd@arndb.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:qrmNHJgSvKZms1HUR5qCXwYnUKTlKngo+YTBcx0uCET yoDKEeE//NROtf0M1VwsuSQjNd2D6Jo3vPy1dPvzSs2VQpdImx 3Wai1+9TI6rn0Ge/zbBUz/goi7w0j1HFe1WZVNkj5PCK/ersv0 uRyrZnT5qmkxTZ+Dj25yPdyDW599dFFeMObRBmczu5d1Wl+fQc X9SCQDbRPxmUD7WKNWZKYqW2OHU0R0qjOQpaLO+IjwpSmzMuvf KG0/xc62KbAESRN9oExVnT879yoDso3ko9bDKRUhds65PcbB67 usLavMHg+YlhB54H987DW0TotGajxUd9lOPxMZbnWdC4/CAR7Q vmj2Vbv1HtaeAHLAtdx8= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 07 January 2014 16:35:01 Arnd Bergmann wrote: > > >> +SoC specific DT Entry: > > >> + pcie0: pcie@1f2b0000 { > > >> + status = "disabled"; > > >> + device_type = "pci"; > > >> + compatible = "xgene,pcie"; > > >> + #interrupt-cells = <1>; > > >> + #size-cells = <2>; > > >> + #address-cells = >; > > >> + reg = < 0x00 0x1f2b0000 0x0 0x00010000>; > > >> + ranges = <0x02000000 0x0 0x00000000 0xe0 0x00000000 0x0 0x10000000 /* mem*/ > > > > > > > > > Also, do you support no prefetchable memory? > > > > HW has either IO or Memory regions for mapping device's memory space. > > There is no separate prefetchable memory space. > > Are you sure the memory is non-prefetchable then? I would have expected > 0x42000000 rather than 0x02000000, but I could be misremembering it. Nevermind. I just checked and you are right: if you only have one memory range, it has to be non-prefetchable. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/