Received: by 10.223.185.116 with SMTP id b49csp292561wrg; Fri, 2 Mar 2018 19:27:15 -0800 (PST) X-Google-Smtp-Source: AG47ELvrfqNEUFbLSTFwx6tJ/vbt3S1K/9VBC2YgNwVq7muSSlphnMQHLh0HGhchEhIFL+BwFLqF X-Received: by 10.98.14.70 with SMTP id w67mr7724698pfi.1.1520047635296; Fri, 02 Mar 2018 19:27:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520047635; cv=none; d=google.com; s=arc-20160816; b=tiYxPJoLlA/7BIHmxaUsipBlfFci4NuxOKeEXLg2DmhnLcNQuJ/zgYcG2H7GSpzFsB hEymI57JxJ1Rqr+d9SBmddH8bLGpBQyi4SGY0zIHVULfFe75Q3f9KMxJrlBGWRRKDTVt PPvpxtWe8A2FCrkHOUnA3TCy1rV2SHUjIKprshe7vgCdi/141QaoNY++lxXGC2LnhtMj w/ZERHo2II2Mk6v95MmJq0gIdKQRVqOqQVLRJvoraISbjR6HdJhXrLVxUHj8O3GBhLDJ swLzEJIMnw5tXPZRHrByLbDkqTWFUT1zxLXscBix79JOwH0NdG/i/VugzXGv6EQnM4vJ 1bpw== 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:arc-authentication-results; bh=D1TvQCf3ICTsnaZmAG9EEmBuOGCx0qH3ankVa2stubI=; b=Negy8ajevlfFm/iRE7P5c4MY68489o21+gRg1DrhllFhODbjZaQXyJVSH23vsvWmNj xVbu5AgK7q9u10kMMutbXr81+5LQIt1ABN2pNFjFD3UdEyHi0SdvoQzJnYVIN+mzS34H KZBW0tIcA0LlAGEUxpm1Ds4CLGhvTM7Pm9hBO3CbgR6xs74zQlKcVcTb5/PZaIcMp0x3 GTLGgzAdtnA6s/Wme4LS3CmMqY5UOqZGR01Nx9ttV0b+e02M31wYb7zoLrZc9G7ImA5I Pcx01J3Pyw9dJzKX9EtAOkb5UQxnefum0vpm2i6LwpMANJ+PL8eqDRsjRxypYZW++moQ iVvg== 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 h1-v6si5854353pln.138.2018.03.02.19.27.00; Fri, 02 Mar 2018 19:27:15 -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 S932176AbeCBTtj (ORCPT + 99 others); Fri, 2 Mar 2018 14:49:39 -0500 Received: from mail-oi0-f66.google.com ([209.85.218.66]:33744 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752744AbeCBTth (ORCPT ); Fri, 2 Mar 2018 14:49:37 -0500 Received: by mail-oi0-f66.google.com with SMTP id e9so1231953oii.0; Fri, 02 Mar 2018 11:49:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=D1TvQCf3ICTsnaZmAG9EEmBuOGCx0qH3ankVa2stubI=; b=rvpCwXpem23VWy2vbnGDBmjQIsq933MRLcI+7r56szSXihznUS6US9JvmqTFtwDkJy GnQIlgBKusI2b7VAMivp+yhSJwib6iQV/BB9BlAbV2lorL2KKdKLNfzS8rQ70+tRTHMM PFBUEdcVtfYqWG0n8t638qby5od2ezKFsIYg9QF+l34bcT6QeZRI+xw5oUQcefmXX9aS FYB53LH+pW25TIfJhCBwhnMpU2799kF9/zFV9AMuF+ggaLYmF+pp5zIC+2uWF+NSxjYj FAnutXg0gSI5+Uejh97AgNzxREfo6hqpky1Rzz6a4TRyFZ/qChSaRcG6VbUB4DohWmlo hm/w== X-Gm-Message-State: APf1xPA3XuPBnPGqzx0Kk53V2ph+Vl04b35Gtm48iq/hTamQhUti9YeC XAXMK+ShW+NcHZRmxgqI1A== X-Received: by 10.202.16.10 with SMTP id 10mr4668967oiq.69.1520020177080; Fri, 02 Mar 2018 11:49:37 -0800 (PST) Received: from localhost (216-188-254-6.dyn.grandenetworks.net. [216.188.254.6]) by smtp.gmail.com with ESMTPSA id 36sm3681160otb.33.2018.03.02.11.49.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 02 Mar 2018 11:49:36 -0800 (PST) Date: Fri, 2 Mar 2018 13:49:35 -0600 From: Rob Herring To: Rasmus Villemoes Cc: Shawn Guo , Thomas Gleixner , Jason Cooper , Marc Zyngier , Mark Rutland , Andy Tang , Alexander Stein , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v5 2/2] dt/bindings: Add bindings for Layerscape external irqs Message-ID: <20180302194935.yq3xw4nxyrxuonz5@rob-hp-laptop> References: <20180125150230.7234-1-rasmus.villemoes@prevas.dk> <20180223210901.23480-1-rasmus.villemoes@prevas.dk> <20180223210901.23480-3-rasmus.villemoes@prevas.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180223210901.23480-3-rasmus.villemoes@prevas.dk> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 23, 2018 at 10:09:00PM +0100, Rasmus Villemoes wrote: > This adds Device Tree binding documentation for the external interrupt > lines with configurable polarity present on some Layerscape SOCs. > > Signed-off-by: Rasmus Villemoes > --- > .../interrupt-controller/fsl,ls-extirq.txt | 44 ++++++++++++++++++++++ > 1 file changed, 44 insertions(+) > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt b/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt > new file mode 100644 > index 000000000000..e510c715e8f6 > --- /dev/null > +++ b/Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt > @@ -0,0 +1,44 @@ > +* Freescale Layerscape external IRQs > + > +Some Layerscape SOCs (LS1021A, LS1043A, LS1046A) support inverting > +the polarity of certain external interrupt lines. > + > +The device node must be a child of the node representing the > +Supplemental Configuration Unit (SCFG). > + > +Required properties: > +- compatible: should be "fsl,-extirq", e.g. "fsl,ls1021a-extirq". > +- interrupt-controller: Identifies the node as an interrupt controller > +- #interrupt-cells: Must be 2. The first element is the index of the > + external interrupt line. The second element is the trigger type. > +- interrupt-parent: phandle of GIC. > +- reg: Specifies the Interrupt Polarity Control Register (INTPCR) in the SCFG. > +- fsl,extirq-map: Specifies the mapping to interrupt numbers in the parent > + interrupt controller. Interrupts are mapped one-to-one to parent > + interrupts. Use the interrupt-map property for this. > + > +Optional properties: > +- fsl,bit-reverse: This boolean property should be set on the LS1021A > + if the SCFGREVCR register has been set to all-ones (which is usually > + the case), meaning that all reads and writes of SCFG registers are > + implicitly bit-reversed. Other compatible platforms do not have such > + a register. > + > +Example: > + scfg: scfg@1570000 { > + compatible = "fsl,ls1021a-scfg", "syscon"; > + ... > + extirq: interrupt-controller { > + compatible = "fsl,ls1021a-extirq"; > + #interrupt-cells = <2>; > + interrupt-controller; > + interrupt-parent = <&gic>; > + reg = <0x1ac>; This needs the length too. What is buys us is following the standard in which mmio has a #size-cells >= 1. BTW, you need a #size-cells and #address-cells properties in the parent. (I think dtc will complain if not). > + fsl,extirq-map = <163 164 165 167 168 169>; > + fsl,bit-reverse; > + }; > + }; > + > + > + interrupts-extended = <&gic GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>, > + <&extirq 1 IRQ_TYPE_LEVEL_LOW>; > -- > 2.15.1 > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html