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 93CEBC761AF for ; Thu, 30 Mar 2023 08:46:41 +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=raT4ZvIbjvqi1IkZ27t/XbpJgvnhp8y90PGXNRqpzt0=; b=4ZezkOxBldAbxa /oou1bC/wYL/f2mg45wWbOVtRnq2xZzCbXYBb8Zgo0fOMlz9/uH2hiAOxZC9bSYoFvi4rJ3ULuCz8 orSimtxi/kahtH9EUl4Uua3rt4v/Ib0SKnsvt2dSnEfQq70Ax/pLsxpwizvMU58avYBLWwOuyUnDq bZ0LWK6SoSYgW6OW2EZO91JAEllvJ0TNgrmd4LEY3nXaLUJr8mPfr4ftSHiEP2TiajvHlolcJ4nzB qZzkZa6UTyQj3d9xGvzB85YozCLUWdaUUAJcFVVsqcWfC74vyUiPln9rzTY3GhotK+c+9SarPufgW Wx6yXliADWX9sZkozkiQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1phnuc-0038Ix-0e; Thu, 30 Mar 2023 08:45:38 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1phnuZ-0038He-02 for linux-arm-kernel@lists.infradead.org; Thu, 30 Mar 2023 08:45:36 +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 9256D2F4; Thu, 30 Mar 2023 01:46:15 -0700 (PDT) Received: from e120937-lin (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 83F2E3F73F; Thu, 30 Mar 2023 01:45:29 -0700 (PDT) Date: Thu, 30 Mar 2023 09:45:19 +0100 From: Cristian Marussi To: Krzysztof Kozlowski Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com, 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 , Krzysztof Kozlowski , devicetree@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: mailbox : arm,mhuv2: Allow for more RX interrupts Message-ID: References: <20230329153936.394911-1-cristian.marussi@arm.com> <20230329153936.394911-2-cristian.marussi@arm.com> <7e93c0c9-0a84-c1ce-a978-c4743963012b@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <7e93c0c9-0a84-c1ce-a978-c4743963012b@linaro.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230330_014535_143901_6A554AB8 X-CRM114-Status: GOOD ( 26.46 ) 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 Thu, Mar 30, 2023 at 09:36:06AM +0200, Krzysztof Kozlowski wrote: > On 29/03/2023 17:39, 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. > Hi, > Last sentence indicates that TX mode has something else, e.g. max 1 > interrupt. Either correct the sentence or add if:then: narrowing it for TX. > By the spec really you can have up to 124 rx interrupt (one per channel) and optionally 124 tx interrupt too. At least one RX is mandatory, while the TX clear channel iterrupt is optional (and not supported at all for spec < 2.1) In both cases you could just have one single combined interrupt, though, and this is what the driver did, and still do (I have noot changed this), on the TX side: it just supports one single combined tx interrupt. So on the TX side, at the HW level, there could be really 124 interrupts BUT the driver still only support a single combined one. So I think my statement above is anyway ambiguos and I'll fix it, but how to fix it, really depends if we want to describe fully what the HW potentially supports OR what the driver really can cope with as of now. Thanks, Cristian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel