From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>, <ohad@wizery.com>,
<bjorn.andersson@linaro.org>, <arnaud.pouliquen@st.com>
Cc: <mcoquelin.stm32@gmail.com>, <alexandre.torgue@st.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 00/16] remoteproc: Add support for detaching a remote processor
Date: Fri, 26 Feb 2021 17:40:49 +0100 [thread overview]
Message-ID: <af614b83-de31-f8fe-8b7d-181a71886aa0@foss.st.com> (raw)
In-Reply-To: <20210223233515.3468677-1-mathieu.poirier@linaro.org>
Hi Mathieu,
On 2/24/21 12:34 AM, Mathieu Poirier wrote:
> Following the work done here [1], this set provides support for the
> remoteproc core to release resources associated with a remote processor
> without having to switch it off. That way a platform driver can be removed
> or the application processor power cycled while the remote processor is
> still operating.
>
> Modifications for this revision are detailed in the changelog of each patch
> but the main difference is that going from RPROC_RUNNING -> RPROC_DETACHED
> is no longer supported to avoid dealing tricky resource table issues.
This seems reasonable to me. If necessary, this could be part of a separate series.
From test point of view, it is working pretty well on my side.
Thanks,
Arnaud
>
> Applies cleanly on rproc-next (e8b4e9a21af7). I will rebase on 5.12-rc1 when it
> comes out next week.
>
> Thanks,
> Mathieu
>
> Arnaud POULIQUEN (1):
> remoteproc: stm32: Move memory parsing to rproc_ops
>
> Mathieu Poirier (15):
> remoteproc: Remove useless check in rproc_del()
> remoteproc: Rename function rproc_actuate()
> remoteproc: Add new RPROC_ATTACHED state
> remoteproc: Properly represent the attached state
> remoteproc: Add new get_loaded_rsc_table() to rproc_ops
> remoteproc: stm32: Move resource table setup to rproc_ops
> remoteproc: Add new detach() remoteproc operation
> remoteproc: Introduce function __rproc_detach()
> remoteproc: Introduce function rproc_detach()
> remoteproc: Properly deal with the resource table when attached
> remoteproc: Properly deal with a kernel panic when attached
> remoteproc: Properly deal with a start request when attached
> remoteproc: Properly deal with a stop request when attached
> remoteproc: Properly deal with a detach request when attached
> remoteproc: Refactor rproc delete and cdev release path
>
> drivers/remoteproc/remoteproc_cdev.c | 21 +-
> drivers/remoteproc/remoteproc_core.c | 263 ++++++++++++++++++++---
> drivers/remoteproc/remoteproc_internal.h | 10 +
> drivers/remoteproc/remoteproc_sysfs.c | 17 +-
> drivers/remoteproc/stm32_rproc.c | 168 +++++++--------
> include/linux/remoteproc.h | 21 +-
> 6 files changed, 362 insertions(+), 138 deletions(-)
>
next prev parent reply other threads:[~2021-02-26 16:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 23:34 Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 01/16] remoteproc: Remove useless check in rproc_del() Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 02/16] remoteproc: Rename function rproc_actuate() Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 03/16] remoteproc: Add new RPROC_ATTACHED state Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 04/16] remoteproc: Properly represent the attached state Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 05/16] remoteproc: Add new get_loaded_rsc_table() to rproc_ops Mathieu Poirier
2021-02-26 16:14 ` Arnaud POULIQUEN
2021-03-01 18:03 ` Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 06/16] remoteproc: stm32: Move resource table setup " Mathieu Poirier
2021-02-26 16:14 ` Arnaud POULIQUEN
2021-02-23 23:35 ` [PATCH v6 07/16] remoteproc: stm32: Move memory parsing " Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 08/16] remoteproc: Add new detach() remoteproc operation Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 09/16] remoteproc: Introduce function __rproc_detach() Mathieu Poirier
2021-02-26 16:15 ` Arnaud POULIQUEN
2021-02-23 23:35 ` [PATCH v6 10/16] remoteproc: Introduce function rproc_detach() Mathieu Poirier
2021-02-26 16:15 ` Arnaud POULIQUEN
2021-02-23 23:35 ` [PATCH v6 11/16] remoteproc: Properly deal with the resource table when attached Mathieu Poirier
2021-02-26 16:21 ` Arnaud POULIQUEN
2021-03-01 18:41 ` Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 12/16] remoteproc: Properly deal with a kernel panic " Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 13/16] remoteproc: Properly deal with a start request " Mathieu Poirier
2021-02-23 23:35 ` [PATCH v6 14/16] remoteproc: Properly deal with a stop " Mathieu Poirier
2021-02-26 16:21 ` Arnaud POULIQUEN
2021-02-23 23:35 ` [PATCH v6 15/16] remoteproc: Properly deal with a detach " Mathieu Poirier
2021-02-26 16:21 ` Arnaud POULIQUEN
2021-02-23 23:35 ` [PATCH v6 16/16] remoteproc: Refactor rproc delete and cdev release path Mathieu Poirier
2021-02-26 16:23 ` Arnaud POULIQUEN
2021-03-01 18:58 ` Mathieu Poirier
2021-02-26 16:40 ` Arnaud POULIQUEN [this message]
2021-03-01 18:58 ` [PATCH v6 00/16] remoteproc: Add support for detaching a remote processor Mathieu Poirier
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=af614b83-de31-f8fe-8b7d-181a71886aa0@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=ohad@wizery.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
all inboxes | Powered by JetHome®