[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e95a0155-54b6-5aaa-ab4e-10cc3a74f1b6@nxp.com>
Date: Tue, 17 Jan 2023 13:05:40 +0200
From: Iuliana Prodan <iuliana.prodan@....com>
To: Daniel Baluta <daniel.baluta@...il.com>,
"Iuliana Prodan (OSS)" <iuliana.prodan@....nxp.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
"S.J. Wang" <shengjiu.wang@....com>,
Fabio Estevam <festevam@...il.com>,
Daniel Baluta <daniel.baluta@....com>,
linux-imx <linux-imx@....com>, linux-remoteproc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Pengutronix Kernel Team <kernel@...gutronix.de>
Subject: Re: [PATCH] remoteproc: imx_dsp_rproc: add module parameter to ignore
ready flag from remote processor
On 1/17/2023 11:28 AM, Daniel Baluta wrote:
> On Tue, Jan 17, 2023 at 1:21 AM Iuliana Prodan (OSS)
> <iuliana.prodan@....nxp.com> wrote:
>> From: Iuliana Prodan <iuliana.prodan@....com>
>>
>> There are cases when we want to test a simple "hello world"
>> application on the DSP and we don't have IPC between the cores.
>> Therefore, skip the wait for remote processor to start.
>>
>> Added "ignoreready" flag while inserting the module to ignore
>> remote processor reply after start.
>> By default, this is off - do not ignore reply from rproc.
> I think that ignore_dsp_ready would be a clearer name flag.
Done, I've sent a v3.
Thanks,
Iulia
Powered by blists - more mailing lists