Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3660586imm; Mon, 4 Jun 2018 07:20:01 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLSfa5lKMm92KDr6rTcExYLGZQM1ZXrAHLSWVoq/CMwus54vgwrlVUUa1he4mGI6S+CqWOU X-Received: by 2002:a65:4c4d:: with SMTP id l13-v6mr17750854pgr.211.1528122001554; Mon, 04 Jun 2018 07:20:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528122001; cv=none; d=google.com; s=arc-20160816; b=gl3vuhmyaNqadG2TCH2/tWsT2m37QGjUoXju0zzd7eGmYt6qMIhV1mTpM7lvfpSAm4 NF4OlEWamJk28e0QJH2FfbDGkyR6RF2ENA+7rKPztVWlANcUkwtRDabzxETPGzBIPi3p r5k7NH3gN9ruz3PakP4x4kIwUv7vX3OjrykCaTphPxj5kcQmRFIAV4tK1ztaw3m0n5ue uWvZBs+5e4vMFQMqmrPfbWAxC7Mr8XPQ3AUPwxhX4lletHfGCfzeisXOJK3PYETPERu7 uoPDmi9Mdpflpgywjg2fHM51AvZPyjnp9FkVB67KuHppUeNxDPXhUON5OSsoxVAXcr3x G4tw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=p2ZnemnhyqYP023YtRX2wARIHv7Q2/HeBGrnADljZFw=; b=dc2i1utfgBJJJJSdH1ULx032OWAILKQ8TkZ8mhH4kOaPgJuSn5E9jHnUWc0gXkCOf3 WUiA4l82OtFOOEufyfEz0IrjPRD94MYIcFM7VZWxxPhuVJoYHkFDzi12UBYdypKhcqVG sZKCCWq0RAxLi7omsGRcOSU6bmfRJr/ojkPspRydjNdP2DrybgrumDJOynxrcwpovQY7 PVZnO7l9Zud+So+ntazVrKiCmgH+qh2xrIzSJQd9yHHWS2h46SUbXMnKG/998JE4Blzv Vj31uoqxACge/4KYhpMJuXf5D0vqmVYyUj6I//aRh0jH2Z0DXkKH89Kekc9wy5Gp24xM gVkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=hz4MHMdp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s2-v6si2304462pgr.567.2018.06.04.07.19.46; Mon, 04 Jun 2018 07:20:01 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=hz4MHMdp; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753886AbeFDOSN (ORCPT + 99 others); Mon, 4 Jun 2018 10:18:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:40654 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753783AbeFDOSK (ORCPT ); Mon, 4 Jun 2018 10:18:10 -0400 Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 288672089C; Mon, 4 Jun 2018 14:18:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1528121890; bh=Gdd5VpyunMeeU6Dz7visDAsXNVd5pJxRuf/XKeEemyg=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=hz4MHMdpDHtuZy5kubuSd1X4dFYOyEhtQ82miH1jQC1b+fzlhh6tWheCDuPhwOVsp HZVpW8hd4UW3yFxKlPHevAoEhHar5/Fo4jnXPwLWoGuTeTEbyIDEjov8mAeC8M+Q7Y 7BqdUXwGwGrXjkYU83VBnD9Ip4yKmCbHQtqoTegw= Received: by mail-it0-f46.google.com with SMTP id p185-v6so5997230itp.4; Mon, 04 Jun 2018 07:18:10 -0700 (PDT) X-Gm-Message-State: APt69E36sRKw/dOcPCZmlf67FnofpMqW3DMEV0A1Xm+4OBU/zy+RjEZK VXnBXc/S8vo95K4nvRTxdtWDO8IrFV7izoNp4Q== X-Received: by 2002:a24:ec44:: with SMTP id g65-v6mr4659457ith.18.1528121889523; Mon, 04 Jun 2018 07:18:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:5505:0:0:0:0:0 with HTTP; Mon, 4 Jun 2018 07:17:49 -0700 (PDT) In-Reply-To: <1527631130-20045-2-git-send-email-ray.jui@broadcom.com> References: <1527631130-20045-1-git-send-email-ray.jui@broadcom.com> <1527631130-20045-2-git-send-email-ray.jui@broadcom.com> From: Rob Herring Date: Mon, 4 Jun 2018 09:17:49 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/6] PCI: iproc: Update iProc PCI binding for INTx support To: Ray Jui , Arnd Bergmann Cc: Lorenzo Pieralisi , Bjorn Helgaas , Mark Rutland , "linux-kernel@vger.kernel.org" , "maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE" , linux-pci@vger.kernel.org, devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +Arnd On Tue, May 29, 2018 at 4:58 PM, Ray Jui wrote: > Update the iProc PCIe binding document for better modeling of the legacy > interrupt (INTx) support > > Signed-off-by: Ray Jui > --- > .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 31 +++++++++++++++++----- > 1 file changed, 24 insertions(+), 7 deletions(-) > > diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt > index b8e48b4..7ea24dc 100644 > --- a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt > +++ b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt > @@ -13,9 +13,6 @@ 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 > - mapping of the PCIe interface to interrupt numbers > - linux,pci-domain: PCI domain ID. Should be unique for each host controller > - bus-range: PCI bus numbers covered > - #address-cells: set to <3> > @@ -41,6 +38,16 @@ 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) > > +Legacy interrupt (INTx) support (optional): > + > +Note INTx is for PAXB only. > + > +- interrupt-controller: claims itself as an interrupt controller for INTx > +- #interrupt-cells: set to <1> > +- interrupt-map-mask and interrupt-map, standard PCI properties to define > +the mapping of the PCIe interface to interrupt numbers > +- interrupts: interrupt line wired to the generic GIC for INTx support > + > MSI support (optional): > > For older platforms without MSI integrated in the GIC, iProc PCIe core provides > @@ -77,9 +84,14 @@ Example: > compatible = "brcm,iproc-pcie"; > reg = <0x18012000 0x1000>; > > + interrupt-controller; > #interrupt-cells = <1>; > - interrupt-map-mask = <0 0 0 0>; > - interrupt-map = <0 0 0 0 &gic GIC_SPI 100 IRQ_TYPE_NONE>; > + interrupt-map-mask = <0 0 0 7>; > + interrupt-map = <0 0 0 1 &pcie0 1>, Are you sure this works? The irq parsing code will ignore interrupt-map if interrupt-controller is found. In other words, you should have one or the other, but not both. Maybe it happens to work because "pcie0" is this node and your irq numbers are the same. Arnd, any thoughts on this? > + <0 0 0 2 &pcie0 2>, > + <0 0 0 3 &pcie0 3>, > + <0 0 0 4 &pcie0 4>; > + interrupts = ; > > linux,pci-domain = <0>; > > @@ -115,9 +127,14 @@ Example: > compatible = "brcm,iproc-pcie"; > reg = <0x18013000 0x1000>; > > + interrupt-controller; > #interrupt-cells = <1>; > - interrupt-map-mask = <0 0 0 0>; > - interrupt-map = <0 0 0 0 &gic GIC_SPI 106 IRQ_TYPE_NONE>; > + interrupt-map-mask = <0 0 0 7>; > + interrupt-map = <0 0 0 1 &pcie1 1>, > + <0 0 0 2 &pcie1 2>, > + <0 0 0 3 &pcie1 3>, > + <0 0 0 4 &pcie1 4>; > + interrupts = ; > > linux,pci-domain = <1>; > > -- > 2.1.4 >