[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250610192738.3095247-1-tanmay.shah@amd.com>
Date: Tue, 10 Jun 2025 12:27:38 -0700
From: Tanmay Shah <tanmay.shah@....com>
To: <andersson@...nel.org>, <mathieu.poirier@...aro.org>
CC: <linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
"Tanmay Shah" <tanmay.shah@....com>
Subject: [PATCH v2] remoteproc: xlnx: allow single core use in split mode
It's a valid use case to have only one core enabled in cluster in split
mode. Remove exact core count expecatation from the driver.
Signed-off-by: Tanmay Shah <tanmay.shah@....com>
---
Change in v2:
- limit core_count to max 2
drivers/remoteproc/xlnx_r5_remoteproc.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/remoteproc/xlnx_r5_remoteproc.c b/drivers/remoteproc/xlnx_r5_remoteproc.c
index 1af89782e116..a1beaa2acc96 100644
--- a/drivers/remoteproc/xlnx_r5_remoteproc.c
+++ b/drivers/remoteproc/xlnx_r5_remoteproc.c
@@ -1336,12 +1336,9 @@ static int zynqmp_r5_cluster_init(struct zynqmp_r5_cluster *cluster)
* and ignore core1 dt node.
*/
core_count = of_get_available_child_count(dev_node);
- if (core_count == 0) {
+ if (core_count == 0 || core_count > 2) {
dev_err(dev, "Invalid number of r5 cores %d", core_count);
return -EINVAL;
- } else if (cluster_mode == SPLIT_MODE && core_count != 2) {
- dev_err(dev, "Invalid number of r5 cores for split mode\n");
- return -EINVAL;
} else if (cluster_mode == LOCKSTEP_MODE && core_count == 2) {
dev_warn(dev, "Only r5 core0 will be used\n");
core_count = 1;
base-commit: dc8417021bcd01914a416bf8bab811a6c5e7d99a
--
2.34.1
Powered by blists - more mailing lists