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 5EEBCC74A5B for ; Wed, 29 Mar 2023 17:46:21 +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=eLGwTipuxWmYSh5VkcDvfs3C75JBUIeKpCyfZqQt1xE=; b=WyC355janCVpiW 5hZi600COpQbSd/UrkRmyknXSsx+4yr6JedHahbp9LrEfHmMDKH8Ew/VJVL/4rveHZZ3MMJnVYS9J /h5zxet2Ik47Vu0jJcVjbaZ5TDOd7Ba21DYEw8pCW+kzLtRpCXKj4yuHI0jiMzU4fBBacdt6vJ3WA r0/AeoCpTtEfAY0xXdKn6acm1XX1A3qeWLVGX6lES1vR+BgrsPCnJG/oVKZW8SkfK/jLVF0VJLgs5 QqTyWEokOepKJs2sGRmwXBPMOGa/lVkYgGQvVKpJ0pKM17ABS4rC0n25/dE4XFqUCWV9hPVl5REyY Y0NUs58D0tfqfIGuzBwA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1phZrH-001LIB-1U; Wed, 29 Mar 2023 17:45:15 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1phZrE-001LGy-0J for linux-arm-kernel@lists.infradead.org; Wed, 29 Mar 2023 17:45:14 +0000 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 295332F4; Wed, 29 Mar 2023 10:45:52 -0700 (PDT) Received: from bogus (unknown [10.57.52.160]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3795D3F6C4; Wed, 29 Mar 2023 10:45:05 -0700 (PDT) Date: Wed, 29 Mar 2023 18:44:31 +0100 From: Sudeep Holla To: Cristian Marussi Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, vincent.guittot@linaro.org, souvik.chakravarty@arm.com, nicola.mazzucato@arm.com, Tushar.Khandelwal@arm.com, viresh.kumar@linaro.org, jassisinghbrar@gmail.com, Rob Herring , Sudeep Holla , Krzysztof Kozlowski , devicetree@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: mailbox : arm,mhuv2: Allow for more RX interrupts Message-ID: <20230329174431.yga3c233sazimane@bogus> References: <20230329153936.394911-1-cristian.marussi@arm.com> <20230329153936.394911-2-cristian.marussi@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230329153936.394911-2-cristian.marussi@arm.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230329_104512_278613_EDC1921E X-CRM114-Status: GOOD ( 24.69 ) 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 Wed, Mar 29, 2023 at 04:39:35PM +0100, Cristian Marussi wrote: > The ARM MHUv2 Receiver block can indeed support more interrupts, up to the > maximum number of available channels, but anyway no more than the maximum > number of supported interrupt for an AMBA device. > > Signed-off-by: Cristian Marussi > --- > Cc: Rob Herring > Cc: Krzysztof Kozlowski > Cc: devicetree@vger.kernel.org > > .../devicetree/bindings/mailbox/arm,mhuv2.yaml | 13 +++++++++---- > 1 file changed, 9 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml b/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml > index a4f1fe63659a..5a57f4e2a623 100644 > --- a/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml > +++ b/Documentation/devicetree/bindings/mailbox/arm,mhuv2.yaml > @@ -69,10 +69,15 @@ properties: > > interrupts: > description: | > - The MHUv2 controller always implements an interrupt in the "receiver" > - mode, while the interrupt in the "sender" mode was not available in the > - version MHUv2.0, but the later versions do have it. > - maxItems: 1 > + The MHUv2 controller always implements at least an interrupt in the > + "receiver" mode, while the interrupt in the "sender" mode was not > + available in the version MHUv2.0, but the later versions do have it. > + In "receiver" mode, beside a single combined interrupt, there could be > + multiple interrupts, up to the number of implemented channels but anyway > + no more than the maximum number of interrupts potentially supported by > + AMBA. > + minItems: 1 > + maxItems: 9 I am not sure 9 is the correct value here. IIUC it is just what Linux defines as AMBA_NR_IRQS. Looking at the history it was bumped from 2 to 9 for use by PL330 DMA driver. I couldn't find anything to relate this 9 in any AMBA or other related specification. Ideally I would say we don't know what the max here. We just have a platform implementing 2 interrupts now. Do we for with 2 for now and change it if some new users require more in the future ? I will leave that to the DT maintainers but 9 is simply random based on Linux code so I would rather choose some other random number with a better reasoning than 9 as AMBA code in the kernel is limiting it to 9. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel