From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.17.24]:52876 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752367AbcD1OUZ (ORCPT ); Thu, 28 Apr 2016 10:20:25 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Kevin Hilman , Magnus Damm , linux-renesas-soc@vger.kernel.org, arm@kernel.org, Olof Johansson , Simon Horman Subject: Re: [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.7 Date: Thu, 28 Apr 2016 16:19:40 +0200 Message-ID: <4612233.87LvTVpE8A@wuerfel> In-Reply-To: <1813099.gFLC2Strmj@wuerfel> References: <1813099.gFLC2Strmj@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-renesas-soc-owner@vger.kernel.org List-ID: On Thursday 28 April 2016 16:14:15 Arnd Bergmann wrote: > On Wednesday 27 April 2016 14:06:43 Simon Horman wrote: > > Second Round of Renesas ARM64 Based SoC DT Updates for v4.7 > > > > * Don't disable referenced optional clocks in DT of r8a7795 SoC > > * Populate EXTALR in DT of salvator-x board > > * Enable PCIe in DT of salvator-x board > > > > Pulled into next/dt64. > > I briefly looked at the contents and noticed that the PCIe host > node you add has a dma-ranges property, but its parent node does > not, so you are still limited to 32-bit DMA and you should fix that. > On a closer look, it seems that the memory you map into the PCI is only 1 GB in size, so it's not really a problem, but I think it's cleaner to have an explicit dma-ranges property anyway. Arnd