From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] remoteproc: add .stop device parameter for stopping remote processor
Date: Mon, 25 Nov 2019 09:28:48 +0100 [thread overview]
Message-ID: <20191125082848.2rkmumxerinj4oa5@pengutronix.de> (raw)
In-Reply-To: <20191121084005.683-3-ahmad@a3f.at>
On Thu, Nov 21, 2019 at 09:40:05AM +0100, Ahmad Fatoum wrote:
> Both the STM32 and i.MX7 remote proc drivers populate the .stop member
> in the struct rproc, but it's not used anywhere.
The .stop member in struct rproc is introduced in this patch.
> The firmware API is not
> really fitting to 'unload' firmware. Add instead a device parameter to
> stop a remote processor, e.g. remoteproc0.stop=1. This is similar to the
> probe command used with MMCs.
>
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
> ---
> drivers/remoteproc/remoteproc_core.c | 30 +++++++++++++++++++++++-----
> include/linux/remoteproc.h | 2 ++
> 2 files changed, 27 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index 8a28c1bafc1b..e031640bc7a0 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -101,6 +101,8 @@ static int rproc_firmware_finish(struct firmware_handler *fh)
> fw.size = rproc->fw_buf_ofs;
>
> ret = rproc_start(rproc, &fw);
> + if (ret == 0)
> + rproc->stop = PARAM_TRISTATE_FALSE;
Can we use positive logic here? "Status Stopped is false" is harder to
read than just "running" or "started".
> kfree(rproc->fw_buf);
>
> @@ -120,6 +122,19 @@ static int rproc_register_dev(struct rproc *rproc, const char *alias)
> return register_device(&rproc->dev);
> }
>
> +static int rproc_set_stop(struct param_d *param, void *priv)
> +{
> + struct rproc *rproc = priv;
> + int (*stop)(struct rproc *);
> +
> + stop = rproc->ops->stop;
> +
> + if (!stop)
> + return -ENOSYS;
> +
> + return stop(rproc);
> +}
I would assume that when I can stop the remote processor with this
parameter I should be able to start it here as well, no?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-11-25 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 8:40 [PATCH 1/3] param: add dev_add_param_tristate(_ro) helpers Ahmad Fatoum
2019-11-21 8:40 ` [PATCH 2/3] watchdog: core: use new dev_add_param_tristate helper for .running param Ahmad Fatoum
2019-11-21 8:40 ` [PATCH 3/3] remoteproc: add .stop device parameter for stopping remote processor Ahmad Fatoum
2019-11-25 8:28 ` Sascha Hauer [this message]
2019-11-25 9:45 ` Ahmad Fatoum
2019-12-04 13:07 ` Ahmad Fatoum
2019-12-05 8:10 ` Sascha Hauer
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=20191125082848.2rkmumxerinj4oa5@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/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