Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Tanmay Shah <tanmay.shah@amd.com>
To: Peng Fan <peng.fan@nxp.com>,
	"andersson@kernel.org" <andersson@kernel.org>,
	"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>
Cc: "linux-remoteproc@vger.kernel.org"
	<linux-remoteproc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remoteproc: xlnx: allow single core use in split mode
Date: Tue, 10 Jun 2025 13:27:24 -0500	[thread overview]
Message-ID: <8cf807c4-de59-4280-b7c6-e01ca0749ebf@amd.com> (raw)
In-Reply-To: <PAXPR04MB8459348088DB7A4FF4253DDA886AA@PAXPR04MB8459.eurprd04.prod.outlook.com>


Hello,

Thanks for your reviews.

On 6/9/25 8:10 PM, Peng Fan wrote:
>> Subject: [PATCH] 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@amd.com>
>> ---
>>   drivers/remoteproc/xlnx_r5_remoteproc.c | 3 ---
>>   1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/remoteproc/xlnx_r5_remoteproc.c
>> b/drivers/remoteproc/xlnx_r5_remoteproc.c
>> index 1af89782e116..f314dd5bdb26 100644
>> --- a/drivers/remoteproc/xlnx_r5_remoteproc.c
>> +++ b/drivers/remoteproc/xlnx_r5_remoteproc.c
>> @@ -1339,9 +1339,6 @@ static int zynqmp_r5_cluster_init(struct
>> zynqmp_r5_cluster *cluster)
>>   	if (core_count == 0) {
> 
> "if ((count == 0 || (count > 2))"
> should be used to here.
> 

That's a fair ask. I will fix it.

>>   		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;
> 
> 
> Then it is safe to drop this code piece, otherwise if hacked devicetree
> being used with 3 r5 cores included, things will go wrong.
> 
> Regards,
> Peng
>>   	} 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
>>
> 


      reply	other threads:[~2025-06-10 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 22:46 [PATCH] remoteproc: xlnx: allow single core use in split mode Tanmay Shah
2025-06-10  1:10 ` Peng Fan
2025-06-10 18:27   ` Tanmay Shah [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8cf807c4-de59-4280-b7c6-e01ca0749ebf@amd.com \
    --to=tanmay.shah@amd.com \
    --cc=andersson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peng.fan@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox