Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp780726ybx; Thu, 7 Nov 2019 02:36:26 -0800 (PST) X-Google-Smtp-Source: APXvYqye6R4F9OrDAni2X4tLEI2KdOZmBztTNTXwDrD2u2Vy2m1YdYYZr7G0DUFROSphPN4wO6dk X-Received: by 2002:a17:906:a457:: with SMTP id cb23mr2207928ejb.191.1573122986501; Thu, 07 Nov 2019 02:36:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573122986; cv=none; d=google.com; s=arc-20160816; b=mtcwoEcpLV7Kml5b+wTXNA9GMR9o6Hu+F/14PcW9X/MBevDPY92D3f9XaxXGcSbKE0 AG0lOJHd/2Fx1X3VRaFQUK8cs0a3NH21cXoYT5G9M7FCqaGPF/iChNqm3l/Z6qTn/eXu 8r3uoD5zpM24OnwCfNrVpsVR5Tac0joOoUijnhLO7z9x7SZyC5brnqE9/VX7dLWcRp5T e4ownPR0LWNRzB9MUF/K9snRseyNeZYRMdh57zmXIKCAH04X2RXbRb/JJW1VDdgvhZcN Dgc+eycZr4goAcGvD+ZacAOYlg4VCN4Ea3IgviC4+3E4kHyfM5Bu8HiYcXG+UYeo1lX5 7ivg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=kvdDkf2CIMcGpjfCK6MVsvBiMYlpvBwYJrqvlYHs0wo=; b=IBR3bCExxm62wTl8GWI2ayC4SQMTRUTYaeVFlBzqCMZ6tNMLP/3GwV20Ojm8rGYD1f CGTp+/G/zxMqvYYUZlBBt/kvLG9/IoIApOEleLoEos2BCpkePwVcBtO4v3iotUcPXqDP VkaE1jHjvJgey4XOitq6Re/a0bpKvtIoUP+F3RfZmJIgU7KScdr2YCfF7oNvTKIbcbnR uNGxoLvM2jOY/bV2nVpK4/M0v0usU8L12Y3KQfsKo4qPB+mEskpeUWK1KtnBOn7aG1RP bW1xYSuwk9XhpT7McO0gRK+2zHAhxVgEhXnGyH9pIdlW6GavbY4iE+QH7xnxj6uXr9Fk 52/w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y57si1101478edb.138.2019.11.07.02.36.02; Thu, 07 Nov 2019 02:36:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388530AbfKGKck (ORCPT + 99 others); Thu, 7 Nov 2019 05:32:40 -0500 Received: from foss.arm.com ([217.140.110.172]:53698 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387796AbfKGKci (ORCPT ); Thu, 7 Nov 2019 05:32:38 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 139551FB; Thu, 7 Nov 2019 02:32:38 -0800 (PST) Received: from localhost (unknown [10.37.6.20]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6D5D83F71A; Thu, 7 Nov 2019 02:32:37 -0800 (PST) Date: Thu, 7 Nov 2019 10:32:35 +0000 From: Andrew Murray To: Nicolas Saenz Julienne Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Bjorn Helgaas , james.quinlan@broadcom.com, mbrugger@suse.com, f.fainelli@gmail.com, phil@raspberrypi.org, wahrenst@gmx.net, Rob Herring , Mark Rutland , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] dt-bindings: pci: add bindings for brcmstb's PCIe device Message-ID: <20191107103235.GW9723@e119886-lin.cambridge.arm.com> References: <20191106214527.18736-1-nsaenzjulienne@suse.de> <20191106214527.18736-2-nsaenzjulienne@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191106214527.18736-2-nsaenzjulienne@suse.de> User-Agent: Mutt/1.10.1+81 (426a6c1) (2018-08-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 06, 2019 at 10:45:23PM +0100, Nicolas Saenz Julienne wrote: > From: Jim Quinlan Nit: Looking at past git history, ideally the patch subject would be 'dt-bindings: *PCI*: *A*dd bindings for brcmstb's PCIe. > > The DT bindings description of the brcmstb PCIe device is described. > This node can only be used for now on the Raspberry Pi 4. > > This was based on Jim's original submission[1], converted to yaml and > adapted to the RPi4 case. Thanks for picking this up. > > [1] https://patchwork.kernel.org/patch/10605937/ > > Signed-off-by: Jim Quinlan > Co-developed-by: Nicolas Saenz Julienne > Signed-off-by: Nicolas Saenz Julienne > --- > .../bindings/pci/brcm,stb-pcie.yaml | 116 ++++++++++++++++++ > 1 file changed, 116 insertions(+) > create mode 100644 Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml > > diff --git a/Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml b/Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml > new file mode 100644 > index 000000000000..0b81c26f8568 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml > @@ -0,0 +1,116 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/pci/brcm,stb-pcie.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Brcmstb PCIe Host Controller Device Tree Bindings > + > +maintainers: > + - Nicolas Saenz Julienne > + > +properties: > + compatible: > + const: brcm,bcm2711-pcie # The Raspberry Pi 4 > + > + reg: > + maxItems: 1 > + > + interrupts: > + minItems: 1 > + maxItems: 2 > + items: > + - description: PCIe host controller > + - description: builtin MSI controller > + > + interrupt-names: > + minItems: 1 > + maxItems: 2 > + items: > + - const: pcie > + - const: msi > + > + "#address-cells": > + const: 3 > + > + "#size-cells": > + const: 2 > + > + "#interrupt-cells": > + const: 1 > + > + interrupt-map-mask: true > + > + interrupt-map: true > + > + ranges: true > + > + dma-ranges: true > + > + clocks: > + maxItems: 1 > + > + clock-names: > + items: > + - const: sw_pcie > + > + msi-controller: > + description: Identifies the node as an MSI controller. > + type: boolean > + > + msi-parent: > + description: MSI controller the device is capable of using. > + $ref: /schemas/types.yaml#/definitions/phandle > + > + linux,pci-domain: > + description: PCI domain ID. Should be unique for each host controller. > + $ref: /schemas/types.yaml#/definitions/uint32 > + > + brcm,enable-ssc: > + description: Indicates usage of spread-spectrum clocking. > + type: boolean > + > +required: > + - compatible > + - reg > + - "#address-cells" > + - "#size-cells" > + - "#interrupt-cells" > + - interrupt-map-mask > + - interrupt-map > + - ranges > + - dma-ranges > + - linux,pci-domain I don't think pci-domain is *required* is it? Thanks, Andrew Murray > + > +additionalProperties: false > + > +examples: > + - | > + #include > + #include > + > + scb { > + #address-cells = <2>; > + #size-cells = <1>; > + pcie0: pcie@7d500000 { > + compatible = "brcm,bcm2711-pcie"; > + reg = <0x0 0x7d500000 0x9310>; > + #address-cells = <3>; > + #size-cells = <2>; > + #interrupt-cells = <1>; > + interrupts = , > + ; > + interrupt-names = "pcie", "msi"; > + interrupt-map-mask = <0x0 0x0 0x0 0x7>; > + interrupt-map = <0 0 0 1 &gicv2 GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH > + 0 0 0 2 &gicv2 GIC_SPI 144 IRQ_TYPE_LEVEL_HIGH > + 0 0 0 3 &gicv2 GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH > + 0 0 0 4 &gicv2 GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>; > + msi-parent = <&pcie0>; > + msi-controller; > + ranges = <0x02000000 0x0 0xf8000000 0x6 0x00000000 0x0 0x04000000>; > + dma-ranges = <0x02000000 0x0 0x00000000 0x0 0x00000000 0x0 0x80000000>; > + linux,pci-domain = <0>; > + brcm,enable-ssc; > + }; > + }; > -- > 2.23.0 >