From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, shengjiu.wang@gmail.com
Subject: Re: [PATCH v2 0/2] remoteproc: core: fix issue for multi-instance
Date: Thu, 14 Apr 2022 11:19:47 -0600 [thread overview]
Message-ID: <20220414171947.GB698343@p14s> (raw)
In-Reply-To: <1648434012-16655-1-git-send-email-shengjiu.wang@nxp.com>
On Mon, Mar 28, 2022 at 10:20:10AM +0800, Shengjiu Wang wrote:
> Use the rproc->power reference count to handle the multi-instance
> case, move the state checking for 'stop' and 'detach' under
> mutex protection, and remove state checking for 'start'.
>
> Shengjiu Wang (2):
> remoteproc: core: Remove state checking before calling rproc_boot()
> remoteproc: core: Move state checking to remoteproc_core
>
> changes in v2:
> - drop 'remoteproc: core: check rproc->power value before decreasing it'
> - refine 'remoteproc: core: Remove state checking before changing state'
> split it to two new patches.
>
> drivers/remoteproc/remoteproc_cdev.c | 11 -----------
> drivers/remoteproc/remoteproc_core.c | 11 +++++++++++
> drivers/remoteproc/remoteproc_sysfs.c | 11 -----------
> 3 files changed, 11 insertions(+), 22 deletions(-)
>
I have applied this set.
Thanks,
Mathieu
> --
> 2.17.1
>
prev parent reply other threads:[~2022-04-14 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 2:20 [PATCH v2 0/2] remoteproc: core: fix issue for multi-instance Shengjiu Wang
2022-03-28 2:20 ` [PATCH v2 1/2] remoteproc: core: Remove state checking before calling rproc_boot() Shengjiu Wang
2022-03-28 2:20 ` [PATCH v2 2/2] remoteproc: core: Move state checking to remoteproc_core Shengjiu Wang
2022-04-14 17:19 ` Mathieu Poirier [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=20220414171947.GB698343@p14s \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=shengjiu.wang@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox