mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Subject: [PATCH 3/3] remoteproc: add .stop device parameter for stopping remote processor
Date: Thu, 21 Nov 2019 09:40:05 +0100	[thread overview]
Message-ID: <20191121084005.683-3-ahmad@a3f.at> (raw)
In-Reply-To: <20191121084005.683-1-ahmad@a3f.at>

Both the STM32 and i.MX7 remote proc drivers populate the .stop member
in the struct rproc, but it's not used anywhere. 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;
 
 	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);
+}
+
 int rproc_add(struct rproc *rproc)
 {
 	struct device_d *dev = &rproc->dev;
@@ -142,12 +157,17 @@ int rproc_add(struct rproc *rproc)
 	fh->close = rproc_firmware_finish;
 
 	ret = firmwaremgr_register(fh);
-	if (ret)
-		dev_err(dev, "filed to register firmware handler %s\n", rproc->name);
-	else
-		dev_info(dev, "%s is available\n", rproc->name);
+	if (ret) {
+		dev_err(dev, "failed to register firmware handler %s\n", rproc->name);
+		return ret;
+	}
 
-	return ret;
+	rproc->stop = PARAM_TRISTATE_UNKNOWN;
+	dev_add_param_tristate(&rproc->dev, "stop", rproc_set_stop, NULL,
+			   &rproc->stop, rproc);
+
+	dev_info(dev, "%s is available\n", rproc->name);
+	return 0;
 }
 
 struct rproc *rproc_alloc(struct device_d *dev, const char *name,
diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
index c6264d1c0a49..af35837fb39a 100644
--- a/include/linux/remoteproc.h
+++ b/include/linux/remoteproc.h
@@ -41,6 +41,8 @@ struct rproc {
 
 	void *fw_buf;
 	size_t fw_buf_ofs;
+
+	int stop;
 };
 
 struct rproc *rproc_alloc(struct device_d *dev, const char *name,
-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-11-21  8:40 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 ` Ahmad Fatoum [this message]
2019-11-25  8:28   ` [PATCH 3/3] remoteproc: add .stop device parameter for stopping remote processor Sascha Hauer
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=20191121084005.683-3-ahmad@a3f.at \
    --to=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