From patchwork Tue Nov 1 00:38:34 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ray Jui X-Patchwork-Id: 689721 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3t7C8M1TbTz9t3N for ; Tue, 1 Nov 2016 11:41:07 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=broadcom.com header.i=@broadcom.com header.b=VAL6V2S+; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161049AbcKAAj3 (ORCPT ); Mon, 31 Oct 2016 20:39:29 -0400 Received: from mail-pf0-f169.google.com ([209.85.192.169]:34034 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S948331AbcKAAjX (ORCPT ); Mon, 31 Oct 2016 20:39:23 -0400 Received: by mail-pf0-f169.google.com with SMTP id n85so84947452pfi.1 for ; Mon, 31 Oct 2016 17:39:23 -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=9APrDW3yp3iYDRH0T+tFV9QOamGPzB3ITN1R3TPaUgY=; b=VAL6V2S+oo/YkrmbxlscRuRRKH5wz0JPStouZwSFtCGtRar8BJvtxHTWYhpMPoykYc BUeMyCGtkCiH1o1GRd4C7IC/JSYChb+0Ym/kqe1M3mUk9o6vjepI8ZAWLh4mEGu8FIQL Jj6hu00mdHSIyyMAfvmVtH0yL7s7BumZJSQo0= 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=9APrDW3yp3iYDRH0T+tFV9QOamGPzB3ITN1R3TPaUgY=; b=cjkMFQ9WgJuhoAob0oqlz2WrNFRQ2/eXHivS6SZcuSTVyyFka76iqwP5e7iY9d6XWR qdmxYJN8YUJ73Xp2yjbdd3G0Pej2EKuIvUG/+FVKKm7VrnbX0AV8zr9l/f63vZXok93L co5V1j3aSZYuEJeAwmApGfPpvGd6PxPXtivW1Qi8QLCPW1vnGiGrnF8hDrPu32byCKUN zmLU/+D8Bft4egE8gwqykhrrzwtHCXN44OifKNoqaBXO5leFaxH45AZHzvgTp9bJ5irR +spYkq9iD6/hIpUFp06eG1kXuyI3s0ubrhgZ1uq0GlBrN6Pp0cLjUG6VEz3jWJeBqzzB NcxQ== X-Gm-Message-State: ABUngvd/AL3+3j06d4hbjNgUjejA8E7iqcq34EyTOZpxbaF94HQ/J+hI42QQvJlsE5Z8MRR5 X-Received: by 10.98.76.194 with SMTP id e63mr54299475pfj.95.1477960762272; Mon, 31 Oct 2016 17:39:22 -0700 (PDT) Received: from lbrmn-lnxub44-1.ric.broadcom.com ([216.31.219.19]) by smtp.gmail.com with ESMTPSA id x62sm2574619pfb.20.2016.10.31.17.39.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 31 Oct 2016 17:39:21 -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 Subject: [PATCH v2 05/12] PCI: iproc: Added PAXCv2 related binding Date: Mon, 31 Oct 2016 17:38:34 -0700 Message-Id: <1477960721-17649-6-git-send-email-ray.jui@broadcom.com> X-Mailer: git-send-email 2.1.4 In-Reply-To: <1477960721-17649-1-git-send-email-ray.jui@broadcom.com> References: <1477960721-17649-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 Add new compatible string "brcm,iproc-pcie-paxc-v2" to the iProc PCIe device tree binding document. "brcm,iproc-pcie-paxc-v2" is for the second generation of the Broadcom iProc PCIe PAXC host controller Also updated the binding document with more detailed description of each compatible string and compatible SoCs Finally, added description of optional property "msi-map", for use with MSI controllers with sideband data Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 31 ++++++++++++++++------ 1 file changed, 23 insertions(+), 8 deletions(-) diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt index 01b88f4..071bbc2 100644 --- a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt +++ b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt @@ -1,10 +1,15 @@ * Broadcom iProc PCIe controller with the platform bus interface Required properties: -- compatible: Must be "brcm,iproc-pcie" for PAXB, or "brcm,iproc-pcie-paxc" - for PAXC. PAXB-based root complex is used for external endpoint devices. - PAXC-based root complex is connected to emulated endpoint devices - internal to the ASIC +- compatible: + "brcm,iproc-pcie" for the first generation of PAXB based controller, +used in SoCs including NSP, Cygnus, NS2, and Pegasus + "brcm,iproc-pcie-paxc" for the first generation of PAXC based +controller, used in NS2 + "brcm,iproc-pcie-paxc-v2" for the second generation of PAXC based +controller, used in Stingray + PAXB-based root complex is used for external endpoint devices. PAXC-based +root complex is connected to emulated endpoint devices internal to the ASIC - reg: base address and length of the PCIe controller I/O register space - #interrupt-cells: set to <1> - interrupt-map-mask and interrupt-map, standard PCI properties to define the @@ -19,6 +24,7 @@ Required properties: Optional properties: - phys: phandle of the PCIe PHY device - phy-names: must be "pcie-phy" +- dma-coherent: present if DMA operations are coherent - 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 @@ -41,10 +47,19 @@ For older platforms without MSI integrated in the GIC, iProc PCIe core provides an event queue based MSI support. The iProc MSI uses host memories to store MSI posted writes in the event queues -- msi-parent: Link to the device node of the MSI controller. On newer iProc -platforms, the MSI controller may be gicv2m or gicv3-its. On older iProc -platforms without MSI support in its interrupt controller, one may use the -event queue based MSI support integrated within the iProc PCIe core. +On newer iProc platforms, gicv2m or gicv3-its based MSI support should be used + +- msi-map: Maps a Requester ID to an MSI controller and associated MSI +sideband data + +- msi-parent: Link to the device node of the MSI controller, used when no MSI +sideband data is passed between the iProc PCIe controller and the MSI +controller + +Refer to the following binding documents for more detailed description on +the use of 'msi-map' and 'msi-parent': + Documentation/devicetree/bindings/pci/pci-msi.txt + Documentation/devicetree/bindings/interrupt-controller/msi.txt When the iProc event queue based MSI is used, one needs to define the following properties in the MSI device node: