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 E9AFFC2BD09 for ; Thu, 27 Jun 2024 21:47:10 +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=1hdWE5zEToOAvVmMdJOCnnZA519ncVrHkH2f1Jn4fcA=; b=bv/0gPiYgSLAMFbbhtnl32cO9q RLTFuNG7+3afefHUAKLyVEb9xGx7jYfaarXfdlnZoCIQWNpw9JGGPKrDVwdAs5CFLi8wcJXEWTgao 9qcfVqQ05zu2dCEHmDJ4cmnz07LO0CHkl9kTlLNxQByrj2ILext48Wrv1GK3im16V2KKDltX994Pd OYPOzqElJ64osjr6Gvx4SpnGK0F/wddKBl/Ae/wn3oNpu3Pva+MulRdltYH/1nA6TGfySNCltzHgP 6K/Lck2guGpvnVlIX26LjR5OnOTir9CZWKQ8wol6im+vCQ4Vm/u5qnU4ZrpguT2oxLj2nhnwh0XFx 08aoxzkw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sMwxE-0000000Bo9t-2Bwa; Thu, 27 Jun 2024 21:46:56 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sMwx6-0000000Bo8d-0VLd for linux-arm-kernel@lists.infradead.org; Thu, 27 Jun 2024 21:46:49 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 540A761EF0; Thu, 27 Jun 2024 21:46:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE9AFC2BBFC; Thu, 27 Jun 2024 21:46:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1719524807; bh=eT7//ofd5tzteAOzE4U68eAT4KD8yHlqWwSSc1NQ8fM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tgVPDYpmfniVXzDq7PDl/rvxdO/4gQUDvQTkdhNVajevCk2nhz95jetooJ8+detL6 sXMVmg/Qjf2yPmpGHRijY1HOtF4EP82g/iEACxQle0dkFlHxzU/KdkWZR+KfIWic5s dQp25Cz7vRPCLFYtCwawZhN+PjLvi7nCNmceM5hjouGadbQj2kd/LDzj4VECcWSi3G 4tyuRG4V8Z60d+k0N1DiNaweoDS9mtr/E4ZA4jI7J0uPhxqKz0Um/rnnumEsnkmNj/ KE5Rva5qpWpcmwi0OXrhA55KCaRehf2h6hs5PenaZDt+c6U5l00RTruHg7LJ+RYEW0 o8T3vV41faddw== Date: Thu, 27 Jun 2024 15:46:45 -0600 From: Rob Herring To: "Peng Fan (OSS)" Cc: Sudeep Holla , Cristian Marussi , Krzysztof Kozlowski , Conor Dooley , arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Peng Fan Subject: Re: [PATCH 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms Message-ID: <20240627214645.GA614300-robh@kernel.org> References: <20240621-scmi-mailbox-v1-v1-0-8ed450735f46@nxp.com> <20240621-scmi-mailbox-v1-v1-1-8ed450735f46@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240621-scmi-mailbox-v1-v1-1-8ed450735f46@nxp.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240627_144648_246761_5E0C9E9B X-CRM114-Status: GOOD ( 16.34 ) 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, Jun 21, 2024 at 08:46:57PM +0800, Peng Fan (OSS) wrote: > From: Peng Fan > > System Controller Management Interface(SCMI) firmwares might have > different designs by SCMI firmware developers. So the maximum receive > channel timeout value might also varies in the various designs. > > So introduce property mbox-rx-timeout-ms to let each platform could > set its own timeout value in device tree. > > Signed-off-by: Peng Fan > --- > Documentation/devicetree/bindings/firmware/arm,scmi.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > index 4d823f3b1f0e..d6cc2bf4c819 100644 > --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml > @@ -121,6 +121,12 @@ properties: > atomic mode of operation, even if requested. > default: 0 > > + max-rx-timeout-ms: > + description: > + An optional time value, expressed in milliseconds, representing, on this > + platform, the mailbox maximum timeout value for receive channel. "on this platform"? Doesn't every property apply to the given platform? > + default: 0 0 means no timeout or response is instant? > + > arm,smc-id: > $ref: /schemas/types.yaml#/definitions/uint32 > description: > > -- > 2.37.1 >