From patchwork Mon Oct 24 22:17:07 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ray Jui X-Patchwork-Id: 9393397 X-Patchwork-Delegate: bhelgaas@google.com Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 08DA2607F0 for ; Mon, 24 Oct 2016 22:20:50 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id EDFC2290B9 for ; Mon, 24 Oct 2016 22:20:49 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id E281E29160; Mon, 24 Oct 2016 22:20:49 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_HI,T_DKIM_INVALID autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 29D3B290B9 for ; Mon, 24 Oct 2016 22:20:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965413AbcJXWUe (ORCPT ); Mon, 24 Oct 2016 18:20:34 -0400 Received: from mail-pf0-f173.google.com ([209.85.192.173]:36213 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965547AbcJXWSB (ORCPT ); Mon, 24 Oct 2016 18:18:01 -0400 Received: by mail-pf0-f173.google.com with SMTP id e6so105850977pfk.3 for ; Mon, 24 Oct 2016 15:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=ZIxcnLrdPiS/q8g4UeSYZfaEvDkbwCJO1aX45SPVAxw=; b=E3pLaPyYlYUfGoR2ep/jWBbV7RKVrZvZALfxP9znvkGJwrLceNiGAFvqdCaF0AESAs OCHz6pwzkMHSNR9Q87ZgxTT34IcZwgHolbIM0lG5KYUAhxBaOWBiJZVnMfXCEmCQmgIe fn0POJA9DkGRhxt2Hp/Hmup4mQb16bZPYBhI4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=ZIxcnLrdPiS/q8g4UeSYZfaEvDkbwCJO1aX45SPVAxw=; b=IH0jfHGbEiG9yZi2fY+qM4xiiBMhspSXUUXh+00Z7XFnav0mnMyhI7j6YWltYBwbkJ k8v2PsLkWoWisffjXZ89g1yF7MMPSzbvHcaHDXJ6Tn3JVph7DWqYSnoUMQNk7cZ6NGhP 8sO1788rkNv0JStYfIGTm4efB8beCzyMDAufQTd6w9d18Z7aDcNi5ExKNJVASJaPAxYB 26QiQo/L4JET45b7h+vIqiL/gWIuYD6+gn49ek/wkZEaHfOZevCyX0+tZw2cOKH5+bAB GwlB11hV2xlJyOy/DE/uhujtUofcClgpqGACwZARfcIyojQS5WQWsILnkCrFA4eTgj1d iF7g== X-Gm-Message-State: ABUngvdKGafF/848+QAHINoM3YGI7MyBy6ERuRAaQCcqvtcZfDQ2ZQ2foqUOPN6k2SI+dg2/ X-Received: by 10.99.143.70 with SMTP id r6mr7380857pgn.54.1477347480167; Mon, 24 Oct 2016 15:18:00 -0700 (PDT) Received: from lbrmn-lnxub44-1.ric.broadcom.com ([216.31.219.19]) by smtp.gmail.com with ESMTPSA id x1sm27745131pax.7.2016.10.24.15.17.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Oct 2016 15:17:59 -0700 (PDT) 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 07/12] PCI: iproc: Update iProc PCIe DT binding Date: Mon, 24 Oct 2016 15:17:07 -0700 Message-Id: <1477347432-17656-8-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-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Remove the following outbound related device tree properties: brcm,pcie-ob-window-size brcm,pcie-ob-oarr-size The above two prperties are a bit duplicated in functions. In addition, the next generation iProc PCIe controller has outbound mapping window that supports more than just two sizes, which cannot be properly supported by these properties A better solution is to make the driver outbound mapping logic slightly more inteligent so it can figure out how to configure the outbound mapping based on the 'ranges' specified in device tree and the number and sizes of the outbound mapping windows that a particular revision of the iProc PCIe controller can support Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt | 7 ------- 1 file changed, 7 deletions(-) diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt index 071bbc2..f827b8d 100644 --- a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt +++ b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt @@ -35,11 +35,6 @@ effective: Required: - brcm,pcie-ob-axi-offset: The offset from the AXI address to the internal address used by the iProc PCIe core (not the PCIe address) -- brcm,pcie-ob-window-size: The outbound address mapping window size (in MB) - -Optional: -- brcm,pcie-ob-oarr-size: Some iProc SoCs need the OARR size bit to be set to -increase the outbound window size MSI support (optional): @@ -95,9 +90,7 @@ Example: phy-names = "pcie-phy"; brcm,pcie-ob; - brcm,pcie-ob-oarr-size; brcm,pcie-ob-axi-offset = <0x00000000>; - brcm,pcie-ob-window-size = <256>; msi-parent = <&msi0>;