From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 74494C47DD9 for ; Thu, 22 Feb 2024 23:43:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=n/LUBO1TMyGSIkgHIZVoQcWAyxwmFyDj7gbK0LoZfcw=; b=qTFUi/wAnnerIA tBtjpIqHDtxdAzRnbMpidq2nQfTIamZg/qols9nHCCJoGCy6bnI5G6LlCjMeU75qusWnN7OHLwgdS MvmzHmnUFJGRe9hC/E4FGibcD2nD9COYCNWImQ7HJ83qxs1bmYlpfEZBzHxv6nfSRxDxHKiXnIcUg 9AYups+djvZOZ/hnttNUkAkkZ2nzwHKxpRWakClorKQ1E1DccQTUIJtL4Xqm4v804lVfzQtBR2Lwf IWwYcDVPXH9fQ3JBAoS6pje8nJ0cdMZsr/p8OEBVRGpnLjr+vWtiiQtxXjeyng4YxG4sQXfLgYvRi DDpi0Pvz1buh0O3R0T/g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rdIie-0000000757h-0337; Thu, 22 Feb 2024 23:43:12 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rdIia-0000000756s-1olV for linux-arm-kernel@lists.infradead.org; Thu, 22 Feb 2024 23:43:09 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 9A38ECE29D6; Thu, 22 Feb 2024 23:43:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3385EC433F1; Thu, 22 Feb 2024 23:43:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1708645384; bh=orYPHvKEF7pNsfLnqS3JuQ7jmo0kJmxsHCs+Py+BljA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jnJy0g8aJUy/nsIbPKzZliYyca0yhygNbHrmb8qSxM9IRSUuonUBjN6cqCGiQPs7t sinQph2fUfALhfnfpUT+l0JSThKKjSVvJkRtH+chmJYXTaWkISRtTzM1H1qxPKZ7Z0 XLw1swd88spcG3rvy3Ts3unIJLjo5G5UCye+DlcyDHRtWAa9e26hKlFH3FGdmUrOU3 E0hiarafAkSIvMbvLMG/egu1oKGeUll0sJq9ExZ6oHzpX2Xop7tAqpemff2KWx6Yy1 kwE7TSSNCsvBNiIhxz/PEwmOGs2fh/vgnCYqVv/Pc0OH9RQQ8mDNbBnRfdiXSC7mUq RsVPZsDPDk7UQ== Date: Thu, 22 Feb 2024 16:43:00 -0700 From: Rob Herring To: Antonio Borneo Cc: Thomas Gleixner , Krzysztof Kozlowski , Conor Dooley , Maxime Coquelin , Alexandre Torgue , Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, Fabrice Gasnier Subject: Re: [PATCH 02/12] dt-bindings: interrupt-controller: stm32-exti: Add irq nexus child node Message-ID: <20240222234300.GA3809915-robh@kernel.org> References: <20240216094758.916722-1-antonio.borneo@foss.st.com> <20240216094758.916722-3-antonio.borneo@foss.st.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240216094758.916722-3-antonio.borneo@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240222_154308_679763_C8C96255 X-CRM114-Status: GOOD ( 14.29 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Feb 16, 2024 at 10:47:47AM +0100, Antonio Borneo wrote: > The mapping of EXTI interrupts to its parent interrupt controller > is both SoC and instance dependent. > The current implementation requires adding a new table to the > driver's code and a new compatible for each new EXTI instance. > > Add to the binding an interrupt nexus child node that will be > used on the new EXTI instances and can be optionally used on the > existing instances. > The property 'interrupt-map' in the nexus node maps each EXTI > interrupt to the parent interrupt. > Align #address-cells and #interrupt-cells between the EXTI node > and its nexus node. Looks like an abuse of interrupt-map. You avoid adding yourself to the abuser list by putting it in a child node. Clever. (See list in drivers/of/irq.c if you don't know what I'm talking about) I assume the EXTI has 0..N interrupts. Just define 'interrupts' with N entries with each entry mapping EXTI interrupt N to 'interrupts' entry N. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel