[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240703031715.379815-1-peng.fan@oss.nxp.com>
Date: Wed, 3 Jul 2024 11:17:14 +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 V2 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>
---
V2:
Drop defaults, update description.
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 ebf384e76df1..dcac0b36c76f 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 the
+ mailbox maximum timeout value for receive channel. The value should
+ be a non-zero value if set.
+
arm,smc-id:
$ref: /schemas/types.yaml#/definitions/uint32
description:
--
2.37.1
Powered by blists - more mailing lists