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 0A87AD3000A for ; Fri, 18 Oct 2024 13:45:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=qAHvXCQgWJg7cRGtnuQYPs5AFZN5VWrCsHmr5KUh5fg=; b=CDmdMhu85pUOtY9wSPirEcZ0dZ 1dBo7lhvvkkCovvFklM8J7zA/Vk8D9RSuRFrZy4AiKtTl5cRDcucPMbdQOnOF1auFabsuaowgRpCo hLIpNRR/k9WAMiIUmpMXi07ah0EeGPFkTiQmHcr3s+jjfifohQ8qPaX8uzNASWRe2g8D1jwc7S9wH pA3fJDxZ4sKz8OmkZucOKzB7WemKVfgKOt9fZneYbEyv/y5DiouDTtZ7QEvByLkMMVC74k1m212tz c3wMeEoknwOqZHLQahxn6azCr8OJcTXdBRWnePn9BEPRAtOk7JfiMCv/3XK5qUkV3o2pK2/3DxuZk Srn5ysqA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1t1nHg-00000000wC7-1SuL; Fri, 18 Oct 2024 13:44:52 +0000 Received: from nyc.source.kernel.org ([147.75.193.91]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1t1n6s-00000000tP8-3Iwy for linux-arm-kernel@lists.infradead.org; Fri, 18 Oct 2024 13:33:44 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id A2216A43F79; Fri, 18 Oct 2024 13:33:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 17F12C4CEC3; Fri, 18 Oct 2024 13:33:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1729258421; bh=nwqVYg9FZxvkSWfFuD0XeXYk+OpqSn4JaMEIAODptlw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Es909GmGYuFgkFVb/Bhn2p7pUJOjy8hzXCeT2nmEATrjU51VIMQ2FIuBmzgXTpi1Y EW3qyiofuNHMypkZjLNNWlDpSEKOyB7tgaB4Hv19C+I+UPCJYMZ48l1Ji9P88Cpm4s XJQtNgLOGhTh/8cQg/Tg5MY9dzkLJfH7cTUunoI+4H7oNKcR/RmyBhpnL5QODtxSKk P62T1EUeXeD+Gno/lGEfnZRd+6kZUDW5AWf00+Vp1WZBXlFJrvlJ6xzoJw/SWhucBs C6ipnLWfSEWZVW7p20yhJ+5suYN2VVtaYCoQ3ThDvso6c/9+XiJiKlDUiyVJmTHeQX VXJqcGahFEgyw== Date: Fri, 18 Oct 2024 08:33:40 -0500 From: Rob Herring To: Cristian Marussi Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org, sudeep.holla@arm.com, james.quinlan@broadcom.com, f.fainelli@gmail.com, vincent.guittot@linaro.org, etienne.carriere@st.com, peng.fan@oss.nxp.com, michal.simek@amd.com, quic_sibis@quicinc.com, quic_nkela@quicinc.com, dan.carpenter@linaro.org, devicetree@vger.kernel.org, Krzysztof Kozlowski Subject: Re: [PATCH 3/5] dt-bindings: firmware: arm,scmi: Introduce more transport properties Message-ID: <20241018133340.GA72220-robh@kernel.org> References: <20241018080602.3952869-1-cristian.marussi@arm.com> <20241018080602.3952869-4-cristian.marussi@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241018080602.3952869-4-cristian.marussi@arm.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241018_063342_919185_92162490 X-CRM114-Status: GOOD ( 19.96 ) 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Oct 18, 2024 at 09:06:00AM +0100, Cristian Marussi wrote: > Depending on specific hardware and firmware design choices, it may be > possible for different platforms to end up having different requirements > regarding the same transport characteristics. > > Introduce max-msg-size and max-msg properties to describe such platform > specific transport constraints, since they cannot be discovered otherwise. > > Cc: devicetree@vger.kernel.org > Cc: Rob Herring (Arm) > Cc: Krzysztof Kozlowski > Signed-off-by: Cristian Marussi > --- > .../devicetree/bindings/firmware/arm,scmi.yaml | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > index 54d7d11bfed4..42852ed887f2 100644 > --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > @@ -131,6 +131,22 @@ properties: > be a non-zero value if set. > minimum: 1 > > + max-msg-size: Vendor prefix needed. > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: > + An optional value, expressed in bytes, representing the maximum size > + allowed for the payload of messages transmitted on this transport. > + If set it is recommended to be greater or equal than the minimum size > + required to support all the messages defined by the set of protocols > + implemented on this platform. Sounds kind of broken if less than the minimum... > + > + max-msg: Vendor prefix and could be a bit more specific what this is. > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: > + An optional value representing the maximum number of concurrent in-flight > + messages allowed by this transport. If set, the value should be non-zero. > + minimum: 1 > + > arm,smc-id: > $ref: /schemas/types.yaml#/definitions/uint32 > description: > -- > 2.46.1 >