Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965798AbcJXWTp (ORCPT ); Mon, 24 Oct 2016 18:19:45 -0400 Received: from mail-pf0-f173.google.com ([209.85.192.173]:36243 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965599AbcJXWSI (ORCPT ); Mon, 24 Oct 2016 18:18:08 -0400 From: Ray Jui To: Bjorn Helgaas , Bjorn Helgaas Cc: linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org, Alex Barba , Oza Oza , Ray Jui , Ray Jui Subject: [PATCH 09/12] PCI: iproc: Update iProc PCIe DT binding Date: Mon, 24 Oct 2016 15:17:09 -0700 Message-Id: <1477347432-17656-10-git-send-email-ray.jui@broadcom.com> X-Mailer: git-send-email 2.1.4 In-Reply-To: <1477347432-17656-1-git-send-email-ray.jui@broadcom.com> References: <1477347432-17656-1-git-send-email-ray.jui@broadcom.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1190 Lines: 26 Add description for optional device tree property 'dma-ranges' for inbound mapping Signed-off-by: Oza Oza Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt index f827b8d..62a0ab9 100644 --- a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt +++ b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt @@ -25,6 +25,9 @@ Optional properties: - phys: phandle of the PCIe PHY device - phy-names: must be "pcie-phy" - dma-coherent: present if DMA operations are coherent +- dma-ranges: Some PAXB based root complexes do not have inbound mapping done + by the ASIC after power on reset. In this case, SW is required to configure +the mapping, based on inbound memory regions specified by this property - brcm,pcie-ob: Some iProc SoCs do not have the outbound address mapping done by the ASIC after power on reset. In this case, SW needs to configure it -- 2.1.4