Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp5787063ybi; Sun, 7 Jul 2019 12:39:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqxYGsu8xXDZkP06uCtzghS8D5V+m+rzaAOoblObT4i3a+uVs5eO0FTxqXGi6SaIiSk/C13I X-Received: by 2002:a17:902:ba96:: with SMTP id k22mr14911959pls.44.1562528362068; Sun, 07 Jul 2019 12:39:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562528362; cv=none; d=google.com; s=arc-20160816; b=sypuB79cupyFdEStmvpNcdiDaZNKlJrKYETfcD4ZCVljt3Wc+7mkStd7dxzxgOELps GbBHHR2nJ92UBFhdPTLXNptTuOSbHpp0Wu1Vhzv9xV/VCkQR9DkyXyZcDON9qHCquag2 Y76pLd2rINfQUovvkMXMgShVhjwydrYZkIz8DBeB+Nsoyn8rd0SJa01IybvPwTEBQXZC P4MGbNLkLMt5DY9yg6zDreWabhqd+7fAw/cM4PQE7F40a1mYF3DHcrlJ0YcxspN5J7k+ w88Hq4dra6RCoUVWJJv2vv8xEfNM+EUmlkIxJO4qIdaSqZsOAU0EaZes5EC6fh8dST1/ XWdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=CCP1eajBb1Q/JkWpr9vaMIgtMinGB0ZBl9AdUNDZY6o=; b=VF8XpV5gBAQj7z8FU8BjJh0hvsdSG29cZOOXzhgNGKVI5sMH/oDHvLOMuNQ//6WMDf c31tJmpr5RAAXdHqIx4np5aianQmUoWkAOtgyki8BxRgvw7jo8DWFEX1Jo9SJOtp1SKo ZWCgP89WK6uyyxHXdsbIoXo6kFoLWn1dYwdwW3M0nLj5+maEaNMosxDK7ejrWhXT+kRz JAONQfR4iAZhBruaQ67+ZCKEc4/nDhTqArN9x0WY3k1EdKpesGwYb65f7Uu4xZsGbOuC mpkHIi0RxlgBZDAb/L0pt9TUP3Yk6yuFjG5OG39IiTBUsUpttnQmFrr6mdzuytpWkf36 KGDQ== 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 g1si2198873plj.194.2019.07.07.12.39.07; Sun, 07 Jul 2019 12:39:22 -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; 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 S1727405AbfGGTLK (ORCPT + 99 others); Sun, 7 Jul 2019 15:11:10 -0400 Received: from foss.arm.com ([217.140.110.172]:57062 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726044AbfGGTLK (ORCPT ); Sun, 7 Jul 2019 15:11:10 -0400 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 13DCD360; Sun, 7 Jul 2019 12:11:09 -0700 (PDT) Received: from why (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5FA503F738; Sun, 7 Jul 2019 12:11:07 -0700 (PDT) Date: Sun, 7 Jul 2019 20:10:59 +0100 From: Marc Zyngier To: Aleix Roca Nonell Cc: Andreas =?UTF-8?B?RsOkcmJlcg==?= , Rob Herring , Mark Rutland , Thomas Gleixner , Jason Cooper , Matthias Brugger , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/6] dt-bindings: interrupt-controller: Document RTD129x Message-ID: <20190707201059.0e86dc71@why> In-Reply-To: <20190707132246.GB13340@arks.localdomain> References: <20190707132246.GB13340@arks.localdomain> Organization: ARM Ltd X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 7 Jul 2019 15:22:46 +0200 Aleix Roca Nonell wrote: > Add binding for Realtek RTD129x interrupt controller. > > Signed-off-by: Aleix Roca Nonell > --- > .../realtek,rtd129x-intc.txt | 24 +++++++++++++++++++ > 1 file changed, 24 insertions(+) > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/realtek,rtd129x-intc.txt > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd129x-intc.txt b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd129x-intc.txt > new file mode 100644 > index 000000000000..3ebb7c02afe5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtd129x-intc.txt > @@ -0,0 +1,24 @@ > +Realtek RTD129x IRQ Interrupt Controller > +======================================= > + > +Required properties: > + > +- compatible : Should be one of the following: > + - "realtek,rtd129x-intc-misc" > + - "realtek,rtd129x-intc-iso" What does 'iso' mean in this context? > +- reg : Specifies the address of the ISR, IER and Unmask > + register in couples of "address length". Are these registers actually interleaved with other stuff? What else it in between? > +- interrupts : Specifies the interrupt line which is mux'ed. > +- interrupt-controller : Presence indicates the node as interrupt controller. > +- #interrupt-cells : Shall be 1. See common bindings in interrupt.txt. So I guess this is level only, with an unspecified polarity? No edge interrupts? > + > + > +Example: > + > + interrupt-controller@98007000 { > + compatible = "realtek,rtd129x-iso-irq-mux"; It'd be good if the the example matched the rest of the documentation. > + reg = <0x98007000 0x4 0x98007040 0x4 0x98007004 0x4>; > + interrupts = ; > + interrupt-controller; > + #interrupt-cells = <1>; > + }; Thanks, M. -- Without deviation from the norm, progress is not possible.