[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240709140957.3171255-1-peng.fan@oss.nxp.com>
Date: Tue, 9 Jul 2024 22:09:56 +0800
From: "Peng Fan (OSS)" <peng.fan@....nxp.com>
To: sudeep.holla@....com,
cristian.marussi@....com,
robh@...nel.org,
krzk+dt@...nel.org,
conor+dt@...nel.org
Cc: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
arm-scmi@...r.kernel.org,
devicetree@...r.kernel.org,
Peng Fan <peng.fan@....com>
Subject: [PATCH V3 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms
From: Peng Fan <peng.fan@....com>
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 <peng.fan@....com>
---
V3:
Add minimum: 1, because 0 is invalid. maximum is not set,
because it is platform specific and unknown.
V2:
Drop defaults, update description.
Documentation/devicetree/bindings/firmware/arm,scmi.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
index ebf384e76df1..f84a978a36b2 100644
--- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
+++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml
@@ -121,6 +121,13 @@ properties:
atomic mode of operation, even if requested.
default: 0
+ max-rx-timeout-ms:
+ description:
+ An optional time value, expressed in milliseconds, representing the
+ mailbox maximum timeout value for receive channel. The value should
+ be a non-zero value if set.
+ minimum: 1
+
arm,smc-id:
$ref: /schemas/types.yaml#/definitions/uint32
description:
--
2.37.1
Powered by blists - more mailing lists