From: Iuliana Prodan <iuliana.prodan@nxp.com>
To: Daniel Baluta <daniel.baluta@gmail.com>,
"Iuliana Prodan (OSS)" <iuliana.prodan@oss.nxp.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
"S.J. Wang" <shengjiu.wang@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-imx <linux-imx@nxp.com>,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH] remoteproc: imx_dsp_rproc: add module parameter to ignore ready flag from remote processor
Date: Tue, 17 Jan 2023 13:05:40 +0200 [thread overview]
Message-ID: <e95a0155-54b6-5aaa-ab4e-10cc3a74f1b6@nxp.com> (raw)
In-Reply-To: <CAEnQRZDXPtE096aPHRcggdzeha5MeUaWsXqncYE33cdYBByV6Q@mail.gmail.com>
On 1/17/2023 11:28 AM, Daniel Baluta wrote:
> On Tue, Jan 17, 2023 at 1:21 AM Iuliana Prodan (OSS)
> <iuliana.prodan@oss.nxp.com> wrote:
>> From: Iuliana Prodan <iuliana.prodan@nxp.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
WARNING: multiple messages have this Message-ID (diff)
From: Iuliana Prodan <iuliana.prodan@nxp.com>
To: Daniel Baluta <daniel.baluta@gmail.com>,
"Iuliana Prodan (OSS)" <iuliana.prodan@oss.nxp.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
"S.J. Wang" <shengjiu.wang@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-imx <linux-imx@nxp.com>,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH] remoteproc: imx_dsp_rproc: add module parameter to ignore ready flag from remote processor
Date: Tue, 17 Jan 2023 13:05:40 +0200 [thread overview]
Message-ID: <e95a0155-54b6-5aaa-ab4e-10cc3a74f1b6@nxp.com> (raw)
In-Reply-To: <CAEnQRZDXPtE096aPHRcggdzeha5MeUaWsXqncYE33cdYBByV6Q@mail.gmail.com>
On 1/17/2023 11:28 AM, Daniel Baluta wrote:
> On Tue, Jan 17, 2023 at 1:21 AM Iuliana Prodan (OSS)
> <iuliana.prodan@oss.nxp.com> wrote:
>> From: Iuliana Prodan <iuliana.prodan@nxp.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-17 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 22:53 [PATCH] remoteproc: imx_dsp_rproc: add module parameter to ignore ready flag from remote processor Iuliana Prodan (OSS)
2023-01-16 22:53 ` Iuliana Prodan (OSS)
2023-01-17 7:36 ` S.J. Wang
2023-01-17 7:36 ` S.J. Wang
2023-01-17 9:09 ` Iuliana Prodan
2023-01-17 9:09 ` Iuliana Prodan
2023-01-17 9:28 ` Daniel Baluta
2023-01-17 9:28 ` Daniel Baluta
2023-01-17 11:05 ` Iuliana Prodan [this message]
2023-01-17 11:05 ` Iuliana Prodan
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=e95a0155-54b6-5aaa-ab4e-10cc3a74f1b6@nxp.com \
--to=iuliana.prodan@nxp.com \
--cc=andersson@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=iuliana.prodan@oss.nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.