[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201008143722.21888-4-etienne.carriere@linaro.org>
Date: Thu, 8 Oct 2020 16:37:21 +0200
From: Etienne Carriere <etienne.carriere@...aro.org>
To: linux-kernel@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org,
Sudeep Holla <sudeep.holla@....com>,
Cristian Marussi <cristian.marussi@....com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Souvik Chakravarty <Souvik.Chakravarty@....com>,
Etienne Carriere <etienne.carriere@...aro.org>,
Peng Fan <peng.fan@....com>
Subject: [PATCH 4/5] firmware: arm_scmi: smc transport supports multi-message pool
There is no reason for the smc transport to restrict itself to a 1
message pool. More can be allocated, messages are copied from/to the
shared memory only on SMC exit/entry hence SCMI driver can play with
several messages.
Use value of 20 to mimic mailbox transport implementation. Any high
value could fit. This should be something configurable.
Signed-off-by: Etienne Carriere <etienne.carriere@...aro.org>
Cc: Peng Fan <peng.fan@....com>
---
drivers/firmware/arm_scmi/smc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/arm_scmi/smc.c b/drivers/firmware/arm_scmi/smc.c
index 1a03c3ec0230..82a82a5dc86a 100644
--- a/drivers/firmware/arm_scmi/smc.c
+++ b/drivers/firmware/arm_scmi/smc.c
@@ -149,6 +149,6 @@ static const struct scmi_transport_ops scmi_smc_ops = {
const struct scmi_desc scmi_smc_desc = {
.ops = &scmi_smc_ops,
.max_rx_timeout_ms = 30,
- .max_msg = 1,
+ .max_msg = 20,
.max_msg_size = 128,
};
--
2.17.1
Powered by blists - more mailing lists