From: "S.J. Wang" <shengjiu.wang@nxp.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: "bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shengjiu.wang@gmail.com" <shengjiu.wang@gmail.com>
Subject: Re: [PATCH] remoteproc: core: Remove state checking before changing state
Date: Fri, 25 Mar 2022 03:44:20 +0000 [thread overview]
Message-ID: <PAXPR04MB9089EC1B959187335D00953BE31A9@PAXPR04MB9089.eurprd04.prod.outlook.com> (raw)
Hi
> >
> > There is no mutex protecting of these state checking, which can't
> > garantee there is no another instance is trying to do same operation.
> >
> > The reference counter rproc->power is used to manage state changing
> > and there is mutex protection in each operation function for multi
> > instance case.
> >
> > So remove this state checking in rproc_cdev_write() and state_store(),
> > just let reference counter rproc->power to manage the behaviors.
> >
> > Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> > ---
> > drivers/remoteproc/remoteproc_cdev.c | 11 -----------
> > drivers/remoteproc/remoteproc_sysfs.c | 11 -----------
> > 2 files changed, 22 deletions(-)
> >
> > diff --git a/drivers/remoteproc/remoteproc_cdev.c
> > b/drivers/remoteproc/remoteproc_cdev.c
> > index 906ff3c4dfdd..687f205fd70a 100644
> > --- a/drivers/remoteproc/remoteproc_cdev.c
> > +++ b/drivers/remoteproc/remoteproc_cdev.c
> > @@ -32,21 +32,10 @@ static ssize_t rproc_cdev_write(struct file *filp,
> const char __user *buf, size_
> > return -EFAULT;
> >
> > if (!strncmp(cmd, "start", len)) {
> > - if (rproc->state == RPROC_RUNNING ||
> > - rproc->state == RPROC_ATTACHED)
> > - return -EBUSY;
> > -
> > ret = rproc_boot(rproc);
> > } else if (!strncmp(cmd, "stop", len)) {
> > - if (rproc->state != RPROC_RUNNING &&
> > - rproc->state != RPROC_ATTACHED)
> > - return -EINVAL;
> > -
> > ret = rproc_shutdown(rproc);
> > } else if (!strncmp(cmd, "detach", len)) {
> > - if (rproc->state != RPROC_ATTACHED)
> > - return -EINVAL;
> > -
> > ret = rproc_detach(rproc);
> > } else {
> > dev_err(&rproc->dev, "Unrecognized option\n"); diff
> > --git a/drivers/remoteproc/remoteproc_sysfs.c
> > b/drivers/remoteproc/remoteproc_sysfs.c
> > index 51a04bc6ba7a..8c7ea8922638 100644
> > --- a/drivers/remoteproc/remoteproc_sysfs.c
> > +++ b/drivers/remoteproc/remoteproc_sysfs.c
> > @@ -194,23 +194,12 @@ static ssize_t state_store(struct device *dev,
> > int ret = 0;
> >
> > if (sysfs_streq(buf, "start")) {
> > - if (rproc->state == RPROC_RUNNING ||
> > - rproc->state == RPROC_ATTACHED)
> > - return -EBUSY;
> > -
>
> As per my previous comment the above conditions need to be moved into
> rproc_boot().
>
> > ret = rproc_boot(rproc);
> > if (ret)
> > dev_err(&rproc->dev, "Boot failed: %d\n", ret);
> > } else if (sysfs_streq(buf, "stop")) {
> > - if (rproc->state != RPROC_RUNNING &&
> > - rproc->state != RPROC_ATTACHED)
> > - return -EINVAL;
> > -
> > ret = rproc_shutdown(rproc);
> > } else if (sysfs_streq(buf, "detach")) {
> > - if (rproc->state != RPROC_ATTACHED)
> > - return -EINVAL;
> > -
>
> This patch should have been part of a patch series with your other work sent
> on March 18th[1].
>
> Thanks,
> Mathieu
>
> [1]. [PATCH] remoteproc: core: check rproc->power value before decreasing
> it
>
Thanks for the comments.
I still have one question, if there are two instances independently to 'start'
'stop' remoteproc, for example:
Instance1: echo start > /sys/class/remoteproc/remoteproc0/state
Instance2: echo start > /sys/class/remoteproc/remoteproc0/state
...
Instance2: echo stop > /sys/class/remoteproc/remoteproc0/state
...
Instance1: echo stop > /sys/class/remoteproc/remoteproc0/state
When instance2 'stop' the remoteproc, then instance1 will be impacted for
It still needs the service from remoteproc.
That's why I just removed of the checking state, didn't move them to
rproc_boot()/rproc_shutdown()/rproc_detach(). And in order to utilize
the reference counter (rproc->power) to handle the multi-instance case.
Best regards
Wang Shengjiu
next reply other threads:[~2022-03-25 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 3:44 S.J. Wang [this message]
2022-03-25 17:22 ` [PATCH] remoteproc: core: Remove state checking before changing state Mathieu Poirier
-- strict thread matches above, loose matches on Subject: below --
2022-03-28 2:00 S.J. Wang
2022-03-23 9:32 Shengjiu Wang
2022-03-24 16:53 ` 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=PAXPR04MB9089EC1B959187335D00953BE31A9@PAXPR04MB9089.eurprd04.prod.outlook.com \
--to=shengjiu.wang@nxp.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=shengjiu.wang@gmail.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;
as well as URLs for NNTP newsgroup(s).